CVE-2026-84380: HTTPX2 · Conflicting Content-Length and Transfer-Encoding headers can be auto-generated
Affects bump-my-versionSource GCVE Database
Not known to be exploited · CVSS 5.6 Medium : upgrade to 1.5.1_1 when convenient.
Data as of 26 Oct 2026, 17:57 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.5.1_1
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
Weaponised: 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 26 Oct 2026.
What to do
Upgrade bump-my-version to 1.5.1_1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewbump-my-versionpkg:brew/bump-my-versionOther 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 to HTTPX2 version 1.5.1_1 or later, where the issue is fixed by treating Content-Length and Transfer-Encoding headers as mutually exclusive when automatically adding 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 from 1.4.0 up to but not including 1.5.1_1 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 framing rules and potentially enabling request smuggling or connection desynchronization attacks when intermediaries interpret these headers differently. The issue is fixed in HTTPX2 version 1.5.1_1.
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)