h2o is an HTTP server with support for HTTP/1.x, HTTP/2 and HTTP/3. Prior to commit 9265bdd, there is an HTTP/2 state amplification issue that combines HPACK decompression amplification with Slowloris-style stream stalling. Amplified decoded header state can be retained by stalled HTTP/2 streams, and depending on the configuration, additional limits are needed to bound decoded header state and prevent attack. This issue has been fixed by commit 9265bdd.
CVE-2026-54340
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 20%
- KEV
- Not listed
Published
July 16, 2026
Last Modified
July 17, 2026
Advisory Details (2)
Auto-updated Jul 17, 2026HTTP/2 state amplification · Advisory · h2o/h2o · GitHub
https://github.com/h2o/h2o/security/advisories/GHSA-qcrr-wrhc-pgq9commit 9265bdd9a996 (h2o/h2o)
Fix landed in h2o/h2o commit 9265bdd9a996 — awaiting tagged release
https://github.com/h2o/h2o/commit/9265bdd9a996ed992681055e3996baf3e09d2063Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 20× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-07-28 19:09 UTCEG score recompute
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-27 20:51 UTCEG score recompute
- 2026-07-26 22:25 UTCEG score recompute
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 11:23 UTCEG score recompute
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:19 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:32 UTCEG score recompute
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 23:54 UTCEG score recompute
- 2026-07-16 23:54 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-400 · CWE-770
- CVE-2004-1464NVD 5.9EG 9.0 KEVEPSS p92CRITICAL
- CVE-2010-3705EG 8.3HIGH
- CVE-2006-1364NVD 7.5EG 8.2EPSS p99HIGH
- CVE-2008-5180NVD 5.3EG 7.9EPSS p99HIGH
- CVE-2012-0024EG 7.8HIGH
- CVE-2011-3192EG 7.8EPSS p100HIGH
- CVE-2010-4686EG 7.8HIGH
- CVE-2010-4671EG 7.8HIGH
- CVE-2009-2054EG 7.8HIGH
- CVE-2009-2726EG 7.8EPSS p93HIGH
Frequently asked(5)
What is CVE-2026-54340?
When was CVE-2026-54340 disclosed?
Is CVE-2026-54340 actively exploited?
What is the CVSS score of CVE-2026-54340?
How do I remediate CVE-2026-54340?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-54340
Is Your Infrastructure Affected by CVE-2026-54340?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.