CVE-2026-84381
WebSocket TLS upgrade bypass in HTTPX2 via SOCKS5 proxy exposes plaintext traffic
Is CVE-2026-84381 being exploited?
Not confirmed. CVE-2026-84381 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.08% probability of exploitation in the next 30 days.
How severe is CVE-2026-84381?
CVE-2026-84381 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-84381?
Yes. A fix has been recorded for CVE-2026-84381. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-84381 affect?
CVE-2026-84381 affects HTTPX2 2.6.0–2.9.1, httpcore2 < 2.10.0, Apps using Client.websocket()/AsyncClient.websocket(). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-84381?
Upgrade httpx2 and httpcore2 to 2.10.0+ and redeploy; audit WebSocket-over-SOCKS5 usage.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
MITM can read/modify WebSocket handshake, query params, Authorization headers, cookies and frames; impersonate the server via SOCKS5 proxy.
Immediate action required
- affected< 2.10.0
- affected>= 2.6.0 and < 2.10.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.