cve.bz

CVE-2025-57804 python-hyper h2: CRLF Injection

6.9 mediumEPSS 2.0%Fix available

Medium (6.9) in python-hyper h2. EPSS 2.0% estimated probability of exploitation activity in the next 30 days. Fixed in h2 4.3.0.

On this page
h2 is a pure-Python implementation of a HTTP/2 protocol stack. Prior to version 4.3.0, an HTTP/2 request splitting vulnerability allows attackers to perform request smuggling attacks by injecting CRLF characters into headers. This occurs when servers downgrade HTTP/2 requests to HTTP/1.1 without properly validating header names/values, enabling attackers to manipulate request boundaries and bypass security controls. This issue has been patched in version 4.3.0.

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N
EPSS
2.0% (unchanged from 2.0% a week ago; 1.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 81st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2025-08-26. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-93 Improper Neutralization of CRLF Sequences (CRLF Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-57804 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-57804?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-57804?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-2025-57804 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.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
python-hyper h2< 4.3.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-847f-9342-265hPyPIh2<4.3.04.3.0
PYSEC-2026-1435PyPIh2<4.3.04.3.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11python-h24.0.0-3+deb11u1DLA-4290-1
Debian12, 13python-h2no fix listedDEBIAN-CVE-2025-57804
Debian14python-h24.3.0-1DEBIAN-CVE-2025-57804
Ubuntu18.04:LTS, 20.04:LTS, 22.04:LTS and 3 morepython-h2no fix listedUBUNTU-CVE-2025-57804
SUSELinux Enterprise Module for Python 3 15 SP6, Linux Enterprise Module for Python 3 15 SP7python-h24.1.0-150400.8.6.1SUSE-SU-2025:03199-1
SUSELinux Enterprise Module for Server Applications 15 SP6, Linux Enterprise Module for Server Applications 15 SP7python-h23.2.0-150200.3.5.1SUSE-SU-2025:03273-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0python-h24.2.0-160000.3.1SUSE-SU-2026:20187-1
openSUSELeap 15.6python-h24.1.0-150400.8.6.1SUSE-SU-2025:03199-1
openSUSELeap 16.0python-h24.2.0-160000.3.1openSUSE-SU-2026:20122-1
openSUSETumbleweedpython-h24.3.0-1.1openSUSE-SU-2025:15496-1
Alpaquita23, 25, streampy3-h2no fix listedBELL-CVE-2025-57804

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

Red Hat rates this Moderate.

Red Hat's statement

This issue is classified as Moderate rather than Important because its impact is constrained to integrity violations through request injection, without directly compromising confidentiality or availability. The flaw arises only in environments where HTTP/2 traffic is downgraded to HTTP/1.1 by intermediaries, which is not the default behavior in many deployments. Successful exploitation requires specific backend or proxy configurations that fail to sanitize CRLF sequences properly. As a result, the vulnerability does not universally expose systems to privilege escalation or data leakage but instead enables request manipulation under certain conditions.

Red Hat's mitigation

Mitigation is either unavailable or does not meet Red Hat Product Security standards for usability, deployment, applicability, or stability.

ProductPackageStateAdvisory
OpenShift Service Mesh 3openshift-service-mesh-dev-preview-beta/istio-ztunnel-rhel9Fix deferred
OpenShift Service Mesh 3openshift-service-mesh/istio-cni-rhel9Fix deferred
OpenShift Service Mesh 3openshift-service-mesh/istio-must-gather-rhel9Fix deferred
OpenShift Service Mesh 3openshift-service-mesh/istio-pilot-rhel9Fix deferred
OpenShift Service Mesh 3openshift-service-mesh/istio-proxyv2-rhel9Fix deferred
OpenShift Service Mesh 3openshift-service-mesh/istio-rhel9-operatorFix deferred
OpenShift Service Mesh 3openshift-service-mesh/istio-sail-operator-bundleFix deferred
OpenShift Service Mesh 3openshift-service-mesh-tech-preview/istio-ztunnel-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/ee-cloud-services-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/ee-supported-rhel9Fix 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-2025-57804.

Attack patterns (CAPEC)

  • CAPEC-15 Command Delimiters Likelihood: High · Severity: High
  • CAPEC-81 Web Server Logs Tampering Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON