NetSight

Security Dashboard

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

Reset
453 matching advisories · page 2 of 16Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.9 CVE-2026-109924 undici vulnerable to Denial of Service via unbounded memory in the EventSource parser npm · undici 37 days ago high7.5 CVE-2026-109869 undici vulnerable to Denial of Service via unhandled error on excessive content-encodings npm · undici 37 days ago medium5.9 CVE-2026-109841 undici vulnerable to Subresource Integrity bypass via non-lowercase algorithm tokens npm · undici 37 days ago high7.4 CVE-2026-109829 undici vulnerable to cache poisoning and cross-user disclosure via cross-origin redirects npm · undici 37 days ago high7.4 CVE-2026-109383 undici vulnerable to TLS certificate validation bypass via dropped tls options in Agent npm · undici 37 days ago high7.5 CVE-2026-109855 undici WebSocket client vulnerable to Denial of Service via failed HTTP/2 handshake npm · undici 37 days ago critical9.8 CVE-2026-110644 nodejs-whisper through 0.3.1 contains an OS command injection vulnerability in convertToWavType() that allows attackers to execute commands by supplying crafte… npm · nodejs-whisper 38 days ago high8.7 CVE-2026-83745 Memory allocation with excessive size value, Improper handling of length parameter inconsistency vulnerability in Apache Thrift nodejs and D lang bindings. Apache Thrift 50 days ago high8.7 CVE-2026-96294 Uncaught exception, Improper Handling of Exceptional Conditions vulnerability in Apache Thrift NodeJS bindings. Apache Thrift 50 days ago high8.2 CVE-2026-94645 Improper validation of specified quantity in input, Allocation of resources without limits or throttling vulnerability in Apache Thrift nodejs bindings. Apache Thrift 50 days ago critical GHSA-wvw7-9m69-qw5x Malicious code in react-nodejs (npm)Malware npm · react-nodejs 53 days ago critical GHSA-4qvj-qq37-mhw2 Malicious code in express-nodejs (npm)Malware npm · express-nodejs, npm · express-nodejs 53 days ago critical GHSA-57gg-7hh5-g549 Malicious code in levels-node-config-nodejs-dione (npm)Malware npm · levels-node-config-nodejs-dione 2026-09-17 critical GHSA-45vg-4vqx-p2cv Malicious code in levels-event-bionics-nodejs (npm)Malware npm · levels-event-bionics-nodejs 2026-09-17 critical GHSA-vm72-vvj8-x2gh Malicious code in less-geckodriver-mongodb-nodejs (npm)Malware npm · less-geckodriver-mongodb-nodejs 2026-09-17 high6.8 GHSA-hmpr-c9rf-qcrf Duplicate Advisory: Incomplete nodejs.* symbol filtering lets sandbox override host WebStream state checks npm · vm2 2026-09-17 critical GHSA-hrmm-3r4r-m4xv Malicious code in leda-nodejs-nextjs-sirius (npm)Malware npm · leda-nodejs-nextjs-sirius 2026-09-17 critical GHSA-xhqg-9q25-mfmm Malicious code in leda-async-nodejs-izar (npm)Malware npm · leda-async-nodejs-izar 2026-09-17 critical GHSA-ghvx-3mr9-wgwx Malicious code in lbank-connector-nodejs (npm)Malware npm · lbank-connector-nodejs, npm · lbank-connector-nodejs 2026-09-17 critical GHSA-5gjm-x46c-7pv7 Malicious code in karma-gatsby-nodejs-europa (npm)Malware npm · karma-gatsby-nodejs-europa 2026-09-17 critical GHSA-x4xp-fc9j-wp77 Malicious code in karma-centauri-nodejs-jupiter (npm)Malware npm · karma-centauri-nodejs-jupiter 2026-09-17 critical GHSA-273x-q478-3xjv Malicious code in jwt-jwt-nodejs-publish (npm)Malware npm · jwt-jwt-nodejs-publish 2026-09-17 critical GHSA-7c5p-h3ww-8g8r Malicious code in jdevice-nodejs-sdk (npm)Malware npm · jdevice-nodejs-sdk 2026-09-13 critical GHSA-63r6-62v6-c7mr Malicious code in javascript-nodejs-lint-staged-build (npm)Malware npm · javascript-nodejs-lint-staged-build 2026-09-13 critical GHSA-8742-6w2w-rvxj Malicious code in izar-magellan-readable-nodejs (npm)Malware npm · izar-magellan-readable-nodejs 2026-09-13 critical GHSA-w66w-h9c7-xw4c Malicious code in iota-umbra-upgrade-nodejs (npm)Malware npm · iota-umbra-upgrade-nodejs 2026-09-13 critical GHSA-cc6w-5hvm-qff4 Malicious code in integrationkit-nodejs (npm)Malware npm · integrationkit-nodejs 2026-09-13 critical GHSA-9hvv-2pxx-34gx Malicious code in init-optimize-css-assets-webpack-plugin-nodejs-grus (npm)Malware npm · init-optimize-css-assets-webpack-plugin-nodejs-grus 2026-09-13 critical GHSA-4wm3-2fh3-2m3f Malicious code in ini-nodejs-speleology-filament (npm)Malware npm · ini-nodejs-speleology-filament 2026-09-13 critical GHSA-9426-v8p9-jrmx Malicious code in hydra-eslint-config-nodejs-triton (npm)Malware npm · hydra-eslint-config-nodejs-triton 2026-09-13

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.