Skip to main content
VulnerabilityPublished Updated

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

Affects rapid-mlxSource GCVE Database

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

Not known to be exploited · CVSS 5.3 Medium : upgrade to 0.12.15 when convenient.

Data as of 1 Nov 2026, 00:36 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.12.15
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 31 Oct 2026.

What to do

Upgrade rapid-mlx to 0.12.15.

Affected software

ProductAffectedFixed in
Homebrewrapid-mlxpkg:brew/rapid-mlxOther threatsAffected
  • >=0.11.3 <0.12.15
Fixed in
  • 0.12.15

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 rejecting forbidden control characters in multipart part header names and values and raising a ValueError before serialization. If immediate upgrade is not possible, validate and sanitize all per-file Content-Type and custom header values before passing them to HTTPX2, ensuring they do not contain NUL, CR, LF, other C0 controls except horizontal tab, or DEL characters. Reject any invalid header names or values to prevent injection.

Description

HTTPX2 versions from 0.11.3 up to but not including 0.12.15 improperly serialize per-file Content-Type and custom headers in multipart/form-data requests without validating for control characters. This allows an attacker who can influence upload metadata to inject additional multipart part headers by including CR or LF characters, potentially altering part semantics or bypassing server-side checks. The vulnerability is fixed in HTTPX2 version 0.12.15, which rejects forbidden control characters and raises an error before serialization.

References

Community reviews

Loading reviews…