NetSight

Security Dashboard

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

Reset
24 matching advisories · page 1 of 1Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
low2.9 CVE-2026-123862 An uncatchable exception in the Node.js zlib streaming API lets a peer crash a process by disconnecting while data is being compressed. nodejs · node, nodejs · Node 10 days ago low2.5 CVE-2026-123829 A Permission Model bypass in Node.js recursive file watching discloses the names of files and directories the process is not permitted to read. nodejs · node, nodejs · Node 10 days ago low3.6 CVE-2026-106071 A flaw in Node.js Permission Model filesystem enforcement can grant access to paths that do not match a wildcard `--allow-fs-read` or `--allow-fs-write` rule. nodejs · node, nodejs · Node 29 days ago low3.7 CVE-2026-106070 A flaw in the Node.js `zlib.ZipFile` API can cause it to return bytes that do not belong to the requested entry after the local and central header validation f… nodejs · node, nodejs · Node 29 days ago low3.3 CVE-2026-106073 A flaw in Node.js Permission Model filesystem enforcement leaves `fs.realpathSync()` without the required read permission checks. nodejs · node, nodejs · Node 29 days ago low3.7 CVE-2026-18540 undici's retry interceptor can append the body of a ranged retry response to bytes already delivered from an earlier partial response while still presenting th… npm · undici 2026-09-04 low3.7 CVE-2026-85008 undici's cache interceptor documents that only safe HTTP methods are cached, but its logic to skip caching is built by subtracting the configured methods from … npm · undici 2026-09-04 low3.7 CVE-2026-84947 undici vulnerable to response truncation via oversized chunked responses in the dump interceptor npm · undici 2026-09-04 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 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 low3.7 CVE-2026-6733 Impact: Undici's HTTP/1.1 client is vulnerable to response queue poisoning on reused keep-alive sockets. npm · undici 2026-06-17 low3.7 CVE-2026-11525 Impact: When undici parses a Set-Cookie header, it accepts any SameSite attribute value that contains Strict, Lax, or None as a substring, rather than the case… npm · undici 2026-06-17 low3.3 CVE-2026-21716 An incomplete fix for CVE-2024-36137 leaves `FileHandle.chmod()` and `FileHandle.chown()` in the promises API without the required permission checks, while the… nodejs · node.js 2026-03-30 low3.3 CVE-2026-21715 A flaw in Node.js Permission Model filesystem enforcement leaves `fs.realpathSync.native()` without the required read permission checks, while all comparable f… nodejs · node.js 2026-03-30 low3.3 CVE-2025-46328 NodeJS Driver for Snowflake has race condition when checking access to Easy Logging configuration file npm · snowflake-sdk 2025-04-28 low2.6 CVE-2024-30261 Undici's fetch with integrity option is too lax when algorithm is specified but hash value is in incorrect npm · undici 2024-04-04 low3.9 CVE-2024-30260 Undici's Proxy-Authorization header not cleared on cross-origin redirect for dispatch, request, stream, pipeline npm · undici 2024-04-04 low3.9 CVE-2024-24758 Undici proxy-authorization header not cleared on cross-origin redirect in fetch npm · undici 2024-02-16 low3.9 CVE-2023-45143 Undici's cookie header not cleared on cross-origin redirect in fetch npm · undici 2023-10-12 low3.7 CVE-2022-31151 undici before v5.8.0 vulnerable to uncleared cookies on cross-host / cross-origin redirect npm · undici 2022-07-21 low3.5 CVE-2021-21298 Node-Red is a low-code programming for event-driven applications built using nodejs. npm · @node-red/runtime 2021-02-26 low3.7 CVE-2020-11080 In nghttp2 before version 1.41.0, the overly large HTTP/2 SETTINGS frame payload causes denial of service. nghttp2 · nghttp2, debian · debian_linux, opensuse · leap +7 2020-06-03 low3.1 CVE-2017-15897 Node.js had a bug in versions 8.X and 9.X which caused buffers to not be initialized when the encoding for the fill value did not match the encoding specified. nodejs · node.js 2017-12-11

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.