UTC
Medium

vLLM: Unauthenticated Internal Path and Username Disclosure via Validation Error Messages

CVE-2026-73555 · GHSA-hwrm-c4cx-rf4j · published 2026-09-04

Severity
Medium
CVSS score
5.3
Chance of exploitation (EPSS)
0.41%
Fixed in
0.26.0
  • Exploitation No known exploitation
  • Automatable Yes
  • Technical impact Partial
  • CISA SSVC
What it is

An unauthenticated attacker can extract the following with a single malformed request: OS username running the vLLM process (e.g., ubuntu) Home directory path (e.g., /home/ubuntu/) Virtual environment path (e.g., vllm-env/) Python version (e.g., 3.12) Internal package structure and line numbers (e.g., ) Handler function names per endpoint, enabling precise version fingerprinting This information aids attackers in constructing targeted exploits: environment paths narrow the attack surface, and handler function names + line numbers enable exact version identification even when the /version endpoint is disabled.

What to do

Upgrade vllm to 0.26.0 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

Two possible fixes (either suffices): Option A — Fix validationexceptionhandler: Construct the error message from exc.errors() (the structured Pydantic error list) rather than str(exc). This avoids the traceback-style string entirely. Option B — Fix sanitizemessage:** Add a regex to strip File "...", line \d+ patterns, similar to how memory addresses are already stripped: Option A is preferred as it addresses the root cause rather than filtering symptoms.

If you cannot upgrade yet

Deploying vLLM behind a reverse proxy that rewrites error response bodies to strip file paths would mitigate this, though it is fragile.

Affected
PackageRegistryAffectedFixed in
vllmPyPI< 0.26.00.26.0

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].