NetSight

Security Dashboard

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

Reset
100 matching advisories · page 1 of 4Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.3 CVE-2026-133487 A security flaw has been discovered in nodejs undici up to 7.24.0. This affects the function... nodejs · undici, undici · undici 35 hours ago medium5.9 CVE-2026-123875 A NULL pointer dereference in Node.js HTTP/2 lets an unauthenticated client crash the server, over both TLS and cleartext, by cancelling file downloads. nodejs · node, nodejs · Node 10 days ago medium6.8 CVE-2026-123877 A certificate validation bypass in Node.js https.Agent lets a cached TLS session authenticated under one CA policy be reused by a later request with a stricter… nodejs · node, nodejs · Node 10 days ago medium6.2 CVE-2026-123871 Node.js discloses proxy credentials in ERR_PROXY_INVALID_CONFIG error messages. CVE-2026-48615... nodejs · node, nodejs · Node 10 days ago medium5.9 CVE-2026-123868 An unauthenticated HTTP/2 client can exhaust Node.js server memory because inbound DATA queued on an undrained stream is charged to no session budget. nodejs · node, nodejs · Node 10 days ago medium4.2 CVE-2026-123867 A per-host mutual-TLS authorization bypass in Node.js lets a client authorized for the default hostname reach a protected hostname it is not authorized for. nodejs · node, nodejs · Node 10 days ago medium5.9 CVE-2026-123828 A one-byte heap buffer overflow in Node.js HTTP/2 Alt-Svc handling lets a remote, unauthenticated attacker corrupt process memory. nodejs · node, nodejs · Node 10 days ago medium6.5 CVE-2026-105481 A flaw in Node.js HTTP Agent connection reuse can cause a client to accept as valid a response that was sent before the client has sent the request. nodejs · node, nodejs · Node 29 days ago medium4.8 CVE-2026-106074 A flaw in Node.js `crypto` causes the internal entropy caches used by `crypto.randomUUID()`, `crypto.randomUUIDv7()`, and `crypto.randomInt()` to be saved into… nodejs · node, nodejs · Node 29 days ago medium6.7 CVE-2026-106072 A flaw in Node.js TLS hostname verification allows a certificate with only a DNS SAN to authenticate an IP endpoint when the client connects using a non-canoni… nodejs · node, nodejs · Node 29 days ago medium5.9 CVE-2026-87029 undici vulnerable to Denial of Service via unhandled exception in the decompress interceptor npm · undici 37 days ago medium5.9 CVE-2026-109932 undici WebSocket client vulnerable to Denial of Service via unbounded automatic PONG buffering npm · undici 37 days ago medium5.9 CVE-2026-109924 undici vulnerable to Denial of Service via unbounded memory in the EventSource parser 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 medium5.2 CVE-2025-7062 A stored cross-site scripting (XSS) vulnerability has been identified in the H5P module `h5p-nodejs-library` by Lumi Education UG in versions up to and includi… versions 2026-09-09 medium5.9 CVE-2026-84890 undici's decompress interceptor decompresses response bodies according to the untrusted Content-Encoding header. npm · undici 2026-09-04 medium5.9 CVE-2026-18149 undici's retry handler can leave an already-exposed response body pending forever. npm · undici 2026-09-04 medium5.9 CVE-2026-85024 undici bundles a WebSocket client whose permessage-deflate size-limit cleanup removes all listeners from the internal zlib inflate stream, including its error … npm · undici 2026-09-04 medium5.9 CVE-2026-85014 undici's experimental WebSocketStream client crashes the whole Node.js process when a remote peer closes the TCP connection without a WebSocket close handshake. npm · undici 2026-09-04 medium6.5 CVE-2026-84933 undici's cache interceptor does not handle the Set-Cookie response header anywhere in its cache path, so it neither refuses to store nor strips that header. npm · undici 2026-09-04 medium4.4 CVE-2026-56850 A flaw in Node.js HTTPS Agent connection reuse can cause PFX object-array key collisions, allowing mutual TLS (mTLS) client identities to be reused across requ… nodejs · node.js 2026-07-30 medium6.1 CVE-2026-56847 A flaw in Node.js Permission Model enforcement allows `trace_events.createTracing().enable()` Writes Trace Logs Outside `--allow-fs-write`. nodejs · node.js 2026-07-30 medium4.2 CVE-2026-15157 undici does not validate the type property of a duck-typed blob-like request body before using it as the Content-Type header on the HTTP/1.1 dispatcher. npm · undici 2026-07-29 medium5.9 CVE-2026-14643 undici's cache interceptor mishandles optional whitespace placed around the equals sign of a qualified no-cache or private Cache-Control directive. npm · undici 2026-07-29 medium4.8 CVE-2026-16728 undici's retry interceptor can deliver a response whose body length does not match the Content-Length header exposed to the application after a retry or resume… npm · undici 2026-07-29 medium4.8 CVE-2026-16729 undici vulnerable to cookie attribute injection via unsanitized domain and unparsed setCookie fields npm · undici 2026-07-29 medium4.3 CVE-2026-48934 A flaw in Node.js TLS host verification can cause an attacker to bypass certification validation. nodejs · node.js 2026-06-26 medium5.4 CVE-2026-48928 A inconsistency in Node.js hostname matching can cause a trust-policy bypass in multi-context mTLS setups. nodejs · node.js 2026-06-26 medium6.5 CVE-2026-48618 A flaw in Node.js TLS hostname handling can cause Node.js unicode dot separator handling can lead to tls wildcard-depth authentication bypass due to resolver a… nodejs · node.js 2026-06-26 medium5.9 CVE-2026-9679 Impact: undici's cookie parser in parseSetCookie percent-decodes cookie values via qsUnescape, turning encoded sequences like %0D%0A, %00, %3B, and %3D into th… npm · undici 2026-06-17

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.