Skip to main content
VulnerabilityPublished Updated

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

Affects httpx2Source GCVE Database

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

Not known to be exploited · CVSS 5.6 Medium : upgrade to 2.11.0 when convenient.

Data as of 18 Nov 2026, 18:04 UTC

CVSS 3.1 base score
5.6Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 2.11.0
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. 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 issue is fixed by treating Content-Length and Transfer-Encoding headers as mutually exclusive when automatically adding request 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 2.9.1 through before 2.11.0 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 message framing rules and potentially enabling request smuggling or connection desynchronization attacks. Exploitation requires attacker-controlled request framing headers, use of HTTP/1.1, and intermediaries that interpret conflicting headers differently. The issue is fixed in HTTPX2 version 2.11.0.

References

Community reviews

Loading reviews…