vllm-project · vLLM · published 2026-10-26
CVE-2026-115917vLLM: Permissive default CORS origins allow cross-origin requests to the vLLM HTTP server
Routine No exploitation evidence; EPSS 0.2%.
CVE-2026-115917 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 15% of all CVEs. This vLLM vulnerability: CVSS 3.4 (v3.1). Fixed upstream in vLLM 0.32.0. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in vLLM 0.32.0.
Patch events
AI toolingvLLM
vLLM security release: 0.32.0
Upgrade to
0.32.0Why: Vendor security release for server software (most severe: CVE-2026-94624).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.2% (15th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 3.4 (v3.1)CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- vllm-project vllm
< 0.32.0(affected)
Description (from the CVE record)#
vLLM is an inference and serving engine for large language models. Prior to 0.32.0, the OpenAI-compatible server configures Starlette CORSMiddleware with allowed_origins set to a wildcard by default. A malicious web page can use a victim's browser to reach an unauthenticated vLLM server on localhost, an internal network, or a VPN, call endpoints including GET /v1/models and POST /v1/chat/completions, consume GPU resources, and read responses. Cookie-based cross-site request forgery does not apply because credentials are disabled by default, and deployments requiring bearer authentication are exposed only when the caller already has a usable token. This issue is fixed in version 0.32.0.
Quoted from the CVE Program record.