CVE-2026-58044
published 2026-08-04CVE-2026-58044: 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…
PriorityP418low3.7CVSS 3.0
AVNACHPRNUINSUCNILAN
EPSS
0.30%
22.9th 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
5 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| nodejs | node | 22.23.1 – 22.23.1 | — |
| nodejs | node | 24.18.0 – 24.18.0 | — |
| nodejs | node | 26.5.0 – 26.5.0 | — |
| nodejs_22 | nodejs | — | — |
| nodejs_24 | nodejs | — | — |
CVSS provenance
nvdv3.03.7LOWCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
vendor_redhat3.7LOW
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 up to 22.23.1/24.18.0/26.5.0 HTTP Client improper synchronization
vuldb·2026-08-04·CVSS 3.7
CVE-2026-58044 [LOW] Node.js up to 22.23.1/24.18.0/26.5.0 HTTP Client improper synchronization
A vulnerability was found in Node.js up to 22.23.1/24.18.0/26.5.0. It has been classified as critical. The impacted element is an unknown function of the component HTTP Client. The manipulation leads to improper synchronization.
This vulnerability is listed as CVE-2026-58044. The attack may be initiated remotely. There is no available exploit.
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-08-04
CVE-2026-58044 [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**.
Red Hat
nodejs: Node.js: Request smuggling via HTTP client header truncation
vendor_redhat·2026-08-04·CVSS 3.7
CVE-2026-58044 [LOW] CWE-444 nodejs: Node.js: Request smuggling via HTTP client header truncation
nodejs: Node.js: Request smuggling via HTTP client header truncation
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**.
A flaw was found in Node.js. The Node.js HTTP client can cause a r
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2026-58044 nodejs24: Node.js: Request smuggling via HTTP client header truncation [fedora-all]
bugzilla·2026-08-10·CVSS 3.7
CVE-2026-58044 [LOW] CVE-2026-58044 nodejs24: Node.js: Request smuggling via HTTP client header truncation [fedora-all]
CVE-2026-58044 nodejs24: Node.js: Request smuggling via HTTP client header truncation [fedora-all]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
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, `Conten
Bugzilla
CVE-2026-58044 nodejs22: Node.js: Request smuggling via HTTP client header truncation [fedora-all]
bugzilla·2026-08-10·CVSS 3.7
CVE-2026-58044 [LOW] CVE-2026-58044 nodejs22: Node.js: Request smuggling via HTTP client header truncation [fedora-all]
CVE-2026-58044 nodejs22: Node.js: Request smuggling via HTTP client header truncation [fedora-all]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
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, `Conten
Bugzilla
CVE-2026-58044 nodejs: Node.js: Request smuggling via HTTP client header truncation
bugzilla·2026-08-04·CVSS 3.7
CVE-2026-58044 [LOW] CVE-2026-58044 nodejs: Node.js: Request smuggling via HTTP client header truncation
CVE-2026-58044 nodejs: Node.js: Request smuggling via HTTP client header truncation
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**.
2026-08-04
Published