CVE-2026-84380: HTTPX2 · Conflicting Content-Length and Transfer-Encoding headers can be auto-generated
Affects httpx2Source GCVE Database
Not known to be exploited · CVSS 5.6 Medium : upgrade to 2.11.0 when convenient.
Data as of 18 Nov 2026, 18:04 UTC
- Patch
- Available – fixed in 2.11.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 2 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade httpx2 to 2.11.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewhttpx2pkg:brew/httpx2Other threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade HTTPX2 to version 2.11.0 or later, where the issue is fixed by treating Content-Length and Transfer-Encoding headers as mutually exclusive when automatically adding request headers. If immediate upgrade is not possible, remove Transfer-Encoding and other hop-by-hop framing headers from untrusted input before constructing outbound requests. Proxy applications should derive outbound framing headers from the body rather than forwarding inbound Content-Length or Transfer-Encoding headers.
Description
HTTPX2 versions 2.9.1 through before 2.11.0 can automatically add a Content-Length header to requests that already include a Transfer-Encoding header. This results in HTTP/1.1 requests containing both headers, violating HTTP message framing rules and potentially enabling request smuggling or connection desynchronization attacks. Exploitation requires attacker-controlled request framing headers, use of HTTP/1.1, and intermediaries that interpret conflicting headers differently. The issue is fixed in HTTPX2 version 2.11.0.
References
- github.com/pydantic/httpx2/security/advisories/GHSA-pf96-p4fj-6566 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-84380 (opens in a new tab)
- github.com/pydantic/httpx2/pull/1137 (opens in a new tab)
- github.com/pydantic/httpx2/commit/829b93a2393212996f613e635261f777d9ec6eab (opens in a new tab)
- github.com/pydantic/httpx2 (opens in a new tab)
- github.com/pydantic/httpx2/releases/tag/v2.11.0 (opens in a new tab)