CISA list

● Branch of Node.js

Node.js 24

Node.js 24 gets security fixes only, until 30 April 2028. Update to 24.22.3.

Data: .

Fix releases of Node.js 24

Releases that end an affected range of a CVE record, newest first. A release gets a page when it fixes three or more records, or one that CISA lists or that EPSS rates 0.50 or more. Records this page cannot place on a branch, counted on the page of the platform, are not in it.
ReleaseFixesSigns of exploitation
24.4.12 CVE records1 record with a public exploit

Records with no fixed release for 24

These records name the branch as affected and name no release that ends the range.

Records with no fixed release for 24
RecordSigns of exploitationFixed in
CVE-2026-48933A flaw in Node.js WebCrypto implementation can crash the process if the input of `subtle.encrypt()` is a multiple of 2GiB. This vulnerability affects all supported release lines: **Node.js 22**…7.5 High · published 26 June 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-48618A 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 and verifier hostname normalization…7.7 High · published 26 June 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-105483A 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 host is written with non-ASCII characters…7.4 High · published 23 October 2026NoneThe record names no fixed release for 26 and 24.
CVE-2025-55130A flaw in Node.js’s Permissions model allows attackers to bypass `--allow-fs-read` and `--allow-fs-write` restrictions using crafted relative symlink paths. By chaining directories and symlinks, a…7.1 High · published 20 January 2026NoneThe record names no fixed release for 25, 24, 22 and 20.
CVE-2026-106072A 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, such as…6.7 Medium · published 23 October 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-105482A 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 CVE-2026-48930, which…7.4 High · published 23 October 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-56848A 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. This…7.5 High · published 4 August 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-56846A 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** and **22.x**.7.5 High · published 4 August 2026NoneThe record names no fixed release for 24 and 22.
CVE-2026-48937A 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 22** and **Node.js…5.3 Medium · published 18 June 2026NoneThe record names no fixed release for 24 and 22.
CVE-2026-48619A 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 all supported…5.3 Medium · published 26 June 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-106074A flaw in Node.js `crypto` causes the internal entropy caches used by `crypto.randomUUID()`, `crypto.randomUUIDv7()`, and `crypto.randomInt()` to be saved into user-land startup snapshots…4.8 Medium · published 23 October 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-106073A flaw in Node.js Permission Model filesystem enforcement leaves `fs.realpathSync()` without the required read permission checks. This is an incomplete fix of CVE-2026-21715, which only covered…3.3 Low · published 23 October 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-106069A 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, when the host is a non-canonical IPv4…7.4 High · published 23 October 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-105481A 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. This is an incomplete fix of CVE-2026-48931. The…6.5 Medium · published 23 October 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-58045A flaw in Node.js allows a spoofed `TypedArray` `byteLength` to trigger a reachable assertion in the synchronous `node:zlib` APIs, causing the entire process to crash. All 11 synchronous zlib…6.2 Medium · published 4 August 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-58044A flaw in Node.js HTTP client can cause a request desynchronization for Node.js-based forwarding proxies that rebuild outbound headers from the visible `IncomingMessage` headers while piping the…3.7 Low · published 4 August 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-58043A flaw in Node.js Permission Model enforcement can over-grant filesystem access across radix-tree prefix boundaries. Under `--permission`, an attacker who is granted access to one path can abuse…7.5 High · published 30 July 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-58042A 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 denial of service…5.9 Medium · published 4 August 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-58041A flaw in Node.js node:sqlite allows a stale StatementSyncIterator created through DatabaseSync#createTagStore() to continue executing a cached prepared statement after it has been reset and rebound…5.3 Medium · published 4 August 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-58040An incomplete fix has been identified in Node.js: HTTPS Agent TLS session reuse skips hostname verification across identity policies (incomplete fix of CVE-2026-48934). This vulnerability affects…6.3 Medium · published 30 July 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-58039A flaw in Node.js Permission Model enforcement allows process.report writes (and overwrites) files outside --allow-fs-write paths. This can lead to confidentiality impact or bypass of the intended…3.3 Low · published 31 July 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-56850A 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 requests configured with different client…4.1 Medium · published 30 July 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-56847A flaw in Node.js Permission Model enforcement allows `trace_events.createTracing().enable()` Writes Trace Logs Outside `--allow-fs-write`. This can lead to confidentiality impact or bypass of the…3.3 Low · published 30 July 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-48935A 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. `--allow-fs-read`. This vulnerability affects all supported release…3.3 Low · published 26 June 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-48934A flaw in Node.js TLS host verification can cause an attacker to bypass certification validation. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and…4.3 Medium · published 26 June 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-48932A flaw in Node.js HTTP client can cause a request desynchronization for Node.js-based forwarding proxies that rebuild outbound headers from the visible `IncomingMessage` headers while piping the…3.7 Low · published 1 September 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-48931A 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. This vulnerability affects all supported release lines: **Node.js…3.7 Low · published 22 June 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-48930A 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. This vulnerability affects all…5.6 Medium · published 26 June 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-48928A inconsistency in Node.js hostname matching can cause a trust-policy bypass in multi-context mTLS setups. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and…4.2 Medium · published 26 June 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-48617A flaw in Node.js Permission Model enforcement allows Bypass via `process.report.writeReport()` Path Misvalidation. This can lead to confidentiality impact or bypass of the intended security…1.8 Low · published 18 June 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-48615A 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 be exposed through…5.9 Medium · published 26 June 2026NoneThe record names no fixed release for 26, 24 and 22.
CVE-2026-21716An incomplete fix for CVE-2024-36137 leaves `FileHandle.chmod()` and `FileHandle.chown()` in the promises API without the required permission checks, while their callback-based equivalents…3.3 Low · published 30 March 2026NoneThe record names no fixed release for 25, 24, 22 and 20.
CVE-2026-21714A 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 value of 231-1. The…5.3 Medium · published 30 March 2026NoneThe record names no fixed release for 25, 24, 22 and 20.
CVE-2026-21712A flaw in Node.js URL processing causes an assertion failure in native code when `url.format()` is called with a malformed internationalized domain name (IDN) containing invalid characters, crashing…5.7 Medium · published 30 March 2026NoneThe record names no fixed release for 25 and 24.
CVE-2025-55132A flaw in Node.js's permission model allows a file's access and modification timestamps to be changed via `futimes()` even when the process has only read permissions. Unlike `utimes()`, `futimes()`…2.8 Low · published 20 January 2026NoneThe record names no fixed release for 25, 24, 22 and 20.

Node.js 24 in dates

WhatWhen
Released6 May 2025
Bug and security fixes end20 October 2026
Security fixes end30 April 2028
Newest release24.22.3 (11 November 2026)

More Node.js pages

What this page says

24.22.3 is the newest release of Node.js 24 that no CVE record we read names as affected.

A release is the fix of a record when the record's affected range for this branch ends before it. Dates are from the product lifecycle data credited under Sources.

Sources
  • CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
  • Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
  • EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)