NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
268 matching advisories · page 7 of 9Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-q8m9-67xc-5f4f Malicious code in angular_turbolinks (RubyGems)Malware rubygems · angular_turbolinks 2026-07-18 critical GHSA-xm5f-7c4r-7wgx Malware in @aonunited/angularMalware npm · @aonunited/angular 2026-07-14 critical GHSA-m7gq-xcwc-78ff Malware in @bodata/angular-clientMalware npm · @bodata/angular-client 2026-06-29 critical10.0 CVE-2026-44643 Angular Expressions provides expressions for the Angular.JS web framework as a standalone module. npm · angular-expressions 2026-05-11 critical GHSA-66qr-2394-v3r3 Malware in accesso-angular-cache-busterMalware npm · accesso-angular-cache-buster 2026-05-04 critical9.0 CVE-2026-32635 Angular vulnerable to XSS in i18n attribute bindings npm · @angular/core, npm · @angular/compiler 2026-03-13 critical9.2 CVE-2026-27739 Angular SSR is vulnerable to SSRF and Header Injection via request handling pipeline npm · @angular/ssr, npm · @nguniversal/common, npm · @nguniversal/express-engine 2026-02-25 critical GHSA-wm69-3896-655x Malware in angular-trackjsMalware npm · angular-trackjs 2025-12-16 critical GHSA-w5m9-xgcq-gxg3 Malware in @trackstar/test-angular-packageMalware npm · @trackstar/test-angular-package 2025-11-24 critical GHSA-p9gj-r4rh-387h Malware in @trackstar/angular-trackstar-linkMalware npm · @trackstar/angular-trackstar-link 2025-11-24 critical GHSA-vhcq-fc6c-hqx4 Malware in itobuz-angular-buttonMalware npm · itobuz-angular-button 2025-11-24 critical GHSA-6c53-64xr-m4p9 Malware in itobuz-angular-authMalware npm · itobuz-angular-auth 2025-11-24 critical GHSA-fchc-834c-jcv5 Malware in itobuz-angularMalware npm · itobuz-angular 2025-11-24 critical GHSA-5q87-h8mq-78q3 Malware in @aryanhussain/my-angular-libMalware npm · @aryanhussain/my-angular-lib 2025-11-24 critical GHSA-rvm6-mw53-3fpx Malware in geopost-angular-componentsMalware npm · geopost-angular-components 2025-10-29 critical GHSA-9hqf-jr5p-23fr Malware in rxjs-angularMalware npm · rxjs-angular 2025-10-29 critical GHSA-fwrp-2g24-6w68 Malware in mstate-angularMalware npm · mstate-angular 2025-09-17 critical GHSA-46m6-c3w3-fw8g Malware in devextreme-angular-rpkMalware npm · devextreme-angular-rpk 2025-09-16 critical GHSA-gfmr-m5h5-m2fw Malware in @ui-ux-gang/devextreme-angular-rpkMalware npm · @ui-ux-gang/devextreme-angular-rpk 2025-09-16 critical GHSA-5f79-8vrf-wfmq Malware in xo-angular-ui-utilsMalware npm · xo-angular-ui-utils 2025-09-16 critical GHSA-6wgq-85c7-p729 Malware in angulartics2Malware npm · angulartics2 2025-09-15 critical GHSA-pmrr-9qcr-gcmp Malware in @nstudio/web-angularMalware npm · @nstudio/web-angular 2025-09-15 critical GHSA-f286-5397-5vx6 Malware in @nstudio/angularMalware npm · @nstudio/angular 2025-09-15 critical GHSA-6rgp-9pj9-2459 Malware in sos-angularMalware npm · sos-angular 2025-09-11 critical GHSA-g8px-4wmr-545q Malware in @navancorp/angular-web-componentsMalware npm · @navancorp/angular-web-components 2025-09-11 critical GHSA-jvrx-qgv4-g2qh Malware in @3kali182/angular-1.6Malware npm · @3kali182/angular-1.6 2025-07-16 critical GHSA-x73f-rp7r-jc2m Malware in @emersonecologics/emerson-angular-troveMalware npm · @emersonecologics/emerson-angular-trove 2025-07-15 critical GHSA-86h4-x6m9-cgg8 Malware in emerson-angular-troveMalware npm · emerson-angular-trove 2025-07-15 critical GHSA-hxm5-ghqv-wp94 Malware in angular-introMalware npm · angular-intro 2025-06-25 critical GHSA-h4qr-pw6p-f247 Malware in traceviz-angular-coreMalware npm · traceviz-angular-core 2025-06-20

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.