Advisory record · GO-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

CVSS 7.5 HighEPSS 0.0084 · 58th percentile

Published by OSV at 7 May 2026, 19:21 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
golang.org/x/netGo<0.53.00.53.0
stdlibGo<1.25.10 || >=1.26.0-0, <1.26.31.25.10, 1.26.3
Identifiers
GO-2026-4918 · BIT-golang-2026-33814 · CVE-2026-33814
Weakness (CWE)
CWE-606
Published
7 May 2026
Updated
16 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The golang.org/x/net module before 0.53.0 and the Go standard library (versions before 1.25.10, and 1.26.0 up to 1.26.3) are affected. An HTTP/2 transport that receives a SETTINGS frame with SETTINGS_MAX_FRAME_SIZE set to 0 can enter an infinite loop while writing CONTINUATION frames. The source gives few details about how a remote peer would trigger this. Upgrade golang.org/x/net to 0.53.0 or later, and upgrade Go to 1.25.10 or 1.26.3.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H ADP (CISA-ADP)
  • CISA KEV Not listed.
  • EPSS 0.0084, the 58th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:12 UTC First seen by agentprime
  2. 31 Oct 2026, 14:12 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.