CVE-2026-18540: undici vulnerable to downstream response splitting via retry interceptor
Impact Undici's interceptors.retry() can resume a request after a partial response and append the resumed bytes to an already partially delivered body, while the application still receives the original response's status and headers. When that response carried a Content-Length, the application can receive a longer body.
Published Sep 29, 2026
Affected packages
undici
- Ecosystem
- npm
- Affected
- < 6.28.1
- Fixed in
- 6.28.1
- Check
npm ls undici
undici
- Ecosystem
- npm
- Affected
- >= 7.0.0, < 7.29.1
- Fixed in
- 7.29.1
- Check
npm ls undici
undici
- Ecosystem
- npm
- Affected
- >= 8.0.0, < 8.10.2
- Fixed in
- 8.10.2
- Check
npm ls undici
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
Undici's interceptors.retry() can resume a request after a partial response and append the resumed bytes to an already partially delivered body, while the application still receives the original response's status and headers. When that response carried a Content-Length, the application can receive a longer body. Applications that forward Undici's status, headers, and body downstream without recalculating framing, for example proxy or gateway applications, may emit a response whose body exceeds the forwarded Content-Length, and the excess bytes can be read as the start of a subsequent HTTP response (downstream response splitting or desynchronization).
For example, a 404 Not Found with Content-Length: 2 that sends one byte then closes can be resumed with an open-ended Range request, and the resumed 206 Partial Content bytes are appended, so the application receives more than two body bytes while still seeing Content-Length: 2. The bug requires interceptors.retry() enabled, an attacker-controlled or faulty upstream, and a downstream forwarder that does not recalculate Content-Length.
Patches
Patched in undici v6.28.1, v7.29.1, and v8.10.2. Upgrade to one of these or later.
Workarounds
- Disable
interceptors.retry()for untrusted upstreams, or setmaxRetries: 0. - Remove or recalculate
Content-Lengthbefore forwarding a response body assembled by Undici.
Credited to samuel871211, mcollina, UlisesGascon.
References
- https://github.com/nodejs/undici/security/advisories/GHSA-r53p-7pc4-xj5r
- https://nvd.nist.gov/vuln/detail/CVE-2026-18540
- https://github.com/nodejs/undici/commit/0160a719063fb0a77f4fdf9500b9166b91e14329
- https://github.com/nodejs/undici/commit/cd8af90b38ae33c2838d54a2d629774122effe95
- https://github.com/nodejs/undici/commit/ce31bc824b578008faae5d3350da66c1b5f71548
- https://hackerone.com/reports/3900104
- https://hackerone.com/reports/3900615
- https://cna.openjsf.org/security-advisories.html
- https://github.com/nodejs/undici/releases/tag/v6.28.1
- https://github.com/nodejs/undici/releases/tag/v7.29.1
- https://github.com/nodejs/undici/releases/tag/v8.10.2
- https://github.com/advisories/GHSA-r53p-7pc4-xj5r
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-109383
undici vulnerable to TLS certificate validation bypass via dropped tls options in Agent
high7.4Oct 27, 2026CVE-2026-109829
undici vulnerable to cache poisoning and cross-user disclosure via cross-origin redirects
high7.4Oct 27, 2026CVE-2026-109855
undici WebSocket client vulnerable to Denial of Service via failed HTTP/2 handshake
high7.5Oct 27, 2026CVE-2026-109932
undici WebSocket client vulnerable to Denial of Service via unbounded automatic PONG buffering
medium5.9Oct 27, 2026CVE-2026-87018
undici vulnerable to Denial of Service via TLS 1.2 certificate-changing renegotiation
high7.5Oct 27, 2026CVE-2026-87029
undici vulnerable to Denial of Service via unhandled exception in the decompress interceptor
medium5.9Oct 27, 2026
