CVE-2026-97032

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” 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.7% (52nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from CISA-ADP (Vulnrichment) CVSS v3.1
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS

Also known asEUVD-2026-95429 (ENISA EUVD) · GO-2026-6617 (OSV.dev)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG 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.7% × 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.7%
EPSS %ILE
52nd
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.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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 15, 2026

Advisory Details (6)

Auto-updated Oct 15, 2026
Patch available.

Patch Availability(15)

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

(12 across 5 ecosystems)
Debian:14(4)
PackageVulnerable rangeFix by version rangeDependents
golang-1.251.25.0-1 ... 1.25.9-1 (20 versions)
  • every version on: no fix on record
—
golang-1.261.26.0-1 ... 1.26~rc3-2 (23 versions)
  • every version up to 1.26.9-1: fixed in 1.26.9-1
—
golang-1.271.27.0-1 ... 1.27~rc3-1 (9 versions)
  • every version up to 1.27.2-1: fixed in 1.27.2-1
—
golang-golang-x-net1:0.27.0-2 ... 1:0.58.0-1 (10 versions)
  • every version up to 1:0.60.0-1: fixed in 1:0.60.0-1
—
Alpine:v3.24(2)
PackageVulnerable rangeFix by version rangeDependents
docker—
  • every version up to 29.9.0-r0: fixed in 29.9.0-r0
—
go—
  • every version up to 1.26.9-r0: fixed in 1.26.9-r0
—
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
golang-1.191.19.10-1 ... 1.19.9-1 (12 versions)
  • every version on: no fix on record
—
golang-golang-x-net1:0.10.0-1 ... 1:0.7.0+dfsg-1 (28 versions)
  • every version on: no fix on record
—
Debian:13(2)
PackageVulnerable rangeFix by version rangeDependents
golang-1.241.24.12-1 ... 1.24.9-1 (10 versions)
  • every version on: no fix on record
—
golang-golang-x-net1:0.27.0-2 ... 1:0.60.0-1 (11 versions)
  • every version on: no fix on record
—
Go(2)
PackageVulnerable rangeFix by version rangeDependents
golang.org/x/net—
  • every version up to 0.60.0: fixed in 0.60.0
—
stdlib—
  • every version up to 1.26.9: fixed in 1.26.9
  • 1.27.0-0 up to 1.27.2: fixed in 1.27.2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 35× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  2. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  3. 2026-11-11 00:52 UTCEchelonGraph re-scored
  4. 2026-11-11 00:52 UTCVendor advisory
  5. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  6. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  7. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  8. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  9. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  10. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  11. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  12. 2026-11-04 11:15 UTCEchelonGraph re-scored
  13. 2026-11-04 11:15 UTCVendor advisory
  14. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  15. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  16. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  17. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  18. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  19. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  20. 2026-10-28 23:09 UTCEchelonGraph re-scored
  21. 2026-10-28 23:09 UTCVendor advisory
  22. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  23. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  24. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  25. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
Show 29 more
  1. 2026-10-25 13:48 UTCEchelonGraph re-scored
  2. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  3. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  4. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  5. 2026-10-22 04:41 UTCEchelonGraph re-scored
  6. 2026-10-22 04:41 UTCVendor advisory
  7. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  8. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  9. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  10. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  11. 2026-10-18 02:56 UTCEchelonGraph re-scored
  12. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  13. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  14. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  15. 2026-10-15 15:57 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
  16. 2026-10-15 15:57 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  17. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  18. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  19. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  20. 2026-10-12 14:40 UTCEchelonGraph re-scored
  21. 2026-10-11 19:11 UTCEchelonGraph re-scored
  22. 2026-10-11 16:26 UTCEchelonGraph re-scored
  23. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  24. 2026-10-11 13:38 UTCEchelonGraph re-scored
  25. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  26. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  27. 2026-10-08 23:20 UTCNVD update
  28. 2026-10-08 22:58 UTCEchelonGraph re-scored
  29. 2026-10-08 22:58 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-97032?
CVE-2026-97032 is a high-severity vulnerability; its CVE record was published on October 8, 2026. HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the…
When was the CVE record for CVE-2026-97032 published?
The CVE record for CVE-2026-97032 was published on October 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 15, 2026; the record at its source may have been updated since.
Is CVE-2026-97032 actively exploited?
CVE-2026-97032 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97032?
CVE-2026-97032 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-97032?
A fix for CVE-2026-97032 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-97032 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-97032

Explore →

Is Your Infrastructure Affected by CVE-2026-97032?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.