NetSight

Security Dashboard

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

Reset
453 matching advisories · page 5 of 16Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-9vg7-pm72-4598 Malicious code in @zalastax/nolb-nodejst (npm)Malware npm · @zalastax/nolb-nodejst 2026-08-14 critical GHSA-46w8-g867-mrq4 Malicious code in @zalastax/nolb-nodejsp (npm)Malware npm · @zalastax/nolb-nodejsp 2026-08-14 critical GHSA-5jc5-c7c9-4php Malicious code in @zalastax/nolb-nodejs_ (npm)Malware npm · @zalastax/nolb-nodejs_ 2026-08-14 critical GHSA-7gwg-w46g-wm99 Malicious code in functions-framework-nodejs (npm)Malware npm · functions-framework-nodejs 2026-08-13 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 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 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 critical GHSA-8cx5-gjvj-8q8v Malicious code in @amiga-fwk-nodejs/log (npm)Malware npm · @amiga-fwk-nodejs/log 2026-07-26 critical GHSA-g8h2-q3c5-hcm7 Malicious code in @amiga-fwk-nodejs/metrics (npm)Malware npm · @amiga-fwk-nodejs/metrics 2026-07-26 critical GHSA-whqv-q5hv-396f Malicious code in 8888acc-utility-service-nodejs-clien (npm)Malware npm · 8888acc-utility-service-nodejs-clien 2026-07-26 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 low3.3 CVE-2026-48936 A flaw in Node.js Permission API can cause a local server to be started (via a Unix domain socket), even without the `--allow-net` permission. nodejs · node.js 2026-06-26 low3.3 CVE-2026-48935 A flaw in Node.js Permission API can cause a file metadata to be modified even on a path that was set as read-only with e.g. nodejs · node.js 2026-06-26 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 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 critical9.8 CVE-2026-48930 A flaw in Node.js TLS hostname handling can cause Embedded-nul hostnames can lead to silent authority rebinding due to c-string truncation in resolver bindings. 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 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 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 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 low3.7 CVE-2026-48931 A flaw in Node.js HTTP Agent can cause a client to accept as valid a response that is send before the client has sent the request. nodejs · node.js 2026-06-22 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 high8.2 CVE-2026-48617 A flaw in Node.js Permission Model enforcement allows Bypass via `process.report.writeReport()` Path Misvalidation. nodejs · node.js 2026-06-18 high7.4 CVE-2026-9697 Impact: undici's ProxyAgent silently drops the requestTls option when configured with a SOCKS5 proxy URI (socks5:// or socks://). npm · undici 2026-06-17 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.