FlawAtlas
Search the atlas
CVE-2026-6733 Low

undici vulnerable to HTTP response queue poisoning via keep-alive socket reuse

## Impact Undici's HTTP/1.1 client is vulnerable to response queue poisoning on reused keep-alive sockets. An attacker-controlled upstream server can inject an unsolicited HTTP/1.1 response onto an idle socket after a request completes. When the client dispatches the next request on that socket, it associates the injected response with the new request, causing responses to be delivered to the wrong requests. This requires an attacker-controlled or compromised upstream HTTP/1.1 server and keep-alive connection reuse. ## Patches Upgrade to undici v6.27.0, v7.28.0 or v8.5.0. ## Workarounds Disable keep-alive connection reuse by setting `keepAliveTimeout: 0` on the Client or Pool.

Exploit probability 0.2%
Published June 19, 2026
Required by Not available
Last source change June 21, 2026

02 / AFFECTED SOFTWARE

Affected packages

Unknown Unknown

246 explicit affected versions

npm undici

03 / CONNECTIONS

Connected vulnerabilities

04 / EVIDENCE

Source records

Open Source Vulnerabilities CVE-2026-6733

Impact: Undici's HTTP/1.1 client is vulnerable to response queue poisoning on reused keep-alive sockets. An attacker-controlled upstream server can inject an unsolicited HTTP/1.1 response onto an idle socket after a request completes. When the client dispatches the next request on that socket, it associates the injected response with the new request, causing responses to be delivered to the wrong requests. This requires an attacker-controlled or compromised upstream HTTP/1.1 server and keep-alive connection reuse. Patches: Upgrade to undici v6.26.0, v7.28.0 or v8.5.0. Workarounds: Disable keep-alive connection reuse by setting keepAliveTimeout: 0 on the Client or Pool.

View original source
Open Source Vulnerabilities GHSA-35p6-xmwp-9g52

## Impact Undici's HTTP/1.1 client is vulnerable to response queue poisoning on reused keep-alive sockets. An attacker-controlled upstream server can inject an unsolicited HTTP/1.1 response onto an idle socket after a request completes. When the client dispatches the next request on that socket, it associates the injected response with the new request, causing responses to be delivered to the wrong requests. This requires an attacker-controlled or compromised upstream HTTP/1.1 server and keep-alive connection reuse. ## Patches Upgrade to undici v6.27.0, v7.28.0 or v8.5.0. ## Workarounds Disable keep-alive connection reuse by setting `keepAliveTimeout: 0` on the Client or Pool.

View original source

05 / REFERENCES

Further evidence