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.
CVE-2026-78669
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 7.5 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.6% (49th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-95426 (ENISA EUVD)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHmedium confidence
- EG Risk
- 49EG Risk 49/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity75% × 45%Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.6% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.6%
- EPSS %ILE
- 49th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.CISA-ADP (Vulnrichment) CVSS v3.1 · CVSS v3.1
- EG Likelihood
- 0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 8, 2026
Last Modified
October 9, 2026
Advisory Details (6)
Auto-updated Oct 9, 2026net/http: excessive CPU consumption from repeated initial window changes · Issue #81742 · golang/go · GitHub
https://go.dev/issue/81742Vendor Advisories for CVE-2026-78669(20)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:92859Red Hat Product SecurityHigh
Red Hat Security Advisory: Satellite 6.17 security update
- RHSA-2026:92861Red Hat Product SecurityCritical
Red Hat Security Advisory: Satellite 6.19 security update
- RHSA-2026:92858Red Hat Product SecurityHigh
Red Hat Security Advisory: Satellite 6.16 EUS security update
- RHSA-2026:92860Red Hat Product SecurityHigh
Red Hat Security Advisory: Satellite 6.18 security update
- RHSA-2026:92621Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.6 Product Security and Bug Fix Update
- RHSA-2026:92622Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.7 Product Security and Bug Fix Update
- RHSA-2026:92516Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat OpenShift Service Mesh 3.4.4
- RHSA-2026:92509Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat OpenShift Service Mesh 3.3.9
- +12 more
Patch Availability(30)
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(10 across 4 ecosystems)
Debian:14(4)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| golang-1.25 | 1.25.0-1 ... 1.25.9-1 (20 versions) |
| — |
| golang-1.26 | 1.26.0-1 ... 1.26~rc3-2 (24 versions) |
| — |
| golang-1.27 | 1.27.0-1 ... 1.27~rc3-1 (9 versions) |
| — |
| golang-golang-x-net | 1:0.27.0-2 ... 1:0.60.0-1 (11 versions) |
| — |
Debian:12(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| golang-1.19 | 1.19.10-1 ... 1.19.9-1 (12 versions) |
| — |
| golang-golang-x-net | 1:0.10.0-1 ... 1:0.7.0+dfsg-1 (28 versions) |
| — |
Debian:13(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| golang-1.24 | 1.24.12-1 ... 1.24.9-1 (10 versions) |
| — |
| golang-golang-x-net | 1:0.27.0-2 ... 1:0.60.0-1 (11 versions) |
| — |
Go(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| golang.org/x/net | — |
| — |
| stdlib | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(25)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
- Microsoft MSRCCVE-2026-786692026-10-11
Excessive CPU consumption from repeated initial window changes in net/http
- Red HatRHSA-2026:86093IMPORTANT2026-10-08
RHSA-2026:86093 — Important
- Red HatRHSA-2026:86196IMPORTANT2026-10-08
RHSA-2026:86196 — Important
- Red HatRHSA-2026:86203IMPORTANT2026-10-08
RHSA-2026:86203 — Important
- Red HatRHSA-2026:86972IMPORTANT2026-10-08
RHSA-2026:86972 — Important
- Red HatRHSA-2026:86973IMPORTANT2026-10-08
RHSA-2026:86973 — Important
- Red HatRHSA-2026:87040IMPORTANT2026-10-08
RHSA-2026:87040 — Important
- Red HatRHSA-2026:87041IMPORTANT2026-10-08
RHSA-2026:87041 — Important
- Red HatRHSA-2026:87042IMPORTANT2026-10-08
RHSA-2026:87042 — Important
- Red HatRHSA-2026:87043IMPORTANT2026-10-08
RHSA-2026:87043 — Important
- Red HatRHSA-2026:87245IMPORTANT2026-10-08
RHSA-2026:87245 — Important
- Red HatRHSA-2026:87246IMPORTANT2026-10-08
RHSA-2026:87246 — Important
- Red HatRHSA-2026:87732IMPORTANT2026-10-08
RHSA-2026:87732 — Important
- Red HatRHSA-2026:87911IMPORTANT2026-10-08
RHSA-2026:87911 — Important
- Red HatRHSA-2026:88188IMPORTANT2026-10-08
RHSA-2026:88188 — Important
- Red HatRHSA-2026:88189IMPORTANT2026-10-08
RHSA-2026:88189 — Important
- Red HatRHSA-2026:88262IMPORTANT2026-10-08
RHSA-2026:88262 — Important
- Red HatRHSA-2026:88280IMPORTANT2026-10-08
RHSA-2026:88280 — Important
- Red HatRHSA-2026:88316IMPORTANT2026-10-08
RHSA-2026:88316 — Important
- Red HatRHSA-2026:88317IMPORTANT2026-10-08
RHSA-2026:88317 — Important
- Red HatRHSA-2026:88332IMPORTANT2026-10-08
RHSA-2026:88332 — Important
- Red HatRHSA-2026:88336IMPORTANT2026-10-08
RHSA-2026:88336 — Important
- Red HatRHSA-2026:88339IMPORTANT2026-10-08
RHSA-2026:88339 — Important
- Red HatRHSA-2026:88340IMPORTANT2026-10-08
RHSA-2026:88340 — Important
- Red HatRHSA-2026:88354IMPORTANT2026-10-08
RHSA-2026:88354 — Important
Data Freshness Timeline
(refreshed 9× in last 7d / 44× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-28 07:48 UTCEG score recompute
- 2026-10-28 07:48 UTCVendor advisory
- 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
- 2026-10-25 14:00 UTCEG score recompute
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-20 18:18 UTCEG score recompute
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-18 03:11 UTCEG score recompute
- 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.6% · 45th percentile
Show 19 moreShow fewer
- 2026-10-13 06:46 UTCEG score recompute
- 2026-10-13 06:46 UTCVendor advisory
- 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-12 15:36 UTCEG score recompute
- 2026-10-11 19:22 UTCEG score recompute
- 2026-10-11 16:38 UTCEG score recompute
- 2026-10-11 13:57 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-11 03:07 UTCEG score recompute
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 45th percentile
- 2026-10-10 04:46 UTCEG score recompute
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 12th percentile
- 2026-10-09 17:33 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
- 2026-10-09 16:52 UTCNVD update
- 2026-10-09 16:39 UTCEG score recomputeFirst assessed: 7.5 HIGH
- 2026-10-09 16:38 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
- 2026-10-08 23:20 UTCNVD update
- 2026-10-08 22:58 UTCEG score recompute
- 2026-10-08 22:58 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownDebian:14:golang-1.27 · Debian:12:golang-golang-x-net
Same vendor
10 shownredhat:RHSA-2026:86093 · redhat:RHSA-2026:87245
Frequently asked(5)
What is CVE-2026-78669?
When was the CVE record for CVE-2026-78669 published?
Is CVE-2026-78669 actively exploited?
What is the CVSS score of CVE-2026-78669?
How do I remediate CVE-2026-78669?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-78669
Is Your Infrastructure Affected by CVE-2026-78669?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.