Advisory

GO-2026-6605

Also known as: BIT-golang-2026-56866, CVE-2026-56866

Summary

HTTP/1 client connection desynchronization after CONNECT rejection in net/http

Details

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.

Severity

Not rated by the source.

Dates

Published
2026-10-08 22:31 UTC
Modified
2026-11-14 13:12 UTC

Affected packages and fixes

stdlib

Go · All systems

Affected

  • introduced 0, fixed 1.26.9, introduced 1.27.0-0, fixed 1.27.2 (semver)

Fixed versions

1.26.9, 1.27.2

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: Go Vulnerability Database · CC BY 4.0

Sources & licences