VulnerabilityPublished 10 Sep 2026Updated 26 Oct 2026

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

Affects bump-my-versionSource GCVE Database

Authoritative record:CVE-2026-84379· Medium 5.3

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

Data as of 26 Oct 2026, 17:57 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 24% 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:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade bump-my-version to 1.5.1_1.

Affected software

Product	Affected	Fixed in
Homebrewbump-my-version`pkg:brew/bump-my-version`Other threats	Affected >=1.4.0 <1.5.1_1	Fixed in 1.5.1_1

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 1.5.1_1 or later, where the vulnerability is fixed by rejecting control characters in multipart part header names and values. If immediate upgrade is not possible, validate and sanitize per-file content_type and custom header values to disallow NUL, CR, LF, other C0 controls except horizontal tab, and DEL characters before passing them to HTTPX2.

Description

HTTPX2 versions from 1.4.0 up to but not including 1.5.1_1 improperly serialize per-file Content-Type and custom headers in multipart/form-data requests without validating for CR or LF characters. This allows an attacker controlling upload metadata to inject additional multipart part headers by terminating headers early. The impact depends on how the receiving server processes multipart parts, potentially altering part semantics or bypassing header-based checks. The issue does not affect the outer HTTP request structure. A fix is available in HTTPX2 version 1.5.1_1 and later.

Impact

If an attacker can control the per-file content_type or custom headers in an HTTPX2 multipart upload, they can inject additional multipart part headers. This may alter the semantics of multipart parts or bypass server-side validation based on part headers. The vulnerability does not compromise the overall HTTP request structure or confidentiality but can lead to logic bypass or unexpected processing depending on the server's multipart parser behavior.

Summary

HTTPX2's multipart serialization of per-file Content-Type and custom headers accepts unvalidated header names and values, allowing CR and LF characters to prematurely terminate multipart part headers and inject additional headers. This vulnerability (CVE-2026-84379) affects versions >=1.4.0 and <1.5.1_1. The injection occurs within the multipart body, not the HTTP headers, and can influence how the server interprets multipart parts. The vulnerability is patched in version 1.5.1_1, which rejects forbidden control characters and raises a ValueError on invalid input.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Oct 2026, 17:57 UTC

Technical details

References

Community reviews

Related threats