Advisory record · GHSA-7mj9-2mp8-4m2p

HTTPX2: Secure WebSocket traffic sent without TLS through SOCKS proxies

CVSS 8.1 HighEPSS 0.0008 · 1st percentile

Published by the GitHub Advisory Database at 8 Sept 2026, 20:45 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
httpcore2PyPI<2.10.02.10.0
httpx2PyPI>=2.6.0, <2.10.02.10.0
Identifiers
GHSA-7mj9-2mp8-4m2p · CVE-2026-84381 · PYSEC-2026-3844 · PYSEC-2026-3845
Weakness (CWE)
CWE-319
Published
8 Sept 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Packages httpcore2 before 2.10.0 and httpx2 from 2.6.0 through 2.9.1 are affected. For wss:// connections routed through a SOCKS5 proxy, TLS is not started, so the WebSocket handshake and frames are sent in plaintext. An attacker who controls or observes the SOCKS proxy path can read sensitive data such as cookies and headers, and a malicious proxy can impersonate the server and alter messages. Upgrade httpx2 and httpcore2 to 2.10.0 or later; until then, avoid routing wss:// connections through a SOCKS proxy.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.1 High 3.1 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0008, the 1st percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:10 UTC First seen by agentprime
  2. 31 Oct 2026, 14:10 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.