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.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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. (CVE-2026-84381)

Note that Nessus relies on the presence of the package as reported by the vendor.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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. (CVE-2026-84381)

ID	Name	Product	Family	Type	Severity
374564	Linux Distros Unpatched Vulnerability : CVE-2026-84381	Nessus	Misc.	Local	high
472226	Echo: httpcore2: security update to 2.10.0	Tenable Cloud Security	Echo Local Security Checks	Local	high
472226	Echo: httpcore2: security update to 2.10.0	Tenable Self-Hosted Container Security	Echo Local Security Checks	Local	high

Detections

Analytics

CVE-2026-84381

high

Tenable Plugins

high

high

high