CVE-2026-84381: HTTPX2: Secure WebSocket traffic sent without TLS through SOCKS proxies
httpcore2 does not start TLS for wss:// connections routed through a SOCKS5 proxy. The WebSocket opening handshake and all subsequent frames are sent in plaintext through the proxy path, despite the caller selecting the secure wss scheme.
The transport flaw affects httpcore2 releases before 2.10.0. HTTPX2 exposed this behavior through its public Client.websocket() and AsyncClient.websocket() APIs from 2.6.0 through 2.9.1.
References
- github.com/advisories/GHSA-7mj9-2mp8-4m2p
- github.com/pydantic/httpx2/commit/fb008dd700b761d955210d9692475c3e2f379453
- github.com/pydantic/httpx2/pull/1104
- github.com/pydantic/httpx2/releases/tag/v2.10.0
- github.com/pydantic/httpx2/security/advisories/GHSA-7mj9-2mp8-4m2p
- nvd.nist.gov/vuln/detail/CVE-2026-84381
Code Behaviors & Features
Detect and mitigate CVE-2026-84381 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →