Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

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

Quick assessment

Affected
pydantic httpx2
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

HTTPX2 是 Python 的下一代 HTTP 客户端。在 2.10.0 之前，当远程源通过 SOCKS5 代理使用 wss 协议时，httpcore2 在 和 中未能正确启动 TLS，因为其 TLS 升级条件仅识别 协议。HTTPX2 从 2.6.0 到 2.9.1 通过 和 暴露了这一缺陷，导致初始握手、查询参数、Authorization 头部、Cookie 以及后续的 WebSocket 数据帧可能以明文形式经过代理路径传输，且没有进行证书验证。控制或监视该路径的攻击者可以读取或修改流量，并冒充 Web

CVSS 8.1 · High

Affected Version Matrix 2

VendorProduct Version RangeStatus
pydantic httpcore2 < 2.10.0 affected
pydantic httpx2 >= 2.6.0, < 2.10.0 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-84381

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
HTTPX2: Secure WebSocket traffic sent without TLS through SOCKS proxies
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
敏感数据的明文传输
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
pydantic httpx2 >= 2.6.0, < 2.10.0 -
pydantic httpcore2 < 2.10.0 -

II. Public POCs for CVE-2026-84381

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-84381

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-84381 (2)

Vendor Advisories for CVE-2026-84381 (1)

Same Patch Batch · pydantic · 2026-09-02 · 5 CVEs total

CVE-2026-84382 7.5 HIGH HTTPX2: Streaming response decompression does not bound peak memory (decompression amplifi
CVE-2026-84378 5.9 MEDIUM HTTPX2: Quadratic SSE line buffering can cause CPU denial of service
CVE-2026-84380 5.6 MEDIUM HTTPX2: Conflicting Content-Length and Transfer-Encoding headers can be auto-generated
CVE-2026-84379 5.3 MEDIUM HTTPX2: Multipart part header injection via unvalidated file Content-Type and custom heade

IV. Related Vulnerabilities

Same product: httpx2
Same vendor: pydantic
Same weakness: CWE-319

V. Comments for CVE-2026-84381

No comments yet

Leave a comment