BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-21710High confidence

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`

nodejs · node

7.5HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Critical, raised one band.upgradedsince 5 Oct 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 25.04% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs nodejs node and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

8 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · mainnodejsVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.24.14.1-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · mainnodejsVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.22.22.2-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.21v3.21 · mainnodejsVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.22.22.2-r0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourcenodejsVendor fix publishedDebian records a fixed source-package version for this release.20.19.2+dfsg-1+deb13u2Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcenodejsVendor fix publishedDebian records a fixed source-package version for this release.18.20.4+dfsg-1~deb12u2Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcenodejsVendor fix publishedDebian records a fixed source-package version for this release.22.22.2+dfsg+~cs22.19.15-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcenodejsVendor fix publishedDebian records a fixed source-package version for this release.22.22.2+dfsg+~cs22.19.15-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivenodejsUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-21710 · CSAF 2.0 · revision 23 · interimSUSE Product Security TeamCVE-2026-21710
144 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • nodejs10 as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • nodejs10-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • nodejs10-docs as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • nodejs8 as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • nodejs8-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • nodejs8-docs as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • npm10 as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • npm8 as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • nodejs10 as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • nodejs10-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • nodejs10-docs as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • nodejs12 as component of SUSE Linux Enterprise High Performance Computing 15 SP2
Summary
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**
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-17170

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

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

What

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

Why

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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

Why

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Allocation of Resources Without Limits or Throttling → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-770 ↗

CWE-770: Allocation of Resources Without Limits or Throttling. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-770
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-0843Node.js: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Node.js ausnutzen, um einen Denial of Service zu verursachen, Sicherheitsmaßnahmen zu umgehen und Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260401Security Bulletin 01 Apr 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 01 Apr 2026, published on 1 April 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0917Multiples vulnérabilités dans Oracle PeopleSoft

d?id=CVE-2025-55130 Référence CVE CVE-2025-55131 https://www.cve.org/CVERecord?id=CVE-2025-55131 Référence CVE CVE-2025-55132 https://www.cve.org/CVERecord?id=CVE-2025-55132 Référence CVE CVE-2025-59465 https://www.cve.org/CVERecord?id=CVE-2025-59465 Référence CVE CVE-2025-59466 https://www.cve.org/CVERecord?id=CVE-2025-59466 Référence CVE CVE-2025-66021 https://www.cve.org/CVERecord?id=CVE-2025-66021 Référence CVE CVE-2025-68431 https://www.cve.org/CVERecord?id=CVE-2025-68431 Référence CVE CVE-2026-21636 https://www.cve.org/CVERecord?id=CVE-2026-21636 Référence CVE CVE-2026-21637 https://www.cve.org/CVERecord?id=CVE-2026-21637 Référence CVE CVE-2026-21710 https://www.cve.org/CVERecord?id=CVE-2026-21710 Référence CVE CVE-2026-47015 https://www.cve.org/CVERecord?id=CVE-2026-47015 Référence CVE CVE-2026-47017 https://www.cve.org/CVERecord?id=CVE-2026-47017 Référence CVE CVE-2026-47024 https://www.cve.org/CVERecord?id=CVE-2026-47024 Référence CVE CVE-2026-47026 https://www.cve.org/CVERecord?id=CVE-2026-47026 Référence CVE CVE-2026-47048 https://www.cve.org/CVERecord?id=CVE-2026-47048 Référence CVE CVE-2026-47049 https://www.cve.org/CVERecord?id=CVE-2026-47049 Référence CVE CVE-2026-47051 https://www.cve.org/CVERecord?id=CVE-2026-47051 Référence CVE CVE-2026-60152 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0796Multiples vulnérabilités dans Tenable Identity Exposure

ord?id=CVE-2025-69418 Référence CVE CVE-2025-69419 https://www.cve.org/CVERecord?id=CVE-2025-69419 Référence CVE CVE-2025-69420 https://www.cve.org/CVERecord?id=CVE-2025-69420 Référence CVE CVE-2025-69421 https://www.cve.org/CVERecord?id=CVE-2025-69421 Référence CVE CVE-2026-13007 https://www.cve.org/CVERecord?id=CVE-2026-13007 Référence CVE CVE-2026-1965 https://www.cve.org/CVERecord?id=CVE-2026-1965 Référence CVE CVE-2026-21218 https://www.cve.org/CVERecord?id=CVE-2026-21218 Référence CVE CVE-2026-21262 https://www.cve.org/CVERecord?id=CVE-2026-21262 Référence CVE CVE-2026-21637 https://www.cve.org/CVERecord?id=CVE-2026-21637 Référence CVE CVE-2026-21710 https://www.cve.org/CVERecord?id=CVE-2026-21710 Référence CVE CVE-2026-21713 https://www.cve.org/CVERecord?id=CVE-2026-21713 Référence CVE CVE-2026-21714 https://www.cve.org/CVERecord?id=CVE-2026-21714 Référence CVE CVE-2026-21715 https://www.cve.org/CVERecord?id=CVE-2026-21715 Référence CVE CVE-2026-21716 https://www.cve.org/CVERecord?id=CVE-2026-21716 Référence CVE CVE-2026-21717 https://www.cve.org/CVERecord?id=CVE-2026-21717 Référence CVE CVE-2026-22795 https://www.cve.org/CVERecord?id=CVE-2026-22795 Référence CVE CVE-2026-22796 https://www.cve.org/CVERecord?id=CVE-2026-22796 Référence CVE CVE-2026-26130 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0627Multiples vulnérabilités dans les produits Splunk

VERecord?id=CVE-2026-1225 Référence CVE CVE-2026-1584 https://www.cve.org/CVERecord?id=CVE-2026-1584 Référence CVE CVE-2026-1605 https://www.cve.org/CVERecord?id=CVE-2026-1605 Référence CVE CVE-2026-1861 https://www.cve.org/CVERecord?id=CVE-2026-1861 Référence CVE CVE-2026-20238 https://www.cve.org/CVERecord?id=CVE-2026-20238 Référence CVE CVE-2026-20239 https://www.cve.org/CVERecord?id=CVE-2026-20239 Référence CVE CVE-2026-20240 https://www.cve.org/CVERecord?id=CVE-2026-20240 Référence CVE CVE-2026-21441 https://www.cve.org/CVERecord?id=CVE-2026-21441 Référence CVE CVE-2026-21637 https://www.cve.org/CVERecord?id=CVE-2026-21637 Référence CVE CVE-2026-21710 https://www.cve.org/CVERecord?id=CVE-2026-21710 Référence CVE CVE-2026-21712 https://www.cve.org/CVERecord?id=CVE-2026-21712 Référence CVE CVE-2026-21713 https://www.cve.org/CVERecord?id=CVE-2026-21713 Référence CVE CVE-2026-21714 https://www.cve.org/CVERecord?id=CVE-2026-21714 Référence CVE CVE-2026-21715 https://www.cve.org/CVERecord?id=CVE-2026-21715 Référence CVE CVE-2026-21716 https://www.cve.org/CVERecord?id=CVE-2026-21716 Référence CVE CVE-2026-21717 https://www.cve.org/CVERecord?id=CVE-2026-21717 Référence CVE CVE-2026-21925 https://www.cve.org/CVERecord?id=CVE-2026-21925 Référence CVE CVE-2026-21932 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0436Multiples vulnérabilités dans Tenable Identity Exposure

ord?id=CVE-2025-55130 Référence CVE CVE-2025-55131 https://www.cve.org/CVERecord?id=CVE-2025-55131 Référence CVE CVE-2025-55132 https://www.cve.org/CVERecord?id=CVE-2025-55132 Référence CVE CVE-2025-59465 https://www.cve.org/CVERecord?id=CVE-2025-59465 Référence CVE CVE-2025-59466 https://www.cve.org/CVERecord?id=CVE-2025-59466 Référence CVE CVE-2026-1965 https://www.cve.org/CVERecord?id=CVE-2026-1965 Référence CVE CVE-2026-21218 https://www.cve.org/CVERecord?id=CVE-2026-21218 Référence CVE CVE-2026-21262 https://www.cve.org/CVERecord?id=CVE-2026-21262 Référence CVE CVE-2026-21637 https://www.cve.org/CVERecord?id=CVE-2026-21637 Référence CVE CVE-2026-21710 https://www.cve.org/CVERecord?id=CVE-2026-21710 Référence CVE CVE-2026-21713 https://www.cve.org/CVERecord?id=CVE-2026-21713 Référence CVE CVE-2026-21714 https://www.cve.org/CVERecord?id=CVE-2026-21714 Référence CVE CVE-2026-21715 https://www.cve.org/CVERecord?id=CVE-2026-21715 Référence CVE CVE-2026-21716 https://www.cve.org/CVERecord?id=CVE-2026-21716 Référence CVE CVE-2026-21717 https://www.cve.org/CVERecord?id=CVE-2026-21717 Référence CVE CVE-2026-23941 https://www.cve.org/CVERecord?id=CVE-2026-23941 Référence CVE CVE-2026-23942 https://www.cve.org/CVERecord?id=CVE-2026-23942 Référence CVE CVE-2026-23943 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0406Multiples vulnérabilités dans les produits Microsoft

De multiples vulnérabilités ont été découvertes dans les produits Microsoft. Elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-029198Node.js Foundation等の複数ベンダの製品における複数の脆弱性

Node.jsのHTTPリクエスト処理における欠陥により、リクエストヘッダーに「__proto__」という名前のヘッダーが含まれ、かつアプリケーションが `req.headersDistinct` にアクセスした際に、未捕捉の `TypeError` が発生します。この現象が起きると、`dest["__proto__"]` は `undefined` ではなく `Object.prototype` と解決され、その結果、配列でないものに対して `.push()` が呼び出されます。この例外はプロパティゲッター内で同期的にスローされるため、`error` イベントリスナーで捕捉できず、すべての `req.headersDistinct` へのアクセスを `try/catch` でラップしなければ例外処理ができません。この脆弱性は、**20.x、22.x、24.x、v25.x** のすべてのNode.js HTTPサーバーに影響を及ぼします。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
RHSA-2026:7310: Red Hat Enterprise Linux AppStream EUS (v. 10.0)
Action
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 30 Mar 2026 · Last source change 15 Jul 2026, 01:19 UTC · CWE-770 · Allocation of Resources Without Limits or Throttling

CVE recordCVE.org · 5.2
CVSS sourceOther authority
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-17170
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCISA ADP
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    SUSE Product Security Team ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: nodejs.org/march-2026-security-releases.
    Before
    no authoritative guidance recorded
    After
    vendor advisory: nodejs.org/march-2026-security-releases
    support@hackerone.com ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Remediation guidance recorded
ENISA EUVD · EUVD-2026-17170↗SUSE Product Security Team security advisory↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-21710 · cve.blacktree.nl