CVE-2026-84381

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 100% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
8.1
EG Score
8.1(medium)
EG Risk
36(Track)
EG Risk 36/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
0%
KEV
Not listed

Published

September 2, 2026

Last Modified

September 9, 2026

Advisory Details (4)

Auto-updated Sep 2, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

v2.10.0

Patch available: pydantic/httpx2 v2.10.0

https://github.com/pydantic/httpx2/releases/tag/v2.10.0
github_commit Patch Available

commit fb008dd700b7 (pydantic/httpx2)

Patch available: pydantic/httpx2 v2.10.0 (contains commit fb008dd700b7)

https://github.com/pydantic/httpx2/commit/fb008dd700b761d955210d9692475c3e2f379453
github_pr Patch Available

Start TLS for wss scheme in SOCKS5 proxy connections

Patch available: pydantic/httpx2 v2.10.0 (PR #1104 merged 2026-08-02)

https://github.com/pydantic/httpx2/pull/1104
github Patch Available

Secure WebSocket traffic sent without TLS through SOCKS proxies · Advisory · pydantic/httpx2 · GitHub

https://github.com/pydantic/httpx2/security/advisories/GHSA-7mj9-2mp8-4m2p

Vendor Advisories for CVE-2026-84381(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
PyPI(2)
PackageVulnerable rangeFixed inDependents
httpcore20.0.0 ... 2.9.1 (13 versions)2.10.0—
httpx22.6.0, 2.7.0, 2.8.0, 2.9.0, 2.9.12.10.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 00:38 UTCEG score recompute
  2. 2026-09-17 19:32 UTCEPSS rescore
  3. 2026-09-17 00:14 UTCEG score recompute
  4. 2026-09-16 14:09 UTCEPSS rescore
  5. 2026-09-15 11:43 UTCEG score recompute
  6. 2026-09-15 03:12 UTCEPSS rescore
  7. 2026-09-15 03:12 UTCEPSS rescore
  8. 2026-09-12 22:18 UTCEG score recompute
  9. 2026-09-11 21:57 UTCEG score recompute
  10. 2026-09-11 14:53 UTCEPSS rescore
  11. 2026-09-11 14:53 UTCEPSS rescore
  12. 2026-09-11 09:47 UTCEG score recompute
  13. 2026-09-10 21:37 UTCEG score recompute
  14. 2026-09-08 23:11 UTCEG score recompute
  15. 2026-09-08 22:01 UTCEPSS rescore
  16. 2026-09-08 03:01 UTCEG score recompute
  17. 2026-09-06 01:38 UTCEG score recompute
  18. 2026-09-05 15:31 UTCEPSS rescore
  19. 2026-09-05 13:29 UTCEG score recompute
  20. 2026-09-05 01:18 UTCEG score recompute
  21. 2026-09-04 08:04 UTCEG score recompute
  22. 2026-09-04 05:07 UTCEPSS rescore
  23. 2026-09-02 19:31 UTCEG score recompute
  24. 2026-09-02 18:28 UTCEG score recompute
  25. 2026-09-02 18:26 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-84381?
CVE-2026-84381 is a high vulnerability published on September 2, 2026. HTTPX2 is a next generation HTTP client for Python. Prior to 2.10.0, httpcore2 fails to start TLS in src/httpcore2/httpcore2/sync/socksproxy.py and src/httpcore2/httpcore2/async/socksproxy.py when the remote origin uses wss through a SOCKS5 proxy because the TLS upgrade condition only recognizes…
When was CVE-2026-84381 disclosed?
CVE-2026-84381 was first published in the National Vulnerability Database on September 2, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-84381 actively exploited?
CVE-2026-84381 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.8% of all scored CVEs.
What is the CVSS score of CVE-2026-84381?
CVE-2026-84381 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-84381?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-84381, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-84381

Explore →

Is Your Infrastructure Affected by CVE-2026-84381?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs