Homepage

Cleartext Transmission of Sensitive Information Affecting vllm-cu130 package, versions <0.27.0-r0

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.08% (1st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-VLLMCU130-19659960
  • published10 Sept 2026
  • disclosed2 Sept 2026
Report a new vulnerability Found a mistake?

Introduced: 2 Sep 2026

NewCVE-2026-84381  (opens in a new tab)
CWE-319  (opens in a new tab)

How to fix?

Upgrade Minimos:latest vllm-cu130 to version 0.27.0-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream vllm-cu130 package and not the vllm-cu130 package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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.