PoC Monitor
← All CVEs
CVE-2026-84381published 2 Sep 2026 18:01 UTCData: JSON · API

HTTPX2

HTTPX2: Secure WebSocket traffic sent without TLS through SOCKS proxies

HTTPX2 is a next generation HTTP client for Python. Prior to 2.10.0, httpcore2 fails to start TLS in src/httpcore2/httpcore2/_sync/socks_proxy.py and src/httpcore2/httpcore2/_async/socks_proxy.py when the remote origin uses wss through a SOCKS5 proxy because the TLS upgrade condition only recognizes https. HTTPX2 exposes the flaw through Client.websocket() and AsyncClient.websocket() from 2.6.0 through 2.9.1, so the opening handshake, query parameters, Authorization headers, cookies, and subsequent frames can cross the proxy path in plaintext without certificate verification. An attacker controlling or observing that path can read or modify traffic and impersonate the WebSocket server. This issue is fixed in httpcore2 2.10.0 and HTTPX2 2.10.0.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.1high · scored by CNA · CWE-319
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

pydantic httpx2
  • >= 2.6.0, < 2.10.0

Fixed in 2.10.0

pydantic httpcore2
  • < 2.10.0

Fixed in 2.10.0

Mitigation

Upgrade httpx2 to 2.10.0 or later.

Upgrade httpcore2 to 2.10.0 or later.

References

1 more

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published2 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.