CVE-2026-78660

Awaiting Analysis Awaiting Analysis - Queue

BaseFortify

Publication date: 2026-10-08

Last updated on: 2026-10-09

Assigner: Go Project

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-10-08

Last Modified

2026-10-09

Generated

2026-10-19

AI Q&A

2026-10-09

EPSS Evaluated

2026-10-18

NVD

CVE-2026-78660

Affected Vendors & Products

Vendor	Product	Version / Range
Go	standard	library net/http 0
Go	standard	library net/http/internal/http2 1.27.0-0
golang.org/x/net	golang.org/x/net/http2	0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-444	The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.

Attack-Flow Graph

Executive Summary

This vulnerability involves improper handling of malformed HTTP/2 framing-related headers in Go's HTTP/2 implementation. When acting as a reverse proxy, the system may forward responses with such headers to an HTTP/1 client. If the HTTP/1 client also has lax parsing, this can lead to response smuggling, where malicious responses are injected into legitimate traffic.

Detection Guidance

This vulnerability involves HTTP/2 header smuggling when acting as a reverse proxy. Detection requires inspecting HTTP/2 to HTTP/1.1 header translation for malformed framing headers. Monitor for inconsistent responses between HTTP/2 and HTTP/1.1 endpoints. Check proxy logs for header anomalies or smuggling attempts.

Impact Analysis

This vulnerability could allow attackers to smuggle malicious responses through your systems, potentially leading to data breaches, unauthorized access, or misdirection of users to malicious content. It primarily affects systems using Go's HTTP/2 implementation as a reverse proxy.

Compliance Impact

This vulnerability could lead to data breaches or unauthorized access, which may violate GDPR's data protection requirements or HIPAA's safeguards for protected health information. Compliance could be impacted if sensitive data is exposed or altered due to response smuggling.

Mitigation Strategies

Update the Go standard library and golang.org/x/net/http2 to the latest patched versions to address the HTTP/2 response smuggling issue.

Hi! I’m here to help you understand CVE-2026-78660. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70