Threat Feed

CVE-2026-56866: HTTP/1 client connection desynchronization after CONNECT rejection in net/http

Exploitation: None known · CVSS 7.5 High · Unauthenticated · Published 2026-10-08

Description

When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle pool. Because CONNECT requests do not have a request body, the server may interpret the trailing body bytes as a subsequent pipelined HTTP/1.1 request on the connection, leaving the pooled connection desynchronized and causing the next caller that reuses it to read the response to the injected request. In reverse proxies (including httputil.ReverseProxy) that forward CONNECT requests through a shared Transport, this can lead to cross-user response poisoning.

Fix

No fixed version in the CVE record yet. Follow the vendor advisory.

Affected versions

ProductVulnerableFixed in
net/http0 before 1.26.9Not listed
net/http1.27.0-0 before 1.27.2Not listed
net/http/httputil0 before 1.26.9Not listed
net/http/httputil1.27.0-0 before 1.27.2Not listed

Seen in 2 sources