Go standard library · Go · published 2026-10-08

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

Routine No exploitation evidence; EPSS 0.6%.

CVE-2026-56866 is not known to be exploited in the wild. EPSS estimates a 0.6% chance of exploitation in the next 30 days, higher than 49% of all CVEs. This Go vulnerability: CVSS 7.5 (v3.1), attacks can be automated. Fixed upstream in Go 1.27.2, 1.26.9; Ubuntu and Red Hat Enterprise Linux still have unfixed releases. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Go 1.27.2, 1.26.9.

Linux distribution packages

If you run the distro’s package rather than an upstream build, this is the version to look for.

DistroReleasePackageStatus
Debian13 trixiegolang-1.24Won’t fix
12 bookwormgolang-1.19Won’t fix
Ubuntu (+27 more packages)26.04 LTSgolang-1.24No fix yet
24.04 LTSgolang-1.24No fix yet
22.04 LTSgolang-1.24No fix yet
Red Hat Enterprise Linux (+64 more packages)RHEL 10bootc-image-builderInvestigating
RHEL 10buildahInvestigating
RHEL 10butaneInvestigating
RHEL 10conmonNo fix yet
RHEL 10delveInvestigating
RHEL 10git-lfsInvestigating
RHEL 10go-fdo-clientInvestigating
RHEL 10go-fdo-serverInvestigating

From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.

Patch events

  1. This monthSecurity release

    Language runtimeGo

    Go security releases: 1.27.2, 1.26.9

    Upgrade to 1.27.21.26.9

    Why: Vendor security release for server software (most severe: CVE-2026-56857).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.6% (50th pct)FIRST EPSS v2026.06.15
CVSS base score7.5 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableYesCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →