cve.bz

CVE-2026-84381 pydantic

8.1 highEPSS 0.08%Fix available

High (8.1) in pydantic. EPSS 0.08% estimated probability of exploitation activity in the next 30 days. Fixed in httpcore2 2.10.0.

On this page
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.

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.08% (unchanged from 0.08% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 0th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-09-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-319 Cleartext Transmission of Sensitive Information
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • httpcore2 (PyPI): fixed in 2.10.0
  • httpx2 (PyPI): fixed in 2.10.0

Ask an AI about this CVE

Show the promptExplain CVE-2026-84381 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-84381?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-84381?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-84381 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
pydantic httpx2>= 2.6.0, < 2.10.0
pydantic httpcore2< 2.10.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-7mj9-2mp8-4m2pPyPIhttpcore2<2.10.02.10.0
GHSA-7mj9-2mp8-4m2pPyPIhttpx2>=2.6.0 <2.10.02.10.0
PYSEC-2026-3844PyPIhttpcore2<2.10.02.10.0
PYSEC-2026-3845PyPIhttpx2>=2.6.0 <2.10.02.10.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu26.10python-httpx2no fix listedUBUNTU-CVE-2026-84381

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as an Important severity because it completely compromises confidentiality and integrity over intended encrypted channels, permitting network-adjacent or man-in-the-middle attackers to capture authentication credentials and tamper with session data. In Red Hat environments, exposure is limited to specific deployments where client services are explicitly configured to route WebSocket Secure (wss://) connections through a SOCKS5 proxy. Direct secure WebSocket connections as well as standard HTTPS traffic traversing SOCKS5 proxies are unaffected, as they negotiate TLS handshakes as expected.

ProductPackageStateAdvisory
Red Hat AI Inference Server 3.5rhaii/vllm-gaudi-rhel9:1791427182Fixed 2026-10-13RHSA-2026:82061
Red Hat AI Inference Server 3.5rhaii/vllm-spyre-rhel9:1791818357Fixed 2026-10-13RHSA-2026:82371
Red Hat OpenShift AI 3.5rhoai/odh-automl-rhel9:1791916705Fixed 2026-10-21RHSA-2026:86891
Red Hat OpenShift AI 3.5rhoai/odh-kserve-autogluon-server-rhel9:1791950388Fixed 2026-10-21RHSA-2026:86891
Exploit Intelligenceexploit-intelligence/vulnerability-analysis-rhel9Not affected
Lightspeed Corelightspeed-core/lightspeed-stack-rhel9Affected
Migration Toolkit for Applications 8mta/mta-solution-server-rhel9Not affected
OpenShift Lightspeedopenshift-lightspeed/lightspeed-agentic-sandbox-rhel9Not affected
OpenShift Lightspeedopenshift-lightspeed/lightspeed-service-api-rhel9Not affected
Red Hat Enterprise Linux command line assistantrhel-cla/rhel-knowledge-bridge-rhel10Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-kserve-storage-initializer-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-vllm-gaudi-rhel9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-84381.

Attack patterns (CAPEC)

  • CAPEC-65 Sniff Application Code Likelihood: Low · Severity: High
  • CAPEC-102 Session Sidejacking Likelihood: High · Severity: High
  • CAPEC-117 Interception Likelihood: Low · Severity: Medium
  • CAPEC-383 Harvesting Information via API Event Monitoring Severity: Low
  • CAPEC-477 Signature Spoofing by Mixing Signed and Unsigned Content Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON