CVE-2026-94626: vLLM Memory Exhaustion via Unvalidated tp_size Parameter
vLLM
An input validation failure in vLLM allows attackers to supply arbitrary tp_size values on completion endpoints. This leads to unbounded memory allocation and kernel OOM-kill of decode worker processes.
disclosed CVENo confirmed exploitation, so this record is tracked as a disclosed vulnerability and not counted as an incident. It moves into the counts if CISA or the vendor confirms exploitation. Why
- CVSS
- 8.7
- EPSS
- 0.01 · top 50% · 2026-11-13
- fix status
- Fix status unknown
- first report
- 21 Sep 2026
- last update
- 21 Sep 2026
- CVE ids
Timeline · 1
Sources · 1
Advisories and databases
- 2026-09-21CVE-2026-94626: vLLM through 0.29.0 fails to validate the tp_size parameter in kv_transfer_params on OpenAI-compatible completion endpoints,…NVD · nvd.nist.gov/vuln/detail/CVE-2026-94626
Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.
Classification
- lane
- Patch now
- AI role
- Attack on AI
- categories
- Infrastructure vulnerability
- severity
- 2 · Disclosed vulnerability
- fix status
- Fix status unknown
- targets
- Framework / tooling
- owasp llm top 10
- LLM03:2025 Supply Chain
- mitre atlas
- no technique for these categories
- dates
- happened 21 Sep 2026 · first reported 21 Sep 2026
- origin
- NVDVulnerability record from NVD / the GitHub Advisory Database. This product uses the NVD API but is not endorsed or certified by the NVD.
- record
- confidence 0.95 · created 2026-10-18 06:33Z · updated 2026-10-18 06:33Z
Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned
Copy a brief
This record as a short Markdown brief, for a ticket, a chat or a coding agent.
the brief as text
# CVE-2026-94626: vLLM Memory Exhaustion via Unvalidated tp_size Parameter https://gcdradar.vercel.app/incidents/cve-2026-94626-vllm-memory-exhaustion-via-unvalidated-tp-siz · AIR-2026-0159 · closed 2026-09-21 - Lane: Patch now - Severity: 2 (Disclosed vulnerability) - Fix status: Fix status unknown - First reported: 2026-09-21 - AI role: Attack on AI - Products: vLLM - CVE ids: CVE-2026-94626 - CVSS: 8.7 ## Summary An input validation failure in vLLM allows attackers to supply arbitrary tp_size values on completion endpoints. This leads to unbounded memory allocation and kernel OOM-kill of decode worker processes. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2026-09-21: CVE-2026-94626: vLLM through 0.29.0 fails to validate the tp_size parameter in kv_transfer_params on OpenAI-compatible completion endpoints,… (https://nvd.nist.gov/vuln/detail/CVE-2026-94626) ## Sources - 2026-09-21 NVD: CVE-2026-94626: vLLM through 0.29.0 fails to validate the tp_size parameter in kv_transfer_params on OpenAI-compatible completion endpoints,… https://nvd.nist.gov/vuln/detail/CVE-2026-94626 Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closedvLLM vLLM Denial of Service through Multimodal UUID Cache Desynchronization
Patch now · Disclosed · since 21 Oct 2026
AI - closedvLLM vLLM Denial of Service via Unvalidated mm_processor_kwargs
Patch now · Disclosed · since 21 Oct 2026
AI - closed6.5vLLM CVE-2026-114050: vLLM multimodal UUID cache identity flaw leads to engine crash
Patch now · Disclosed · since 21 Oct 2026 · updated 23 Oct 2026 · CVE-2026-114050
AI - closed7.1vLLM CVE-2026-114054: vLLM cache aliasing vulnerability exposes processed media and KV state
Patch now · Disclosed · since 21 Oct 2026 · CVE-2026-114054
AI - closed7.5vLLM CVE-2026-114051: vLLM input validation check omission causes denial of service
Patch now · Disclosed · since 21 Oct 2026 · CVE-2026-114051
AI - closed6.3vLLM CVE-2026-114049: vLLM cross-request mask leak vulnerability
Patch now · Disclosed · since 21 Oct 2026 · CVE-2026-114049
AI