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

Advisory record · `GO-2026-4918`

- **Identifiers:** `GO-2026-4918` · `BIT-golang-2026-33814` · `CVE-2026-33814`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-606](https://cwe.mitre.org/data/definitions/606.html)
- **Tags:** [CWE-606](https://agentprime.io/advisories/tag/cwe-606.md)
- **Published:** 7 May 2026
- **Updated:** 16 Oct 2026
- **Reviewed by a person:** No

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.

## Affected packages

- `golang.org/x/net` (Go): affected `<0.53.0`; fixed in `0.53.0`
- `stdlib` (Go): affected `<1.25.10 || >=1.26.0-0, <1.26.3`; fixed in `1.25.10`, `1.26.3`

## 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

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`, from 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

- 31 Oct 2026, 14:12 UTC: First seen by agentprime
- 31 Oct 2026, 14:12 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GO-2026-4918)

## Sources

- [OSV: GO-2026-4918](https://osv.dev/vulnerability/GO-2026-4918)
- <https://go.dev/cl/761581>
- <https://go.dev/cl/761640>
- <https://groups.google.com/g/golang-announce/c/qcCIEXso47M>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GO-2026-4918>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GO-2026-4918/>. Everything for agents: <https://agentprime.io/llms.txt>.