CVE-2026-78660

HTTP/2 transport accepts malformed framing-related headers in net/http

Published Oct 8, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such headers to an HTTP/1 client when acting as a reverse proxy. If the HTTP/1 client also does not behave strictly enough, this can result in response smuggling.

Analysis

AI-generated

Technical impact

This vulnerability resides in the Go HTTP/2 implementation. The framework allows malformed framing‑related headers because they cannot corrupt the HTTP/2 framing itself. When acting as a reverse proxy, the implementation forwards such headers to an HTTP/1 client. If that downstream client accepts the headers without strict validation, an attacker can craft responses that are split or merged in the HTTP/1 stream, leading to response smuggling. The flaw results from inadequate handling of malformed framing‑related headers (CWE‑444). The attacker can inject arbitrary data into the response, exposing confidential information or manipulating application behavior. The likely attack vector is an attacker sending a malicious HTTP/2 request with malformed framing‑related headers to a reverse proxy that forwards to an HTTP/1 client.

Affected Systems

The affected components are Go’s net/http, net/http/internal/http2, and golang.org/x/net/http2 packages. All Go releases compiled with these packages prior to the referenced fixes are vulnerable. No explicit version list is provided in the advisory.

Risk and Exploitability

The issue can be exploited only when an attacker can inject malformed headers into an HTTP/2 request that is then proxied to an HTTP/1 client and that client is permissive to header parsing. The EPSS score is <1% and the CVSS score is 7.5; the vulnerability is not listed in CISA’s KEV catalog. Based on the description, the exploit requires a specific proxy configuration and a vulnerable downstream client, so the likelihood of exploitation is low to moderate; however, the impact of a successful smuggle can be significant.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to the latest Go release that includes the fix referenced in the advisory
  • an upgrade is not immediately possible, disable HTTP/2 proxying or configure the proxy to strip framing‑related headers before forwarding
  • Ensure downstream HTTP/1 clients enforce strict header validation to prevent response smuggling

Generated by OpenCVE AI on October 9, 2026 at 20:23 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
Weaknesses CWE-20
Type Values Removed Values Added
Weaknesses CWE-444
Metrics cvssV3_1

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

ssvc

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

Type Values Removed Values Added
First Time appeared Go Standard Library
Go Standard Library net/http
Go Standard Library net/http2
Vendors & Products Go Standard Library
Go Standard Library net/http
Go Standard Library net/http2
Type Values Removed Values Added
Weaknesses CWE-20
Type Values Removed Values Added
Description Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such headers to an HTTP/1 client when acting as a reverse proxy. If the HTTP/1 client also does not behave strictly enough, this can result in response smuggling.
Title HTTP/2 transport accepts malformed framing-related headers 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:23 PM
Reserved
Aug 24, 2026, 11:36 PM
Status
Awaiting Analysis
Published
Oct 8, 2026, 11:17 PM
Modified
Oct 9, 2026, 5:16 PM