h2 is a pure-Python implementation of a HTTP/2 protocol stack. Versions up to and including 4.4.0 accept request header blocks containing more than one Host header, and forward every Host header to the consuming application. Where the consumer downgrades HTTP/2 to HTTP/1.1, the resulting request carries two Host header lines, providing a request smuggling primitive. This issue is fixed in version 4.4.1.
CVE-2026-71554
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EG Risk
- 39(Track)EG Risk 39/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 computedSeverity53% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 25%
- KEV
- Not listed
Published
August 6, 2026
Last Modified
August 8, 2026
Advisory Details (2)
Auto-updated Aug 6, 2026Duplicate Host header could facilitate request smuggling · Advisory · python-hyper/h2 · GitHub
Affected: v4.4.1
https://github.com/python-hyper/h2/security/advisories/GHSA-6hr6-w5qg-qmwgcommit 292a40829fee (python-hyper/h2)
Fix landed in python-hyper/h2 commit 292a40829fee — awaiting tagged release
https://github.com/python-hyper/h2/commit/292a40829feefda98c8509dcdbbb4a57af9bd6a6Vendor Advisories for CVE-2026-71554(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(5 across 5 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| python-h2 | 4.0.0-3 ... 4.3.0-2 (9 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| python-h2 | 4.1.0-4, 4.2.0-1, 4.3.0-1, 4.3.0-2 | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| python-h2 | 4.2.0-1, 4.3.0-1, 4.3.0-2 | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| python-h2 | 4.2.0-1, 4.3.0-1, 4.3.0-2 | — | — |
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| h2 | 0.1.0 ... 4.4.0 (47 versions) | 4.4.1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 16× in last 7d / 31× 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-08-21 02:44 UTCEG score recompute
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 00:49 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 22:47 UTCEG score recompute
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 20:44 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 18:49 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 16:45 UTCEG score recompute
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 14:50 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 12:55 UTCEG score recompute
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 11:01 UTCEG score recompute
- 2026-08-11 09:05 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 07:11 UTCEG score recompute
- 2026-08-09 13:47 UTCEPSS rescore
- 2026-08-09 05:16 UTCEG score recompute
Show 6 moreShow fewer
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 03:22 UTCEG score recompute
- 2026-08-08 02:52 UTCEG score recompute
- 2026-08-08 00:32 UTCEG score recompute
- 2026-08-06 22:37 UTCEG score recompute
- 2026-08-06 22:07 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-444
Frequently asked(5)
What is CVE-2026-71554?
When was CVE-2026-71554 disclosed?
Is CVE-2026-71554 actively exploited?
What is the CVSS score of CVE-2026-71554?
How do I remediate CVE-2026-71554?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-71554
Is Your Infrastructure Affected by CVE-2026-71554?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.