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 request body to a backend connection. This issue may result in the unintended omission of critical headers, such as `Content-Length`, potentially causing data integrity issues. Organizations using Node.js versions 22, 24, or 26, particularly those implementing forwarding proxies, should prioritize addressing this vulnerability to mitigate potential disruptions in HTTP request handling.
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**.