CVE-2026-78669

Excessive CPU consumption from repeated initial window changes in net/http

Published Oct 8, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values.

Analysis

AI-generated

Technical impact

A malicious HTTP/2 peer can exhaust a client or server’s CPU by opening many streams and repeatedly sending small SETTINGS frames that alter the SETTINGS_INITIAL_WINDOW_SIZE. The result is a significant increase in processing load without advancing data transfer, effectively denying service. The weakness is a form of uncontrolled resource consumption flaw.

Affected Systems

Go’s standard library packages net/http, net/http/internal/http2, and the golang.org/x/net/http2 package are affected. No specific version ranges are listed, so any deployment using these packages may be susceptible.

Risk and Exploitability

Because the vulnerability is triggered by crafted HTTP/2 traffic, the attack vector is network. The CVSS score is 7.5. The EPSS score is 0.227%, indicating a very low probability of exploitation observed publicly; however, the vulnerability is not listed in the CISA KEV catalog, and a low EPSS does not imply the issue is benign. Deployments that rely on HTTP/2 for client‑server communication could experience sudden CPU spikes if an attacker opens many streams or injects frequent SETTINGS frames. More detailed risk assessment should consider whether HTTP/2 is enabled and whether external traffic is restricted. The impact is potentially high, especially in environments where service availability is critical.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to a Go release that includes the fix referenced by the Go issue and code reviews (e.g., the changes introduced in commits https://go.dev/cl/847186 and https://go.dev/cl/847308).
  • If the application does not require HTTP/2, disable the protocol on servers by setting the appropriate configuration flag or API call to prevent the vulnerability from being exploitable.
  • Configure HTTP/2 connection limits—such as setting MaxStreamWindowSize, MaxConcurrentStreams, or other stream‑management parameters—to constrain resource usage and mitigate abnormal SETTINGS frame traffic.

Generated by OpenCVE AI on October 9, 2026 at 19:07 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8935-1 Go vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-405
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-770
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Important

Type Values Removed Values Added
First Time appeared Go Standard Library
Go Standard Library net/http
Go Standard Library net/http2
Vendors & Products Go Standard Library
Go Standard Library net/http
Go Standard Library net/http2
Type Values Removed Values Added
Description A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values.
Title Excessive CPU consumption from repeated initial window changes in net/http
References
Weaknesses
  • CWE-405

    Asymmetric Resource Consumption (Amplification)

  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
Go
Published
Updated
Oct 9, 2026, 4:32 PM
Reserved
Aug 24, 2026, 11:36 PM
Status
Awaiting Analysis
Published
Oct 8, 2026, 11:17 PM
Modified
Oct 9, 2026, 5:16 PM
Severity
Important
Public date
Oct 8, 2026, 10:53 PM