ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-33814

Infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE in net/http/internal/http2 in golang.org/x/net

Published May 7, 2026 · catalog updated Oct 16, 2026 · Infinite loop in HTTP/2

Check if you run it

No confirmed exploitation is on record for CVE-2026-33814. EPSS is 0.78%. Act only if a listed version of Infinite loop in HTTP/2 is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Infinite loop in HTTP/2).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.78%
Remediation
Fix linked
Affected products
Go golang.org/x/net · Go stdlib · cpe golang/go · cpe golang/http2

When processing HTTP/2 SETTINGS frames, transport will enter an infinite loop of writing CONTINUATION frames if it receives a SETTINGS_MAX_FRAME_SIZE with a value of 0.

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.

  • Go golang.org/x/net0 → 0.53.0
  • Go stdlib0 → 1.25.10
  • cpe golang/goversion unspecified
  • cpe golang/http2version unspecified

How to fix CVE-2026-33814

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-33814. EPSS is 0.78%. Act only if a listed version of Infinite loop in HTTP/2 is installed.

Which versions are affected?

Compare what you have installed with 0 → 0.53.0, 0 → 1.25.10. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-606; CWE-835: Infinite Loop. EPSS 0.78%. 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.

Related Odoo Git fixes

Quoted Community commit messages that cite this CVE. Presence of a commit is not proof that every edition or backport includes the fix. Enterprise proprietary diffs are never shown here. Timeline

Timeline

Detection, updates, and resolution for this record.

  1. May 7, 2026 · OpenSSF OSV / OSV Scanner

    Detected

    When processing HTTP/2 SETTINGS frames, transport will enter an infinite loop of writing CONTINUATION frames if it receives a SETTINGS_MAX_FRAME_SIZE with a value of 0.

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

    Fix available

    golang.org/x/net fixed in 0.53.0; stdlib fixed in 1.25.10

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

    Fix available

    golang.org/x/net fixed in 0.53.0

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

    Fix available

    stdlib fixed in 1.25.10

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

    Updated

    When processing HTTP/2 SETTINGS frames, transport will enter an infinite loop of writing CONTINUATION frames if it receives a SETTINGS_MAX_FRAME_SIZE with a value of 0.

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

    Updated

    When processing HTTP/2 SETTINGS frames, transport will enter an infinite loop of writing CONTINUATION frames if it receives a SETTINGS_MAX_FRAME_SIZE with a value of 0.

Sources

  • CVE.orgVulnerability recordCVE-2026-33814

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-33814

    30-day exploitation probability 0.8%

    first.org
  • Go Vulnerability DatabasePackage advisoryGO-2026-4918

    Infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE in net/http/internal/http2 in golang.org/x/net

    osv.dev
  • NIST NVDVulnerability recordCVE-2026-33814

    When processing HTTP/2 SETTINGS frames, transport will enter an infinite loop of writing CONTINUATION frames if it receives a SETTINGS_MAX_FRAME_SIZE with a value of 0.

    nvd.nist.gov
  • OpenSSF OSV / OSV ScannerPackage advisoryGO-2026-4918

    Infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE in net/http/internal/http2 in golang.org/x/net

    osv.dev

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.