Skip to main content
VulnerabilityPublished Updated

CVE-2026-21710: nodejs node · Unthrottled Resource Allocation

Affects nodejs nodeSource CVE Database V5

0
Compare

Not known to be exploited · 25% EPSS · CVSS 7.5 High · fixed in 26.0.0 : patch nodejs node soon.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.0 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
25.4% chance of exploitation in 30 days – higher than 97% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 26.0.0, 25.0.0, 23.0.0 +1
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade nodejs node to 26.0.0, 25.0.0, 23.0.0 or 21.0.0.

Affected software

ProductAffectedFixed in
nodejsnodeAffected
  • 4.0 – 19.0
  • >=20.20.1 <=20.20.1
  • >=22.22.1 <=22.22.1
  • >=24.14.0 <=24.14.0
  • >=25.8.1 <=25.8.1
16 affected builds
Fixed in–
npmnodepkg:npm/nodeOther threatsAffected
  • >=20.0.0 <21.0.0
  • >=22.0.0 <23.0.0
  • >=24.0.0 <25.0.0
  • >=25.0.0 <26.0.0
Fixed in
  • 21.0.0
  • 23.0.0
  • 25.0.0
  • 26.0.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Red Hat has released security updates addressing this vulnerability in their Node.js packages. Applying the official patches from Red Hat advisories (e.g., RHSA-2026:7310 and related errata) will remediate the issue. Until patched, applications can mitigate the impact by wrapping all accesses to req.headersDistinct in try/catch blocks, though this is a workaround rather than a full fix. Users should consult the Red Hat advisories for detailed update instructions and apply the updates promptly.

Description

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**

References

Community reviews

Loading reviews…