CVE-2026-9540: vllm · Denial of Service
Affects vllmSource CVE Database V5
Public exploit available · CVSS 6.9 Medium.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 26 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| vllm-projectvllm | Affected
| Fixed in– |
PyPIvllmpkg:pypi/vllmOther threats | Affected
| Fixed in– |
CPE configurations (1)
cpe:2.3:a:vllm-project:vllm:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A pull request addressing the issue is pending acceptance. Users should monitor the vendor's repository or advisory channels for the official patch. Until then, consider limiting exposure of the vulnerable service to untrusted networks to reduce risk.
Description
CVE-2026-9540 is a denial of service vulnerability in vllm-project vllm version 0.19.0. It involves an issue in the OpenAI-compatible Serving Path component that can be exploited remotely without authentication. A public exploit exists, but the fix is pending acceptance in a pull request.
References
- vuldb.com/vuln/365601 (opens in a new tab)
- vuldb.com/vuln/365601/cti (opens in a new tab)
- vuldb.com/submit/814645 (opens in a new tab)
- github.com/vllm-project/vllm/issues/37343 (opens in a new tab)
- github.com/vllm-project/vllm/pull/37594 (opens in a new tab)
- ingero.io/debugging-vllm-latency-minimax-ollama-mcp/ (opens in a new tab)
- github.com/vllm-project/vllm/ (opens in a new tab)