LowGHSA-vvpg-rrww-wpmhCVE-2026-115917PYSEC-2026-4348

vLLM: Permissive default CORS origins allow cross-origin requests to the vLLM HTTP server

Published 28 Oct 2026 · Updated 29 Oct 2026

Is your project on an affected vllm?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

vllmPyPI
Affected
<0.32.0
Fixed in
0.32.0
Update to the fixed version for your release line, for example:pip install 'vllm>=0.32.0'

Details

Summary

The OpenAI-compatible server registers Starlette CORSMiddleware with allowed_origins defaulting to ["*"], and performs no authentication unless --api-key (or VLLM_API_KEY) is configured. A web page on any origin can send requests to a vLLM server that the victim's browser can reach (for example localhost or an internal/VPN address) and read the responses. The default allow_credentials=False blocks cookie-bearing cross-origin requests; because vLLM authenticates with a bearer header rather than cookies, the wildcard still permits untokenized access to an unauthenticated server and read access when the caller already holds a token.

Details

Affected components

  • vllm/entrypoints/launchers/cli_args.py - allowed_origins default value.
  • vllm/entrypoints/serve/middleware/register.py - CORSMiddleware registration.
  • vllm/entrypoints/serve/middleware/authenticate.py - auth middleware and its guarded path prefixes.

Root cause

vllm/entrypoints/launchers/cli_args.py:

allow_credentials: bool = False
"""Allow credentials."""
allowed_origins: list[str] = field(default_factory=lambda: ["*"])
"""Allowed origins."""

vllm/entrypoints/serve/middleware/register.py:

app.add_middleware(
    CORSMiddleware,
    allow_origins=args.allowed_origins,
    allow_credentials=args.allow_credentials,
    allow_methods=args.allowed_methods,
    allow_headers=args.allowed_headers,
)

The auth middleware is added only when a token is configured and guards only the /v1, /v2, /inference, and /cohere prefixes. /v1/load_lora_adapter and /v1/unload_lora_adapter are inside /v1 and therefore do require a key when one is set; they are open only when no key is configured and dynamic LoRA updating is enabled.

Impact

  • A malicious page can enumerate models (GET /v1/models), issue POST /v1/chat/completions, consume GPU time, and read model output through the victim's browser.
  • When the server is reachable only from the victim's network, the browser acts as a proxy a remote website could not otherwise use.
  • With allow_credentials=False, cookie-based CSRF does not apply; the exposure is cross-origin request execution and response disclosure.

This advisory was fixed in MR61009.

Is GHSA-vvpg-rrww-wpmh in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected vllm, and gives you the command that fixes it.

More advisories for vllm

  • MediumCVE-2026-115913vLLM: Phi-4 multimodal audio encoder materializes and retains full attention matrices: a single max-length audio OOM-crashes the vLLM engine · 28 Oct 2026
  • MediumCVE-2026-115914vLLM DeepSeek-OCR image processing vulnerable to denial of service · 28 Oct 2026
  • HighCVE-2026-115915vLLM: Untrusted EPS inputs can trigger denial of service or Ghostscript RCE · 28 Oct 2026
  • HighCVE-2026-115912vLLM: Public multimodal SHM handle forgery reaches worker-side `pickle.loads()` with insecure serialization disabled · 28 Oct 2026
  • MediumCVE-2026-115916vLLM: Out-of-vocabulary prompt token id passes input validation and triggers a CUDA device-side assert (engine crash / DoS) · 28 Oct 2026
  • MediumCVE-2026-115918vLLM: Responses API bypasses trust_request_chat_template for chat_template_kwargs · 28 Oct 2026
All 113 advisories for vllm

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.