CVE-2026-94439

HTTP/1 server connection desynchronization after 2xx CONNECT response in net/http

Published Oct 8, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
When an HTTP server handler sends a 2xx response to an HTTP/1 CONNECT request and returns without hijacking the connection, the server improperly continues to read and serve requests from the connection. Since a 2xx response to an HTTP/1 CONNECT converts the connection into a tunnel, the server should not treat the connection as continuing to contain HTTP. The impact of this misbehavior is mostly limited to potential request smuggling, where an intermediate proxy considers the data on the connection to be tunneled and the server considers it to be HTTP.

Analysis

AI-generated

Technical impact

A Go net/http server that returns a 2xx response to an HTTP/1 CONNECT request without hijacking the underlying connection incorrectly continues to parse and serve HTTP requests on the same socket. Because a 2xx CONNECT normally turns the connection into a raw tunnel, the server should stop HTTP framing. The retained framing can create a desynchronization that allows an attacker to smuggle a request through an intermediate proxy where the connection is treated as a tunnel. The weakness is a protocol parsing and synchronization fault (CWE-444).

Affected Systems

The affected package is the Go standard library’s net/http. The bug is tracked under GO-2026-6613 and applies to any Go release that has not yet incorporated that issue fix. No specific version numbers are listed, so all vulnerable deployments should verify whether the GO-2026-6613 change is present.

Risk and Exploitability

The CVSS score of 7.5 indicates high severity. EPSS score is < 1% and the vulnerability is not listed in the CISA KEV catalog, suggesting limited known exploitation. Exploitation requires a client or intermediate proxy that can issue a CONNECT to the vulnerable server and then send data that the server will misinterpret as HTTP after a 2xx response. While active attacks are not well documented, the potential for request smuggling could let an attacker bypass proxy filtering or redirect traffic unnoticed, especially in environments where proxy and application server expectations differ.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to a Go release that includes the GO-2026-6613 fix.
  • If an upgrade cannot be performed immediately, block or reject HTTP/1 CONNECT methods at perimeter firewalls, reverse proxies, or application firewalls to prevent tunnel establishment.
  • Ensure any handler that replies with a 2xx CONNECT promptly hijacks or closes the underlying connection, for example by invoking ResponseWriter.Hijack and then exiting the handler.

Generated by OpenCVE AI on October 9, 2026 at 18:41 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8935-1 Go vulnerabilities
History
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}

Type Values Removed Values Added
Weaknesses CWE-151
CWE-665
Type Values Removed Values Added
Weaknesses CWE-151
CWE-665
Type Values Removed Values Added
First Time appeared Go Standard Library
Go Standard Library net/http
Vendors & Products Go Standard Library
Go Standard Library net/http
Type Values Removed Values Added
Weaknesses CWE-444
References
Metrics threat_severity

None

cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N'}

threat_severity

Moderate

Type Values Removed Values Added
Description When an HTTP server handler sends a 2xx response to an HTTP/1 CONNECT request and returns without hijacking the connection, the server improperly continues to read and serve requests from the connection. Since a 2xx response to an HTTP/1 CONNECT converts the connection into a tunnel, the server should not treat the connection as continuing to contain HTTP. The impact of this misbehavior is mostly limited to potential request smuggling, where an intermediate proxy considers the data on the connection to be tunneled and the server considers it to be HTTP.
Title HTTP/1 server connection desynchronization after 2xx CONNECT response in net/http
References
Weaknesses
  • CWE-444

    Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

Sources

Status
PUBLISHED
Assigner
Go
Published
Updated
Oct 9, 2026, 4:52 PM
Reserved
Sep 21, 2026, 4:43 PM
Status
Awaiting Analysis
Published
Oct 8, 2026, 11:17 PM
Modified
Oct 9, 2026, 5:16 PM
Severity
Moderate
Public date
Oct 8, 2026, 10:53 PM