golang.org/x/net · Go · published 2026-05-07

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

Routine No exploitation evidence; EPSS 0.8%.

CVE-2026-33814 is not known to be exploited in the wild. EPSS estimates a 0.8% chance of exploitation in the next 30 days, higher than 58% of all CVEs. This Go vulnerability: CVSS 7.5 (v3.1), attacks can be automated. Fixed upstream in Go 1.26.3, 1.25.10. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Go 1.26.3, 1.25.10.

Patch events

  1. This monthSecurity release

    Language runtimeGo

    Go security releases: 1.26.3, 1.25.10

    Upgrade to 1.26.31.25.10

    Why: Vendor security release for server software (most severe: CVE-2026-33811).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.8% (59th pct)FIRST EPSS v2026.06.15
CVSS base score7.5 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableYesCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →