CVE-2026-84379: HTTPX2 · Multipart part header injection via unvalidated file Content-Type and custom headers
Affects httpx2Source GCVE Database
Not known to be exploited · CVSS 5.3 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:L/PR:N/UI:N/S:U/C:N/I:L/A:NExploitation 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 vulnerability is fixed by rejecting forbidden control characters in multipart part header names and values, raising a ValueError before request serialization. If immediate upgrade is not possible, applications should validate and sanitize all per-file Content-Type and custom header names and values to reject NUL, CR, LF, other C0 controls except horizontal tab, and DEL characters before passing them to HTTPX2.
Description
HTTPX2 versions from 2.9.1 up to but not including 2.11.0 allow injection of additional multipart part headers via unvalidated CR or LF characters in per-file Content-Type and custom headers. This occurs because these headers are serialized directly into the multipart body without proper validation, enabling attackers who control upload metadata to inject headers that may alter multipart semantics or bypass server-side checks. The issue is fixed in HTTPX2 version 2.11.0, which rejects forbidden control characters in multipart part header names and values.
References
- github.com/pydantic/httpx2/security/advisories/GHSA-h4x7-gw46-3wm6 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-84379 (opens in a new tab)
- github.com/pydantic/httpx2/pull/1142 (opens in a new tab)
- github.com/pydantic/httpx2/commit/de96d810ee4e309d118982fe7084a46a2bcd600d (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)