CVE-2026-48932
published 2026-09-01CVE-2026-48932: 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…
PriorityP417low3.7CVSS 3.0
AVNACHPRNUINSUCNILAN
EPSS
0.17%
6.7th percentile
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
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| nodejs | node | 22.22.3 – 22.22.3 | — |
| nodejs | node | 24.16.0 – 24.16.0 | — |
| nodejs | node | 26.3.0 – 26.3.0 | — |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
Node.js prior 22.22.3/24.16.0/26.3.0 HTTP Client improper synchronization (Nessus ID 343404)
vuldb·2026-09-07·CVSS 3.7
CVE-2026-48932 [LOW] Node.js prior 22.22.3/24.16.0/26.3.0 HTTP Client improper synchronization (Nessus ID 343404)
A vulnerability was found in Node.js. It has been rated as problematic. This affects an unknown part of the component HTTP Client. Performing a manipulation results in improper synchronization.
This vulnerability is cataloged as CVE-2026-48932. It is possible to initiate the attack remotely. There is no exploit available.
Upgrading the affected component is advised.
GHSA
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 origi
ghsa_unreviewed·2026-09-01
CVE-2026-48932 [LOW] CWE-444 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 origi
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**.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2026-09-01
Published