Skip to main content
VulnerabilityPublished Updated

CVE-2026-33814: golang.org/x/net/http2 · Infinite Loop

Affects golang.org/x/net/http2Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 0.53.0 soon.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 58% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.53.0, 1.26.3, 1.25.10
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade golang.org/x/net/http2 to 0.53.0; net/http to 1.26.3 or 1.25.10.

Affected software

ProductAffectedFixed in
golang.org/x/netgolang.org/x/net/http2Affected
  • <0.53.0
Fixed in
  • 0.53.0
Go standard librarynet/httpAffected
  • >=1.26.0-0 <1.26.3
Fixed in
  • 1.26.3
Go standard librarynet/httpAffected
  • <1.25.10
Fixed in
  • 1.25.10
Gogolang.org/x/net/http2pkg:golang/golang.org/x/net/http2Other threatsAffected
  • =0
Fixed in–
Gogolang.org/x/net/http2pkg:golang/golang.org/x/net/http2Other threatsAffected
  • <0.53.0
Fixed in
  • 0.53.0
Gonet/httppkg:golang/net/httpOther threatsAffected
  • <1.25.10
  • >=1.26.0-0 <1.26.3
Fixed in
  • 1.25.10
  • 1.26.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

According to the Red Hat advisory, no mitigation or official fix meeting their criteria for ease of use, deployment, and stability is currently available. No temporary workarounds are provided.

Description

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.

References

Community reviews

Loading reviews…