--- id: "VND-nodejs-july-2025-security-releases" kind: "vulnerability" aliases: [] title: "Node.js: Tuesday, July 15, 2025 Security Releases" severity: "high" cvss: null epss: null exploited: false status: "open" category: "runtime" products: [{"name": "node", "fixed": ["20.19.4"], "affected": ">= 20.0.0, < 20.19.4", "ecosystem": "node"}, {"name": "node", "fixed": ["22.17.1"], "affected": ">= 22.0.0, < 22.17.1", "ecosystem": "node"}, {"name": "node", "fixed": ["24.4.1"], "affected": ">= 24.0.0, < 24.4.1", "ecosystem": "node"}] ecosystems: ["node"] tags: ["backend", "node", "node.js", "runtime", "self-hosted", "windows"] not_affected_if: ["end-of-life-not-applicable"] published_at: "2025-07-15T00:00:00+00:00" first_seen_at: "2026-10-23T19:13:00+00:00" updated_at: "2026-10-25T05:39:27+00:00" sources: [{"source": "nodejs", "url": "https://nodejs.org/en/blog/vulnerability/july-2025-security-releases", "first_seen_at": "2026-10-23T19:13:00+00:00"}] --- # Node.js: Tuesday, July 15, 2025 Security Releases Two issues in Node.js affect the 20.x, 22.x and 24.x release lines. A Windows device-name flaw (CON, PRN, AUX) can bypass path traversal protection in path.normalize() and path.join, and a V8 string hashing regression in 24.x re-enables hash collision denial of service. _Summary, check and fix written by a model from the sources; labelled as such._ ## Affected - node:node affected >= 20.0.0, < 20.19.4 fixed 20.19.4 - node:node affected >= 22.0.0, < 22.17.1 fixed 22.17.1 - node:node affected >= 24.0.0, < 24.4.1 fixed 24.4.1 ## How to check - Run `node --version` and compare against the fixed versions `20.19.4`, `22.17.1` and `24.4.1` - Check whether the application passes user-controlled paths to `path.join` or `path.normalize` on Windows - For HashDoS, check whether an attacker can control strings that the application hashes on `24.x` releases ## Fix - Upgrade Node.js 20.x to `20.19.4` or later - Upgrade Node.js 22.x to `22.17.1` or later - Upgrade Node.js 24.x to `24.4.1` or later ## Timeline - 2026-10-23T19:13:00+00:00 nodejs https://nodejs.org/en/blog/vulnerability/july-2025-security-releases ## From the sources Commercial support for versions past the Maintenance LTS phase is available through our OpenJS Ecosystem Sustainability Program partners Tuesday, July 15, 2025 Security Releases TNJP The Node.js Project Tuesday, July 15, 2025 Security Releases Security releases available Updates are now available for the 24.x, 22.x, 20.x Node.js release lines for the following issues. Windows Device Names (CON, PRN, AUX) Bypass Path Traversal Protection in path.normalize() (CVE-2025-27210) - (high) An incomplete fix has been identified for CVE-2025-23084 in Node.js, specifically affecting Windows device names like CON, PRN, and AUX. This vulnerability affects Windows users of path.join API. Impact: This vulnerability affects all users in active release lines: 20.x, 22.x, 24.x Thank you, to oblivionsage for reporting this vulnerability and thank you RafaelGSS for fixing it. HashDoS in V8 (CVE-2025-27209) - (high) The V8 release used in Node.js v24.0.0 has changed how string hashes are computed using rapidhash. This implementation re-introduces the HashDoS vulnerability as an attacker who can control the strings to be hashed can generate many hash collisions - an attacker can generate collisions even without knowing the hash-seed. While the V8 team does not classify this as a security vulnerability, the Node.js project considers it one due to its potential impact in real-world scenarios. This vulnerability affects Node.js v24.x users. Impact: This vulnerability affects all users in active release lines: 24.x Thank you, to sharp_edged for reporting this vulnerability and thank you targos for fixing it. Downloads and release details Node.js v20.19.4 Node.js v22.17.1 Node.js v24.4.1 Summary The Node.js project will release new versions of the 24.x, 22.x, 20.x releases lines on or shortly after, Tuesday, July 15, 2025 in order to address: 2 high severity issues. Impact The 24.x release line of Node.js is vulnerable to 2 high severity issues. The 22.x release line of Node.js is vulnerable to 1 high severity issues. The 20.x release line of Node.js is vulnerable to 1 high 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, Tuesday, July 15, 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, January 13, 2026 Security Releases Next Wednesday, May 14, 2025 Security Releases --- _Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_