NetSight

Security Dashboard

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

Reset
160 matching advisories · page 1 of 6Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2026-126051 A deferred-callback use-after-destroy in Node.js TLS server handshake handling allows a remote, unauthenticated attacker to terminate the server process. nodejs · node, nodejs · Node 10 days ago high7.5 CVE-2026-123874 A use-after-free in Node.js HTTP/2 lets an unauthenticated client corrupt server memory, over both TLS and cleartext, when the server serves files with respond… nodejs · node, nodejs · Node 10 days ago high8.1 CVE-2026-123872 A client certificate authentication bypass in Node.js TLS lets a client change the servername during TLS 1.2 renegotiation to reach endpoints it was not author… nodejs · node, nodejs · Node 10 days ago high7.5 CVE-2026-123866 A use-after-free in Node.js HTTP/2 stream teardown can leak response memory, including the contents of other connections' response buffers, to a peer. nodejs · node, nodejs · Node 10 days ago high7.5 CVE-2026-123865 Node.js is vulnerable to an HTTP/2 memory and file-descriptor leak via a protocol error during session shutdown nodejs · node, nodejs · Node 10 days ago high8.1 CVE-2026-123864 A re-entrancy flaw in Node.js HTTPS lets an unauthenticated client read memory belonging to other connections, including TLS private keys and other users' requ… nodejs · node, nodejs · Node 10 days ago high8.2 CVE-2026-123863 A reachable assertion in Node.js HTTP/2 session teardown lets any unauthenticated client abort the server, over both TLS and cleartext. nodejs · node, nodejs · Node 10 days ago high7.4 CVE-2026-106069 A flaw in Node.js TLS hostname verification can cause a server certificate to be validated against a different IP address than the one the client connected to,… nodejs · node, nodejs · Node 29 days ago high7.4 CVE-2026-105483 A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the hos… nodejs · node, nodejs · Node 29 days ago high7.4 CVE-2026-105482 A flaw in Node.js DNS resolution allows hostnames containing a NUL byte to be silently truncated by the dns.resolve*() functions and dns.reverse(). nodejs · node, nodejs · Node 29 days ago high7.5 CVE-2026-109461 Origin validation error in Microsoft Authentication Library (MSAL) for Node.js allows an unauthorized attacker to disclose information over a network. npm · @azure/msal-node 36 days ago high7.5 CVE-2026-87018 undici vulnerable to Denial of Service via TLS 1.2 certificate-changing renegotiation 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 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 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 high6.8 GHSA-hmpr-c9rf-qcrf Duplicate Advisory: Incomplete nodejs.* symbol filtering lets sandbox override host WebStream state checks npm · vm2 2026-09-17 high7.5 CVE-2026-19534 undici's WebSocket client crashes the whole Node.js process during the opening handshake when a server responds with a subprotocol that the client never reques… npm · undici 2026-09-04 high7.4 CVE-2026-85152 undici 8.10.0 omits the destination origin from the cache and request-deduplication keys when the cache or deduplicate interceptor is composed directly onto a … npm · undici 2026-09-04 high7.4 CVE-2026-84961 undici's BalancedPool constructor passes its entire options object through an internal deep-clone that serializes and reparses the value as JSON. npm · undici 2026-09-04 high8.4 CVE-2026-58043 A flaw in Node.js Permission Model enforcement can over-grant filesystem access across radix-tree prefix boundaries. nodejs · node.js 2026-07-30 high7.4 CVE-2026-13697 undici vulnerable to cross-user information disclosure and parse-time crash via degenerate private cache directives npm · undici 2026-07-29 high7.3 CVE-2026-13760 OS command injection in the NodejsFunction Docker bundling pipeline (OsCommand helper) in AWS aws-cdk-lib on all platforms might allow a actor who controls dep… npm · aws-cdk-lib 2026-07-01 high7.5 CVE-2026-48933 A flaw in Node.js WebCrypto implementation can crash the process if the input of `subtle.encrypt()` is a multiple of 2GiB. nodejs · node.js 2026-06-26 high7.5 CVE-2026-48619 A flaw in Node.js HTTP/2 client allows a server to send an unlimited number of ORIGIN frames, which could lead to an Out of Memory error on the client. nodejs · node.js 2026-06-26 high7.5 CVE-2026-48615 A flaw in Node.js proxy tunnel error handling could expose proxy credentials in `ERR_PROXY_TUNNEL` error messages. nodejs · node.js 2026-06-26 high7.5 CVE-2026-48937 A flaw in Node.js HTTP/2 server API can cause servers to keep accepting data even after sending a `GOAWAY` frame. nodejs · node.js 2026-06-18

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.