CVE-2026-16728

published 29 Jul 2026 · updated 30 Jul 2026

undici vulnerable to downstream response desynchronization via retry interceptor

4.8MediumCVSS 4.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 6.28.0, 7.29.0 and 8.9.0.

undici's retry interceptor can deliver a response whose body length does not match the Content-Length header exposed to the application after a retry or resume of a partial response. In undici before 6.28.0, from 7.0.0 up to before 7.29.0, and from 8.0.0 up to before 8.9.0, a malicious or faulty upstream can return a partial response with a mismatched framing header, close the socket early, and have the retry interceptor assemble a body of a different length while the original Content-Length stays attached. Applications that use the retry interceptor and forward upstream headers and bodies downstream, such as proxies or gateways, may then emit an invalid HTTP response with a stale Content-Length, leading to downstream response desynchronization, connection hangs, or response corruption. Exploitation requires the retry interceptor enabled, an upstream returning a mismatched partial response, and a downstream forwarder that does not remove or recalculate Content-Length. The issue is fixed in undici 6.28.0, 7.29.0, and 8.9.0.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
undici<6.28.0, >=7.0.0 <7.29.0, >=8.0.0 <8.9.06.28.0, 7.29.0, 8.9.0

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

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