CyberRota Analysis
AI-GeneratedA flaw in the Node.js HTTP client can lead to request desynchronization in Node.js-based forwarding proxies that reconstruct outbound headers from visible `IncomingMessage` headers while still sending the original body to a reused backend connection. This issue allows certain headers, such as `Content-Length`, to be omitted from userland access, potentially leading to unexpected behavior or security concerns. Organizations using Node.js versions 22, 24, or 26, particularly those implementing forwarding proxies, should prioritize addressing this vulnerability to ensure proper request handling and mitigate potential risks.
Original NVD 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**.