CVSS 3.1
5.3 mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LMedium (5.3) in python-hyper h2. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in h2 4.4.1.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Lh2 (PyPI): fixed in 4.4.1Explain CVE-2026-71554 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-71554?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-71554?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-71554 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| python-hyper h2 | < 4.4.1 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-6hr6-w5qg-qmwg | PyPI | h2 | <4.4.1 | 4.4.1 |
| PYSEC-2026-3628 | PyPI | h2 | <4.4.1 | 4.4.1 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | python-h2 | no fix listed | DEBIAN-CVE-2026-71554 |
| Ubuntu | 18.04:LTS, 20.04:LTS, 22.04:LTS and 3 more | python-h2 | no fix listed | UBUNTU-CVE-2026-71554 |
| SUSE | Linux Enterprise Module for Python 3 15 SP7 | python-h2 | 4.1.0-150400.8.9.1 | SUSE-SU-2026:3970-1 |
| SUSE | Linux Enterprise Module for Server Applications 15 SP7 | python-h2 | 3.2.0-150200.3.8.1 | SUSE-SU-2026:3972-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | python-h2 | 4.2.0-160000.4.1 | SUSE-SU-2026:23563-1 |
| openSUSE | Leap 16.0 | python-h2 | 4.2.0-160000.4.1 | openSUSE-SU-2026:21693-1 |
| openSUSE | Tumbleweed | python-h2 | 4.4.1-1.1 | openSUSE-SU-2026:11523-1 |
| Alpaquita | 23 | py3-h2 | 4.1.0-r2 | BELL-CVE-2026-71554 |
| Alpaquita | 25 | py3-h2 | 4.1.0-r4 | BELL-CVE-2026-71554 |
| Alpaquita | stream | py3-h2 | 4.1.0-r6 | BELL-CVE-2026-71554 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.
Red Hat rates this Moderate.
h2 is a pure-Python HTTP/2 protocol stack. Versions <= 4.4.0 accept request header blocks containing more than one Host header and forward every Host header to the consuming application. When that application downgrades HTTP/2 to HTTP/1.1, the resulting request carries duplicate Host header lines, providing an HTTP request-smuggling primitive (CWE-444) that can be used to bypass front-end security controls.
Red Hat rates this Moderate (CVSS 5.3, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L), consistent with the upstream advisory (GHSA-6hr6-w5qg-qmwg) and CVEORG. Exploitation depends on a consuming application performing an HTTP/2 to HTTP/1.1 downgrade (typical of some proxy/gateway configurations); deployments that terminate HTTP/2 without downgrading are not exposed. All h2 releases up to and including 4.4.0 are affected; the issue is fixed in 4.4.1.
Update the bundled h2 Python library to 4.4.1 or later. Where an immediate upgrade is not possible, avoid HTTP/2 to HTTP/1.1 downgrade in front-end proxies for affected services, or reject requests carrying more than one Host header at the edge.
| Product | Package | State | Advisory |
|---|---|---|---|
| Migration Toolkit for Containers | rhmtc/openshift-migration-hook-runner-rhel8 | Fix deferred | |
| Red Hat Ansible Automation Platform 2 | ansible-automation-platform-24/ee-supported-rhel8 | Fix deferred | |
| Red Hat Ansible Automation Platform 2 | ansible-automation-platform-24/ee-supported-rhel9 | Fix deferred | |
| Red Hat Ansible Automation Platform 2 | ansible-automation-platform-24/platform-resource-runner-rhel8 | Fix deferred | |
| Red Hat Ansible Automation Platform 2 | ansible-automation-platform-25/ee-supported-rhel8 | Fix deferred | |
| Red Hat Ansible Automation Platform 2 | ansible-automation-platform-25/ee-supported-rhel9 | Fix deferred | |
| Red Hat Ansible Automation Platform 2 | ansible-automation-platform-25/platform-resource-runner-rhel8 | Fix deferred | |
| Red Hat Ansible Automation Platform 2 | ansible-automation-platform-26/ee-supported-rhel9 | Fix deferred | |
| Red Hat Ansible Automation Platform 2 | ansible-automation-platform-27/ee-supported-rhel9 | Fix deferred | |
| Red Hat Hardened Images | python-urllib3 | Fix deferred | |
| Red Hat OpenShift AI (RHOAI) | rhai/guidellm-rhel9 | Fix deferred | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-feature-server-rhel9 | Fix deferred | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-llama-stack-core-rhel9 | Fix deferred | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-ogx-core-rhel9 | Fix deferred | |
| Red Hat OpenStack Platform 17.1 | python-h2 | Fix deferred | |
| Red Hat OpenStack Platform 18.0 | python-h2 | Fix deferred | |
| Red Hat OpenStack Platform 18.0 | rhoso/openstack-tempest-all-rhel9 | Fix deferred |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-71554.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.