Skip to main content
VulnerabilityPublished Updated

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

Affects hermes-agentSource GCVE Database

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

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

Data as of 27 Oct 2026, 21:00 UTC

CVSS 3.1 base score
5.6Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.22.2
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 hermes-agent to 0.22.2.

Affected software

ProductAffectedFixed in
Homebrewhermes-agentpkg:brew/hermes-agentOther threatsAffected
  • >=0.21.6 <0.22.2
  • >=2026.8.31_1 <=2026.9.24
Fixed in
  • 0.22.2

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.22.2 or later, where the issue is fixed by treating Content-Length and Transfer-Encoding headers as mutually exclusive during automatic header generation. If immediate upgrade is not possible, remove Transfer-Encoding and other hop-by-hop framing headers from untrusted input before constructing outbound requests. Applications acting as proxies should derive outbound framing headers from the body content rather than forwarding inbound Content-Length or Transfer-Encoding headers.

Description

HTTPX2 versions before 0.22.2 can automatically add a Content-Length header to requests that already include a Transfer-Encoding header, resulting in conflicting HTTP/1.1 framing headers. This ambiguity can enable request smuggling or connection desynchronization when intermediaries interpret the headers differently. The issue affects requests with fixed-size bodies using HTTP/1.1 and requires attacker-controlled framing headers to be forwarded by the application. The vulnerability is fixed in HTTPX2 version 0.22.2.

References

Community reviews

Loading reviews…