CVE Intelligence
High Denial of service

CVE-2026-21710 — Allocation of Resources Without Limits or Throttling in Nodejs Node

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

Published Mar 30, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: hackerone

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 25% (30-day exploitation probability)+15
  • Technical severity (high)+6
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
25.04%
ahead of 98% of scored CVEs · Oct 14, 2026
Affects
Nodejs
Node and 3 more
CVSS base
7.5
High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Nodejs Node, Nodejs Node.js, Red Hat Enterprise Linux…).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. EPSS ahead of 98% of scored CVEs: prioritize it in the patch queue.
  5. Search available logs for exploit probes matching the vulnerability class (denial of service), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Nodejs Node ≥ 5.0 and < 5.*≥ 19.0 and < 19.*≥ 18.0 and < 18.*≥ 17.0 and < 17.*≥ 16.0 and < 16.*≥ 15.0 and < 15.*≥ 14.0 and < 14.*≥ 13.0 and < 13.*
and 12 more ≥ 12.0 and < 12.*≥ 11.0 and < 11.*≥ 10.0 and < 10.*≥ 9.0 and < 9.*≥ 8.0 and < 8.*≥ 7.0 and < 7.*≥ 6.0 and < 6.*≥ 4.0 and < 4.*≥ 25.8.1 and ≤ 25.8.1≥ 24.14.0 and ≤ 24.14.0≥ 22.22.1 and ≤ 22.22.1≥ 20.20.1 and ≤ 20.20.1
Vulnerable CVE Program (cve.org) e CISA ADP
Nodejs Node.js ≥ 25.0.0 and ≤ 25.8.1≥ 24.0.0 and ≤ 24.14.0≥ 22.0.0 and ≤ 22.22.1≤ 20.20.1 Vulnerable NIST National Vulnerability Database
Red Hat Enterprise Linux version 8.0version 10.0version 9.0 Vulnerable NIST National Vulnerability Database
Red Hat Enterprise Linux Eus version 10.0version 9.6version 9.4 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.5 CVSS 3.1 High 3.9 3.6 0b0ca135-0b70-47e7-9f44-1890c2a1c46c via NIST National Vulnerability Database
7.5 CVSS 3.0 High 3.9 3.6 support@hackerone.com via NIST National Vulnerability Database
7.5 CVSS 3.0 High — — hackerone via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (score shown at the top: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-770 · Allocation of Resources Without Limits or Throttling

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 25.04%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Track CPU/memory spikes and availability drops correlated with request patterns.
web/proxy/WAF logsnetwork IDS/IPSresource metrics

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · nodejs/node
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 7.5
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    Mar 30, 2026 · hackerone

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

16 on the record

Elsewhere on this site

Nodejs
every CVE for this vendor
Denial of service
same class
CWE-770
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-104045 Sssd: sssd: denial of service via race condition in autofs responder 9d
  • CVE-2026-104046 Sssd: sssd: denial of service via incomplete identity provider authentication requests 9d
  • CVE-2026-104047 Sssd: sssd: information disclosure via query injection in entra id lookups 9d
  • CVE-2026-104048 Sssd: sssd: authorization bypass via cross-domain username collision in hbac evaluation 9d
  • CVE-2026-102558 Libsoup: libsoup: heap buffer overflow during websocket receive-buffer growth 16d
  • CVE-2026-102555 Libsoup: libsoup: heap buffer overflow via uninitialized length in data-uri base64 decoding 16d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-21710 is "Allocation of Resources Without Limits or Throttling in Nodejs Node", rated High. It affects Node (Nodejs); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. EPSS 25.04% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.