Live › vulnerability › VND-nodejs-may-2025-security-releases
Go to dashboardA flaw in SignTraits::DeriveBits() can throw an exception from a background thread based on user-supplied input, crashing the Node.js process (CVE-2025-23166, high). The May 2025 releases also fix an llhttp header-termination bug enabling request smuggling on Node.js 20 and a Windows memory leak in ReadFileUtf8 (CVE-2025-23167 medium, CVE-2025-23165 low).
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:13 UTC. All times on this page are UTC.
Any server running an affected Node.js release that performs async cryptographic operations on input an outside party can supply can be crashed remotely. The request smuggling issue applies only to Node.js 20.x HTTP servers behind proxies that rely on access controls, and the ReadFileUtf8 leak applies only to Windows systems using that API on v20 and v22.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| node | node | >= 20.0.0, < 20.19.2 | 20.19.2 |
| node | node | >= 22.0.0, < 22.15.1 | 22.15.1 |
| node | node | >= 23.0.0, < 23.11.1 | 23.11.1 |
| node | node | >= 24.0.0, < 24.0.2 | 24.0.2 |
node --version and compare against the fixed lines: 20.19.2, 22.15.1, 23.11.1, 24.0.2.crypto.subtle or crypto functions on untrusted input.20.19.2 on the 20.x line, 22.15.1 on 22.x, 23.11.1 on 23.x, or 24.0.2 on 24.x.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Commercial support for versions past the Maintenance LTS phase is available through our OpenJS Ecosystem Sustainability Program partners Wednesday, May 14, 2025 Security Releases TNJP The Node.js Project Wednesday, May 14, 2025 Security Releases Security releases available Updates are now available for the 24.x, 23.x, 22.x, 20.x Node.js release lines for the following issues. Improper error handling in async cryptographic operations crashes process (CVE-2025-23166) - (high) The C++ method SignTraits::DeriveBits() may incorrectly call ThrowException() based on user-supplied inputs when executing in a background thread, crashing the Node.js process. Such cryptographic operations are commonly applied to untrusted inputs. Thus, this mechanism potentially allows an adversary to remotely crash a Node.js runtime. Impact: This vulnerability affects all users in active release lines: 20.x, 22.x, 23.x, 24.x Thank you, @panva and @tniessen, for reporting and fixing this vulnerability. Improper HTTP header block termination in llhttp (CVE-2025-23167) - (medium) 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, allowing attackers to bypass proxy-based access controls and submit unauthorized requests. The issue was resolved by upgrading llhttp to version 9, which enforces correct header termination. Impact: This vulnerability affects only Node.js 20.x users prior to the llhttp v9 upgrade. Thank you, to kenballus for reporting this vulnerability and thank you RafaelGSS for fixing it. Corrupted pointer in node::fs::ReadFileUtf8(const FunctionCallbackInfo<Value>& args) when args[0] is a string. (CVE-2025-23165) - (low) 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 file descriptor is set. This results in an unrecoverable memory leak on every call. Repeated use can cause unbounded memory growth, leading to a denial of service. Impact: This vulnerability affects Windows systems relying on the ReadFileUtf8 API on Node.js release lines: v20 and v22. Thank you, to Justin Nietzel for reporting and fixing this vulnerability. Downloads and release details Node.js v20.19.2 Node.js v22.15.1 Node.js v23.11.1 Node.js v24.0.2 Summary The Node.js project will release new versions of the 24.x, 23.x, 22.x, 20.x releases lines on or shortly after, Wednesday, May 14, 2025 in order to address: 1 high severity issues. 1 medium severity issues. 1 low severity issues. Impact The 24.x release line of Node.js is vulnerable to 1 high severity issues. The 23.x release line of Node.js is vulnerable to 1 high severity issues. The 22.x release line of Node.js is vulnerable to 1 low severity issues, 1 high severity issues. The 20.x release line of Node.js is vulnerable to 1 low severity issues, 1 high severity issues, 1 medium severity issues. It's important to note that End-of-Life versions are always affected when a security release occurs. To ensure your system's security, please use an up-to-date version as outlined in our Release Schedule . Release timing Releases will be available on, or shortly after, Wednesday, May 14, 2025. Contact and future updates The current Node.js security policy can be found at https://nodejs.org/en/security/ . Please follow the process outlined in https://github.com/nodejs/node/blob/master/SECURITY.md if you wish to report a vulnerability in Node.js. Subscribe to the low-volume announcement-only nodejs-sec mailing list at https://groups.google.com/forum/#!forum/nodejs-sec to stay up to date on security vulnerabilities and security-related releases of Node.js and the projects maintained in the nodejs GitHub organization. Previous Tuesday, July 15, 2025 Security Releases Next Node.js Test CI Security Incident
This page as .md · .json · in your agent: get_signal("VND-nodejs-may-2025-security-releases")