CVE-2026-48932

published 1 Sep 2026 · updated 1 Sep 2026

A flaw in Node.js HTTP client can cause a request desynchronization for Node.js-based forwarding proxies that rebuild outbound headers from…

3.7LowCVSS 3.7EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
nodejs>=22.22.3 <=22.22.3, >=24.16.0 <=24.16.0, >=26.3.0 <=26.3.0

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-48932 severity on Zeptric[![CVE-2026-48932](https://zeptric.io/badge/cve/CVE-2026-48932.svg)](https://zeptric.io/cve/CVE-2026-48932)