CVE-2026-84381

published 2 Sep 2026 · updated 5 Sep 2026

HTTPX2: Secure WebSocket traffic sent without TLS through SOCKS proxies

8.1HighCVSS 8.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
pydantic<2.10.0, >=2.6.0 <2.10.0

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-84381 severity on Zeptric[![CVE-2026-84381](https://zeptric.io/badge/cve/CVE-2026-84381.svg)](https://zeptric.io/cve/CVE-2026-84381)