Vulnerabilities

Vulnerability · CVE-2026-78660

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

Published Oct 8, 2026 · catalog updated Oct 16, 2026 · HTTP/2 transport accepts malformed

Check if you run it

No confirmed exploitation is on record for CVE-2026-78660. EPSS is 0.30%. Act only if a listed version of HTTP/2 transport accepts malformed is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (HTTP/2 transport accepts malformed).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.30%
Remediation
Not established
Affected products
Bitnami golang · Go golang.org/x/net · Go stdlib

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Bitnami golang0 → 1.26.9
  • Go golang.org/x/net0 → 0.60.0
  • Go stdlib0 → 1.26.9
  • Go stdlib1.27.0-0 → 1.27.2

How to fix CVE-2026-78660

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-78660. EPSS is 0.30%. Act only if a listed version of HTTP/2 transport accepts malformed is installed.

Which versions are affected?

Compare what you have installed with 0 → 1.26.9, 0 → 0.60.0, 1.27.0-0 → 1.27.2. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.30%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 8, 2026 · OpenSSF OSV / OSV Scanner

    Detected

    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

  2. Oct 16, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    stdlib fixed in 1.26.9; stdlib fixed in 1.27.2; golang.org/x/net fixed in 0.60.0

  3. Oct 16, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    stdlib fixed in 1.26.9

  4. Oct 16, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    stdlib fixed in 1.27.2

  5. Oct 16, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    golang.org/x/net fixed in 0.60.0

  6. Oct 16, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    golang fixed in 1.26.9

  7. Oct 16, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    golang fixed in 1.26.9

  8. Oct 16, 2026 · OpenSSF OSV / OSV Scanner

    Updated

    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

Sources

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.