CVE-2026-84380: HTTPX2 · Conflicting Content-Length and Transfer-Encoding headers can be auto-generated
Affects rapid-mlxSource GCVE Database
Not known to be exploited · CVSS 5.6 Medium : upgrade to 0.12.15 when convenient.
Data as of 1 Nov 2026, 00:36 UTC
- Patch
- Available – fixed in 0.12.15
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 31 Oct 2026.
What to do
Upgrade rapid-mlx to 0.12.15.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewrapid-mlxpkg:brew/rapid-mlxOther 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 0.12.15 or later, where the issue is fixed by treating Content-Length and Transfer-Encoding headers as mutually exclusive when automatically generating request headers. If upgrading is not immediately 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 request body rather than forwarding inbound framing headers.
Description
HTTPX2 versions from 0.11.3 up to but not including 0.12.15 automatically add a Content-Length header even when a Transfer-Encoding header is present, resulting in conflicting HTTP/1.1 framing headers. This can cause ambiguous message boundaries leading to potential request smuggling or connection desynchronization when intermediaries interpret these headers differently. The issue is fixed in version 0.12.15.
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)