Skip to main content
VulnerabilityPublished Updated

CVE-2026-84379: HTTPX2 · Multipart part header injection via unvalidated file Content-Type and custom headers

Affects httpx2Source GCVE Database

0
Compare
Authoritative record:CVE-2026-84379· Medium 5.3

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

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Homebrewhttpx2pkg:brew/httpx2Other threatsAffected
  • >=2.9.1 <2.11.0
Fixed in
  • 2.11.0

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

Community reviews

Loading reviews…