CVE-2026-84380: HTTPX2 Conflicting Content-Length And Transfer-Encoding Headers Vulnerability
MODERATECVE-2026-84380 is a MODERATE (CVSS 5.6) conflicting content-length and transfer-encoding headers vulnerability (CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')) affecting HTTPX2 libraries in the PyPI ecosystem. The issue involves conflicting content-length and transfer-encoding headers can be auto-generated. Remediation is available by upgrading affected packages to version 2.11.0.
CVE-2026-84380 at a Glance
Security Impact
CVSS: 5.6
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L).
How to Fix CVE-2026-84380
To remediate this vulnerability, upgrade all affected HTTPX2 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
pip install httpx2>=2.11.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
pip show httpx2
How to Check if You Are Affected
To determine whether your Python environment is affected by CVE-2026-84380, inspect your installed packages using pip:
pip show httpx2
Analyze the terminal output to locate any version of HTTPX2 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.11.0), your application is affected.
Note: The pip show httpx2 command checks currently installed packages in your active Python environment.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling'), where the product acts as an intermediary http agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed http requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination. In HTTPX2, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-84380 Affected HTTPX2 Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
httpx2
|
PyPI |
< 2.11.0
|
2.11.0
|
References
Frequently Asked Questions
What is CVE-2026-84380?
Which HTTPX2 versions are affected?
What version fixes CVE-2026-84380?
Is httpx2 affected?
What is the CVSS score of CVE-2026-84380?
What CWE is associated with CVE-2026-84380?
How can I check PyPI dependencies for CVE-2026-84380?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-pf96-p4fj-6566",
"modified" : "2026-09-08T20:46:28Z",
"published" : "2026-09-08T20:46:28Z",
"aliases" : [ "CVE-2026-84380" ],
"summary" : "HTTPX2: Conflicting Content-Length and Transfer-Encoding headers can be auto-generated",
"details" : "### Summary\n\nHTTPX2 can automatically add a `Content-Length` header to a request that already contains a caller-supplied `Transfer-Encoding` header. The resulting HTTP/1.1 request contains both framing headers, which can create an ambiguous message boundary and enable request smuggling or connection desynchronization when processed by intermediaries that disagree about which header takes precedence.\n\n### Details\n\nWhen a request body has a known size, HTTPX2's content encoder returns a default `Content-Length`. `Request._prepare()` applies each default header with `setdefault()`, which only checks whether that same header is already present. It does not check whether the mutually exclusive `Transfer-Encoding` header is present.\n\nFor example:\n\n```python\nimport httpx2\n\nrequest = httpx2.Request(\n \"POST\",\n \"http://example.com/\",\n headers={\"Transfer-Encoding\": \"chunked\"},\n content=b\"test 123\",\n)\n\nprint(request.headers)\n```\n\nThe request contains both:\n\n```text\nTransfer-Encoding: chunked\nContent-Length: 8\n```\n\nOn an HTTP/1.1 connection, the body is serialized using chunked transfer coding while both headers are sent on the wire. This violates HTTP message-framing requirements. Fixed-size byte, JSON, form, and known-length multipart bodies can reach the affected path.\n\nStreaming bodies with an explicit `Content-Length` are not affected in current HTTPX2 releases because the automatically generated `Transfer-Encoding` is already suppressed in that direction.\n\n### Impact\n\nAn attacker may be able to use the conflicting framing headers as a request-smuggling or desynchronization primitive. Exploitation requires an application to pass attacker-controlled request framing headers and associated body data to HTTPX2, use HTTP/1.1, and communicate through a proxy or origin that accepts conflicting headers and interprets them differently from another hop.\n\nDepending on the downstream infrastructure, successful exploitation could interfere with requests sharing a persistent connection, bypass front-end routing or authorization decisions, or poison responses or caches. Applications that do not forward attacker-controlled `Transfer-Encoding` headers are not directly exposed.\n\n### Mitigation\n\nUpgrade to HTTPX2 `2.11.0` or later. Patched versions treat `Content-Length` and `Transfer-Encoding` as mutually exclusive when applying automatically generated request headers.\n\nIf upgrading is not immediately possible, remove `Transfer-Encoding` and other hop-by-hop framing headers from untrusted input before constructing outbound requests. Applications acting as proxies should derive outbound framing from the body rather than forwarding inbound `Content-Length` or `Transfer-Encoding` headers.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "PyPI",
"name" : "httpx2"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "2.11.0"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/pydantic/httpx2/security/advisories/GHSA-pf96-p4fj-6566"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-84380"
}, {
"type" : "WEB",
"url" : "https://github.com/pydantic/httpx2/pull/1137"
}, {
"type" : "WEB",
"url" : "https://github.com/pydantic/httpx2/commit/829b93a2393212996f613e635261f777d9ec6eab"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/pydantic/httpx2"
}, {
"type" : "WEB",
"url" : "https://github.com/pydantic/httpx2/releases/tag/v2.11.0"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-444" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-09-08T20:46:28Z",
"nvd_published_at" : "2026-09-02T18:21:29Z"
}
}