Vulnerability Description
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.
CVSS Score
HIGH
Related Weaknesses (CWE)
References
- https://github.com/pydantic/httpx2/commit/fb008dd700b761d955210d9692475c3e2f3794
- https://github.com/pydantic/httpx2/pull/1104
- https://github.com/pydantic/httpx2/releases/tag/v2.10.0
- https://github.com/pydantic/httpx2/security/advisories/GHSA-7mj9-2mp8-4m2p
FAQ
What is CVE-2026-84381?
CVE-2026-84381 is a vulnerability with a CVSS score of 8.1 (HIGH). 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...
How severe is CVE-2026-84381?
CVE-2026-84381 has been rated HIGH with a CVSS base score of 8.1/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-84381?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.