CVE-2026-48932: CWE-444 HTTP Request Smuggling in nodejs node
Description
A flaw in Node.js HTTP client can cause a request desynchronization for Node.js-based forwarding proxies that rebuild outbound headers from the visible `IncomingMessage` headers while piping the original body to a reused backend connection. Node.js can omit headers beyond `maxHeadersCount` / `maxHeaderPairs` from `req.headers`, `req.rawHeaders`, and `req.headersDistinct`, while still using those omitted headers internally for HTTP message framing. In particular, `Content-Length` can be hidden from userland while the request body is still delivered. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
CVSS v3.0
Score 3.7low
Affected software
nodejs
node
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability involves a flaw in the Node.js HTTP client where headers exceeding maxHeadersCount or maxHeaderPairs limits are omitted from user-accessible header objects (req.headers, req.rawHeaders, req.headersDistinct) but remain internally used for HTTP message framing. This discrepancy can cause request desynchronization in forwarding proxies that reconstruct outbound headers from visible headers but pipe the original body to reused backend connections. The hidden Content-Length header can lead to HTTP request smuggling attacks. The issue affects Node.js versions 22.22.3, 24.16.0, and 26.3.0.
Potential Impact
The vulnerability can lead to HTTP request smuggling due to request desynchronization, potentially allowing an attacker to interfere with the HTTP request processing in Node.js-based forwarding proxies. However, the CVSS score of 3.7 and the low severity rating indicate limited impact, with no confidentiality or availability impact and only low integrity impact. There are no known exploits in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or temporary mitigation is currently documented. Users should monitor Node.js vendor advisories for updates addressing this issue.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- hackerone
- Date Reserved
- 2026-05-26T15:00:06.427Z
- Cvss Version
- 3.0
- State
- PUBLISHED
Threat ID: 6a963a79acd9273b491bc8b5
Added to database: 09/01/2026, 02:37:45 UTC
Last enriched: 09/07/2026, 14:52:03 UTC
Last updated: 10/16/2026, 18:48:21 UTC
Views: 118
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.