CVE-2026-21710: Vulnerability in nodejs node
CVE-2026-21710 is a high-severity vulnerability in Node. js HTTP request handling affecting versions 20. x, 22. x, 24. x, 25. x, and earlier major releases. The flaw triggers an uncaught TypeError when a request contains a header named '__proto__' and the application accesses req. headersDistinct. This occurs because the '__proto__' property resolves to Object. prototype instead of undefined, causing a push operation on a non-array.
AI Analysis
Technical Summary
This vulnerability in Node.js HTTP servers arises from improper handling of a header named '__proto__' in the req.headersDistinct property. Accessing this property leads to a TypeError because '__proto__' resolves to Object.prototype, causing a push method call on a non-array object. The exception is thrown synchronously within a property getter and bypasses error event listeners, making it difficult to handle without explicit try/catch blocks. Affected versions include all Node.js HTTP servers on 20.x, 22.x, 24.x, 25.x, and earlier major versions. The CVSS 3.0 score is 7.5, indicating high severity with network attack vector, low attack complexity, no privileges required, no user interaction, and impact limited to availability (denial of service). No official patch or vendor advisory is currently referenced.
Potential Impact
The vulnerability causes a denial of service condition by triggering an uncaught synchronous TypeError when processing HTTP requests with a '__proto__' header. This can crash or disrupt Node.js HTTP servers that access req.headersDistinct without proper error handling. There is no impact on confidentiality or integrity according to the CVSS vector. No known exploits in the wild have been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, applications should implement defensive coding by wrapping all accesses to req.headersDistinct in try/catch blocks to prevent unhandled exceptions. Avoid processing requests with suspicious '__proto__' headers if possible. Monitor official Node.js channels for updates and patches.
CVE-2026-21710: Vulnerability in nodejs node
Description
CVE-2026-21710 is a high-severity vulnerability in Node. js HTTP request handling affecting versions 20. x, 22. x, 24. x, 25. x, and earlier major releases. The flaw triggers an uncaught TypeError when a request contains a header named '__proto__' and the application accesses req. headersDistinct. This occurs because the '__proto__' property resolves to Object. prototype instead of undefined, causing a push operation on a non-array.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability in Node.js HTTP servers arises from improper handling of a header named '__proto__' in the req.headersDistinct property. Accessing this property leads to a TypeError because '__proto__' resolves to Object.prototype, causing a push method call on a non-array object. The exception is thrown synchronously within a property getter and bypasses error event listeners, making it difficult to handle without explicit try/catch blocks. Affected versions include all Node.js HTTP servers on 20.x, 22.x, 24.x, 25.x, and earlier major versions. The CVSS 3.0 score is 7.5, indicating high severity with network attack vector, low attack complexity, no privileges required, no user interaction, and impact limited to availability (denial of service). No official patch or vendor advisory is currently referenced.
Potential Impact
The vulnerability causes a denial of service condition by triggering an uncaught synchronous TypeError when processing HTTP requests with a '__proto__' header. This can crash or disrupt Node.js HTTP servers that access req.headersDistinct without proper error handling. There is no impact on confidentiality or integrity according to the CVSS vector. No known exploits in the wild have been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, applications should implement defensive coding by wrapping all accesses to req.headersDistinct in try/catch blocks to prevent unhandled exceptions. Avoid processing requests with suspicious '__proto__' headers if possible. Monitor official Node.js channels for updates and patches.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- hackerone
- Date Reserved
- 2026-01-04T15:00:06.574Z
- Cvss Version
- 3.0
- State
- PUBLISHED
Threat ID: 69cacda7e6bfc5ba1d6188a2
Added to database: 3/30/2026, 7:23:19 PM
Last enriched: 4/7/2026, 10:54:54 AM
Last updated: 5/15/2026, 7:54:44 AM
Views: 78
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.