Skip to main content
VulnerabilityPublished Updated

CVE-2026-84381: HTTPX2 · Secure WebSocket traffic sent without TLS through SOCKS proxies

Affects httpx2Source GCVE Database

0
Compare
Authoritative record:CVE-2026-84381· High 8.1

Not known to be exploited · CVSS 8.1 High : upgrade to 2.10.0 soon.

Data as of 18 Nov 2026, 17:51 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 2.10.0
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

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

Affected software

ProductAffectedFixed in
Homebrewhttpx2pkg:brew/httpx2Other threatsAffected
  • >=2.9.1 <2.10.0
Fixed in
  • 2.10.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 and httpcore2 to version 2.10.0 or later, where TLS is correctly started for both https and wss origins over SOCKS5 proxies. If immediate upgrade is not possible, avoid routing wss:// connections through SOCKS proxies. Instead, use direct secure WebSocket connections or alternative transports that perform and verify TLS to the WebSocket origin.

Description

HTTPX2 versions from 2.6.0 through 2.9.1, relying on httpcore2 before 2.10.0, fail to initiate TLS for secure WebSocket (wss://) connections routed through SOCKS5 proxies. This results in the WebSocket handshake and subsequent frames being sent in plaintext through the proxy, exposing sensitive headers, cookies, and messages. The flaw allows a malicious or compromised SOCKS proxy to intercept, modify, or impersonate the WebSocket server. The issue is fixed in HTTPX2 and httpcore2 version 2.10.0.

References

Community reviews

Loading reviews…