Findings

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 · corrected/updated Oct 16, 2026 · golang go · evidence confidence high

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.

Grounded briefings

Catalog interpretations for three audiences. Each brief cites ingested metadata and the original advisories below. They are not independent research and they do not invent exploit steps.

Executive

CVE-2026-33814 is a high public vulnerability record for golang go. It is not currently listed in the CISA Known Exploited catalog. Check the linked vendor or CERT advisories for patch status. This summary is a catalog interpretation of the ingested metadata and cites the original advisories below.

System administrator

Identify whether golang go is in your estate, then compare installed versions with the affected ranges. Affected packages or ranges on record: golang.org/x/net (0 → 0.53.0); stdlib (0 → 1.25.10); golang/go; golang/http2. Check the linked vendor or CERT advisories for patch status. Prefer the vendor or distribution advisory linked in Sources before changing production systems. This is a catalog interpretation, not a runbook.

Security analyst

Signals on file: CVSS 7.5, EPSS 0.8%. It is not currently listed in the CISA Known Exploited catalog. Weakness classes: CWE-606, CWE-835. Sources contributing to this record: cve_org, epss, nvd, osv. Public exploit references, when present, are outbound links only and are not proof of active exploitation. This is a catalog interpretation of stored metadata.

Exploitation and remediation

  • Exploitation evidence

    Not listed as known exploited in CISA KEV. Not in the CISA KEV catalog.

  • Patch and remediation

    No required-action text is stored yet. Use the vendor or CERT links in Sources for patch availability.

  • Safe detection guidance

    Compare installed versions with the affected ranges below and verify the advisory from the original publisher. This site stores metadata and outbound links only; it does not ship exploit code or proof-of-concept payloads.

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. May 7, 2026 · OSV.dev

    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 · OSV.dev

    Fix available

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

  3. Oct 15, 2026 · OSV.dev

    Fix available

    golang.org/x/net fixed in 0.53.0

  4. Oct 15, 2026 · OSV.dev

    Fix available

    stdlib fixed in 1.25.10

  5. Oct 15, 2026 · OSV.dev

    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 · OSV.dev

    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.

Affected

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

Sources

  • CVE.orgVulnerability recordCVE-2026-33814

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-33814

    30-day exploitation probability 0.8%

    first.org
  • 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
  • OSV.devPackage 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