Skip to main content
VulnerabilityPublished Updated

CVE-2026-84380: HTTPX2 · Conflicting Content-Length and Transfer-Encoding headers can be auto-generated

Affects bump-my-versionSource GCVE Database

0
Authoritative record:CVE-2026-84380· Medium 5.6

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

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade bump-my-version to 1.5.1_1.

Affected software

ProductAffectedFixed in
Homebrewbump-my-versionpkg:brew/bump-my-versionOther threatsAffected
  • >=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 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

Community reviews

Loading reviews…