undici vulnerable to downstream response desynchronization via retry interceptor
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| undici | undici | unaffected |
|
Configuration 1 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Hardened Images | |||
| nodejs26-main-26.5.1-1.5.hum1 | cpe:/a:redhat:hummingbird:1 | RHSA-2026:48273 | 2026-07-29T00:00:00Z |
| nodejs24-main-24.18.1-0.1.hum1 | cpe:/a:redhat:hummingbird:1 | RHSA-2026:48537 | 2026-07-30T00:00:00Z |
| Vendor | Product | Versions | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Undici | Undici |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-8xcm-r25x-g524 | undici vulnerable to downstream response desynchronization via retry interceptor |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.288% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Redhat
Redhat hummingbird |
|
| CPEs | cpe:/a:redhat:hummingbird:1 | |
| Vendors & Products |
Redhat
Redhat hummingbird |
|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Undici
Undici undici |
|
| Vendors & Products |
Undici
Undici undici |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | undici vulnerable to downstream response desynchronization via retry interceptor | |
| Weaknesses | CWE-444 | |
| References |
| |
| Metrics |
cvssV3_1
|