Skip to content

Node.js · product

Node

144 CVEs

Every dot is a CVE in what this vendor ships; the named ones are the most at risk.

likely to be exploited
21

Every one of the 144 is a mark on the map. Named now: 79 to 104, most at risk first.

  1. The implementation of realpath in libuv < 10.22.1, < 12.18.4, and < 14.9.0 used within Node.js incorrectly determined the buffer size which can result in a buffer overflow if the…CVE-2020-8252NodeJS · 0.7% likely

    CWE-1201 bounty report

  2. We have identified a bug in Node.js error handling where "Maximum call stack size exceeded" errors become uncatchable when `async_hooks.createHook()` is enabled. Instead of reachi…CVE-2025-59466nodejs · CVSS 5.9 · 0.7% likely

    CWE-2481 bounty report

  3. 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. This vulnerability affects…CVE-2026-48619nodejs · CVSS 5.3 · 0.6% likelycovered by CyberSIXT

    CWE-4001 bounty report

  4. 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-canonical IPv4 spelling, s…CVE-2026-106072nodejs · CVSS 6.7 · 0.6% likely

    CWE-2951 bounty report

  5. A vulnerability has been identified in Node.js version 20, affecting users of the experimental permission model when the --allow-fs-read flag is used with a non-* argument. This f…CVE-2023-30582NodeJS · CVSS 5.3 · 0.6% likely

    CWE-2841 bounty report

  6. A flaw in Node.js HTTP/2 handling allows `nghttp2_session_mem_send()` to be called re-entrantly while `nghttp2_session_mem_recv()` is executing, resulting in a heap-use-after-free…CVE-2026-56848nodejs · CVSS 7.5 · 0.6% likelycovered by CyberSIXT

    CWE-4161 bounty report1 article

  7. A flaw in Node.js HTTP/2 server API can cause servers to keep accepting data even after sending a `GOAWAY` frame. This vulnerability affects two supported release lines: **Node.js…CVE-2026-48937nodejs · CVSS 5.3 · 0.6% likely

    CWE-4001 bounty report

  8. On Linux, Node.js ignores certain environment variables if those may have been set by an unprivileged user while the process is running with elevated privileges with the only exce…CVE-2024-21892NodeJS · CVSS 7.5 · 0.6% likely

    CWE-2691 bounty report

  9. A flaw in Node.js HTTP/2 handling can cause HTTP/2 retained header blocks evade maxSessionMemory and enable remote memory exhaustion. This vulnerability affects Node.js **24.x** a…CVE-2026-56846nodejs · CVSS 7.5 · 0.6% likely

    CWE-4001 bounty report

  10. In Node.js, the `ReadFileUtf8` internal binding leaks memory due to a corrupted pointer in `uv_fs_s.file`: a UTF-16 path buffer is allocated but subsequently overwritten when the…CVE-2025-23165nodejs · CVSS 3.7 · 0.6% likely

    CWE-4011 bounty report

  11. Node.js is vulnerable to a heap buffer overflow in HTTP/2 session.altsvc() via a long originCVE-2026-123828nodejs · CVSS 5.9 · 0.5% likelycovered by CyberSIXT

    CWE-1221 article1 article this week: Node.js fixes HTTP/2 and TLS flaws exposing data and keys

  12. Node.js is vulnerable to an HTTP/2 memory and file-descriptor leak via a protocol error during session shutdownCVE-2026-123865nodejs · CVSS 7.5 · 0.5% likelycovered by CyberSIXT

    CWE-4002 articles2 articles this week: Node.js fixes 16 flaws exposing servers to crashes and data leaks

  13. A flaw in Node.js 20's HTTP parser allows improper termination of HTTP/1 headers using `\r\n\rX` instead of the required `\r\n\r\n`. This inconsistency enables request smuggling,…CVE-2025-23167nodejs · CVSS 6.5 · 0.5% likely

    CWE-4441 bounty report

  14. The Permission Model assumes that any path starting with two backslashes \ has a four-character prefix that can be ignored, which is not always true. This subtle bug leads to vuln…CVE-2024-37372NodeJS · CVSS 3.6 · 0.5% likely

    CWE-221 bounty report

  15. Node.js is vulnerable to HTTP/2 response memory disclosure via a use-after-free during stream teardownCVE-2026-123866nodejs · CVSS 7.5 · 0.5% likelycovered by CyberSIXT

    CWE-4161 bounty report2 articles2 articles this week: Node.js fixes 16 flaws exposing servers to crashes and data leaks

  16. Node.js is vulnerable to an HTTP/2 use-after-free via respondWithFile() stream reset during a pending writeCVE-2026-123874nodejs · CVSS 7.5 · 0.5% likelycovered by CyberSIXT

    CWE-4162 articles2 articles this week: Node.js fixes 16 flaws exposing servers to crashes and data leaks

  17. 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(). This is an incomplete fix of CV…CVE-2026-105482nodejs · CVSS 7.4 · 0.5% likelycovered by CyberSIXT

    CWE-2841 bounty report1 article

  18. Node.js is vulnerable to a remote HTTP/2 denial of service via a reachable assertion in Http2Session teardownCVE-2026-123863nodejs · CVSS 8.2 · 0.5% likelycovered by CyberSIXT

    CWE-6172 articles2 articles this week: Node.js fixes 16 flaws exposing servers to crashes and data leaks

  19. A vulnerability has been identified in Node.js, affecting users of the experimental permission model when the --allow-fs-read flag is used. This flaw arises from an inadequate per…CVE-2024-22018NodeJS · CVSS 2.9 · 0.5% likely

    1 bounty report

  20. An untrusted search path vulnerability exists in Node.js. <19.6.1, <18.14.1, <16.19.1, and <14.21.3 that could allow an attacker to search and potentially load ICU data when runni…CVE-2023-23920NodeJS · CVSS 4.2 · 0.5% likely

    CWE-4261 bounty report

  21. A memory leak occurs in Node.js HTTP/2 servers when a client sends WINDOW_UPDATE frames on stream 0 (connection-level) that cause the flow control window to exceed the maximum val…CVE-2026-21714nodejs · CVSS 5.3 · 0.4% likely

    CWE-4011 bounty report

  22. With the aid of the diagnostics_channel utility, an event can be hooked into whenever a worker thread is created. This is not limited only to workers but also exposes internal wor…CVE-2025-23083NodeJS · CVSS 7.7 · 0.4% likely

    CWE-2841 bounty report

  23. A flaw in Node.js can cause dns.resolveAny() Aborts the Node.js Process When a DNS Response Contains More Than 256 A Records. Repeated triggering of this condition can lead to den…CVE-2026-58042nodejs · CVSS 5.9 · 0.4% likely

    CWE-4001 bounty report

  24. A flaw in Node.js proxy tunnel error handling could expose proxy credentials in `ERR_PROXY_TUNNEL` error messages. When proxy credentials are embedded in the proxy URL, they may b…CVE-2026-48615nodejs · CVSS 5.9 · 0.4% likelycovered by CyberSIXT

    CWE-3591 bounty report

  25. Node.js is vulnerable to an HTTP/2 memory exhaustion denial of service via unaccounted inbound DATA on an undrained streamCVE-2026-123868nodejs · CVSS 5.9 · 0.4% likelycovered by CyberSIXT

    CWE-4001 article1 article this week: Node.js fixes HTTP/2 and TLS flaws exposing data and keys

  26. Node.js is vulnerable to an HTTP/2 denial of service via a NULL pointer dereference when a respondWithFile() download is cancelledCVE-2026-123875nodejs · CVSS 5.9 · 0.4% likelycovered by CyberSIXT

    CWE-4761 article1 article this week: Node.js fixes 16 flaws exposing servers to crashes and data leaks

exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it

Zoom in on the map and the dots under the middle of it are named where they are.

Data as of 2026-11-15. CVE List through 2026-11-15 · EPSS of 2026-11-14 · CISA KEV checked 2026-11-15. Sources: the CVE List, CISA KEV, EPSS, NVD, nuclei templates and public bug bounty data.