ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-78669

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

Published Oct 8, 2026 · catalog updated Oct 16, 2026 · Excessive CPU consumption from

Check if you run it

No confirmed exploitation is on record for CVE-2026-78669. EPSS is 0.57%. Act only if a listed version of Excessive CPU consumption from is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Excessive CPU consumption from).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Unknown—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.57%
Remediation
Not established
Affected products
Go golang.org/x/net · Go stdlib

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Go golang.org/x/net0 → 0.60.0
  • Go stdlib0 → 1.26.9
  • Go stdlib1.27.0-0 → 1.27.2

How to fix CVE-2026-78669

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-78669. EPSS is 0.57%. Act only if a listed version of Excessive CPU consumption from is installed.

Which versions are affected?

Compare what you have installed with 0 → 0.60.0, 0 → 1.26.9, 1.27.0-0 → 1.27.2. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.57%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 8, 2026 · Go Vulnerability Database

    Detected

    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.

  2. Oct 16, 2026 · Go Vulnerability Database

    Fix available

    stdlib fixed in 1.26.9; stdlib fixed in 1.27.2; golang.org/x/net fixed in 0.60.0

  3. Oct 16, 2026 · Go Vulnerability Database

    Fix available

    stdlib fixed in 1.26.9

  4. Oct 16, 2026 · Go Vulnerability Database

    Fix available

    stdlib fixed in 1.27.2

  5. Oct 16, 2026 · Go Vulnerability Database

    Fix available

    golang.org/x/net fixed in 0.60.0

  6. Oct 16, 2026 · Go Vulnerability Database

    Updated

    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.

Sources

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.