CVE-2026-84380: HTTPX2 · Conflicting Content-Length and Transfer-Encoding headers can be auto-generated
Affects hermes-agentSource GCVE Database
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
- 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:LExploitation 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.
What to do
Upgrade hermes-agent to 0.22.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewhermes-agentpkg:brew/hermes-agentOther threats | Affected
| Fixed in
|
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
- github.com/pydantic/httpx2/security/advisories/GHSA-pf96-p4fj-6566 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-84380 (opens in a new tab)
- github.com/pydantic/httpx2/pull/1137 (opens in a new tab)
- github.com/pydantic/httpx2/commit/829b93a2393212996f613e635261f777d9ec6eab (opens in a new tab)
- github.com/pydantic/httpx2 (opens in a new tab)
- github.com/pydantic/httpx2/releases/tag/v2.11.0 (opens in a new tab)