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.
Published: 2026-10-08
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Remediation

No vendor fix or workaround currently provided.

Additional remediation guidance may be available on OpenCVE Cloud.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 09 Oct 2026 02:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-20

Thu, 08 Oct 2026 23:00:00 +0000

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

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: Go

Published:

Updated: 2026-10-08T22:53:59.334Z

Reserved: 2026-08-24T23:36:15.738Z

Link: CVE-2026-78660

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-08T23:17:03.510

Modified: 2026-10-08T23:17:03.510

Link: CVE-2026-78660

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-09T02:00:23Z

Weaknesses
  • CWE-20

    Improper Input Validation