Windows apps · Application version · March 24, 2026

Node.js 25.8.2

Node.js 25.8.2, released March 24, 2026, fixes 8 CVEs in Node.js. None of them is reported as exploited. Patch Radar priority: High. The latest Node.js is 26.12.1, which also fixes every one of these CVEs.

High

Superseded. The latest Node.js is 26.12.1, which also fixes every CVE on this page. Install that instead.

CVEs closed

None rated Critical

Exploited

None reported

Highest CVSS

7.5

Base score, 0 to 10

Highest EPSS

0.2544

97th percentile

Priority of the 8 CVEs

Patch now 0
                                Urgent 0
                                High 8
                                Routine 0

Applies to

Product	Version
Node.js	25.8.2

CVEs this fix closes

Priority	CVE	Title	CVSS	EPSS	Exploitation
High	CVE-2026-21710	A flaw in Node.js HTTP request handling causes an uncaught `TypeError` when a request is received with a header named `__proto__` and the application accesses `req.headersDistinct`. When this occurs, `dest["__proto__"]` resolves to `Object.prototype` rather than `undefined`, causing `.push()` to be called on a non-array. This exception is thrown synchronously inside a property getter and cannot be intercepted by `error` event listeners, meaning it cannot be handled without wrapping every `req.headersDistinct` access in a `try/catch`. * This vulnerability affects all Node.js HTTP servers on 20.x, 22.x, 24.x, and v25.x	7.5	0.2544	None reported
High	CVE-2026-21714	Node.js 14 and 15 others: Missing Release of Memory after Effective Lifetime	7.5	0.0043	None reported
High	CVE-2026-21713	Node.js 14 and 15 others: Observable Timing Discrepancy	7.5	0.0037	None reported
High	CVE-2026-21712	A 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 the Node.js process.	7.5	0.0033	None reported
High	CVE-2026-21717	A flaw in V8's string hashing mechanism causes integer-like strings to be hashed to their numeric value, making hash collisions trivially predictable. By crafting a request that causes many such collisions in V8's internal string table, an attacker can significantly degrade performance of the Node.js process. The most common trigger is any endpoint that calls `JSON.parse()` on attacker-controlled input, as JSON parsing automatically internalizes short strings into the affected hash table. This vulnerability affects 20.x, 22.x, 24.x, and 25.x.	7.5	0.0027	None reported
High	CVE-2026-21711	Node.js 14 and 12 others: Improper Access Control	7.5	0.0017	None reported
High	CVE-2026-21715	Node.js 14 and 15 others: Incorrect Permission Assignment for Critical Resource	7.5	0.0015	None reported
High	CVE-2026-21716	Node.js 14 and 15 others: Missing Authorization	7.5	0.0014	None reported

Other Node.js versions with security fixes

For tools and AI agents

This page as data: JSON · Markdown

Link to this page

If this page saved you time, a link to it in your ticket, advisory or write-up helps others find it.

HTML

<a href="https://patchblox.com/security/fix/windows-app/openjs.nodejs-25.8.2">Node.js 25.8.2 on Patchblox Patch Radar</a>

Reusing the data? How to credit Patch Radar.

Is it current everywhere?

Patchblox finds every install below the fixed version, including per-user copies, and updates them from a signed catalog package.

Get a demo

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.