# CVE-2026-84381: HTTPX2: Secure WebSocket traffic sent without TLS through SOCKS proxies

> HTTPX2 sends WebSocket traffic over SOCKS proxies without TLS, allowing attackers to read or modify sensitive data and impersonate servers.

- **Severity:** High 8.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Sep 2026
- **Updated:** 5 Sep 2026
- **Also known as:** ECHO-2af1-2f46-154f, GHSA-7mj9-2mp8-4m2p, MINI-794m-j5jh-44gg, PYSEC-2026-3844, PYSEC-2026-3845, ROOT-APP-PYPI-CVE-2026-84381, UBUNTU-CVE-2026-84381

## What is CVE-2026-84381?

CVE-2026-84381 is a high-severity vulnerability in pydantic httpcore2, published on 2 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2026-84381?

6 open source packages ship an affected version, including httpcore2 and httpx2.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `httpcore2` | PyPI | All versions | 2.10.0 |
| `httpcore2` | PyPI | All versions | 2.10.0 |
| `httpcore2` | PyPI | All versions | 2.10.0 |
| `httpx2` | PyPI | From 2.6.0 | 2.10.0 |
| `httpx2` | PyPI | From 2.6.0 | 2.10.0 |
| `httpx2` | PyPI | From 2.6.0 | 2.10.0 |

## How do I fix CVE-2026-84381?

Upgrade httpcore2 to 2.10.0 or later.

## Is CVE-2026-84381 being exploited?

There is no known exploitation of CVE-2026-84381 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-84381 and fix it if it is affected.

What it is: CVE-2026-84381 is a high-severity vulnerability in pydantic httpcore2, published on 2 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-84381 in the wild and no public exploit code.

Affected packages and fixed versions:
- httpcore2 (PyPI): affected all versions; fixed in 2.10.0
- httpcore2 (PyPI): affected all versions; fixed in 2.10.0
- httpcore2 (PyPI): affected all versions; fixed in 2.10.0
- httpx2 (PyPI): affected from 2.6.0; fixed in 2.10.0
- httpx2 (PyPI): affected from 2.6.0; fixed in 2.10.0
- httpx2 (PyPI): affected from 2.6.0; fixed in 2.10.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-84381/ (Markdown: https://insights.sbomify.com/CVE-2026-84381/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-84381
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-84381
- OSV: https://osv.dev/vulnerability/CVE-2026-84381

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-84381/
Summaries are generated and may contain mistakes; the official description above is the record.