vLLM vulnerabilities: known CVEs & security history
vLLM · AI / ML · 92 tracked CVEs · 0 actively exploited · updated November 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all vLLM release lines — 92 in total. A CVE here doesn't mean your version is affected — check vLLM's current status and the safe version to run.
Known vLLM CVEs
Actively-exploited and most-severe first. Showing the top 80 of 92. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2026-22778 | critical | 9.8 | 4% | 2026 |
| CVE-2026-48746 | critical | 9.1 | 1% | 2026 |
| CVE-2026-54232 | high | 8.8 | 1% | 2026 |
| CVE-2026-56340 | high | 8.8 | 1% | 2026 |
| CVE-2026-27893 | high | 8.8 | 1% | 2026 |
| CVE-2026-22807 | high | 8.8 | 1% | 2026 |
| CVE-2025-62164 | high | 8.8 | 1% | 2025 |
| CVE-2026-116176 | high | 8.2 | 0% | 2026 |
| CVE-2026-115915 | high | 8.1 | 1% | 2026 |
| CVE-2026-90553 | high | 7.8 | 0% | 2026 |
| CVE-2026-116180 | high | 7.7 | 0% | 2026 |
| CVE-2026-115912 | high | 7.5 | 0% | 2026 |
| CVE-2026-116179 | high | 7.5 | 0% | 2026 |
| CVE-2026-116177 | high | 7.5 | 0% | 2026 |
| CVE-2026-94627 | high | 7.5 | — | 2026 |
| CVE-2026-94626 | high | 7.5 | — | 2026 |
| CVE-2026-94624 | high | 7.5 | — | 2026 |
| CVE-2026-94623 | high | 7.5 | — | 2026 |
| CVE-2026-94622 | high | 7.5 | — | 2026 |
| CVE-2026-93592 | high | 7.5 | — | 2026 |
| CVE-2026-93436 | high | 7.5 | — | 2026 |
| CVE-2026-37237 | high | 7.5 | — | 2026 |
| CVE-2026-55574 | high | 7.5 | 1% | 2026 |
| CVE-2026-54234 | high | 7.5 | 1% | 2026 |
| CVE-2026-53923 | high | 7.5 | 0% | 2026 |
| CVE-2026-41523 | high | 7.5 | 1% | 2026 |
| CVE-2026-5497 | high | 7.5 | 1% | 2026 |
| CVE-2025-59425 | high | 7.5 | 1% | 2025 |
| CVE-2026-25960 | high | 7.1 | 0% | 2026 |
| CVE-2026-24779 | high | 7.1 | 1% | 2026 |
| CVE-2025-66448 | high | 7.1 | 1% | 2025 |
| CVE-2026-115918 | medium | 6.5 | 0% | 2026 |
| CVE-2026-115916 | medium | 6.5 | 0% | 2026 |
| CVE-2026-115914 | medium | 6.5 | 0% | 2026 |
| CVE-2026-115913 | medium | 6.5 | 0% | 2026 |
| CVE-2026-115911 | medium | 6.5 | 0% | 2026 |
| CVE-2026-116181 | medium | 6.5 | 0% | 2026 |
| CVE-2026-116175 | medium | 6.5 | 0% | 2026 |
| CVE-2026-105757 | medium | 6.5 | 0% | 2026 |
| CVE-2026-105756 | medium | 6.5 | 0% | 2026 |
| CVE-2026-105754 | medium | 6.5 | 0% | 2026 |
| CVE-2026-105753 | medium | 6.5 | 0% | 2026 |
| CVE-2026-100654 | medium | 6.5 | 0% | 2026 |
| CVE-2026-100653 | medium | 6.5 | 0% | 2026 |
| CVE-2026-100651 | medium | 6.5 | 0% | 2026 |
| CVE-2026-100650 | medium | 6.5 | 1% | 2026 |
| CVE-2026-69147 | medium | 6.5 | 1% | 2026 |
| CVE-2026-57173 | medium | 6.5 | 1% | 2026 |
| CVE-2026-90555 | medium | 6.5 | 0% | 2026 |
| CVE-2026-73560 | medium | 6.5 | 0% | 2026 |
| CVE-2026-73559 | medium | 6.5 | — | 2026 |
| CVE-2026-55514 | medium | 6.5 | 1% | 2026 |
| CVE-2026-55646 | medium | 6.5 | 1% | 2026 |
| CVE-2026-54235 | medium | 6.5 | 0% | 2026 |
| CVE-2026-54233 | medium | 6.5 | 0% | 2026 |
| CVE-2026-47155 | medium | 6.5 | 0% | 2026 |
| CVE-2026-44223 | medium | 6.5 | 0% | 2026 |
| CVE-2026-34756 | medium | 6.5 | 0% | 2026 |
| CVE-2026-34755 | medium | 6.5 | 0% | 2026 |
| CVE-2025-62426 | medium | 6.5 | 1% | 2025 |
| CVE-2025-62372 | medium | 6.5 | 0% | 2025 |
| CVE-2026-90554 | medium | 6.2 | 0% | 2026 |
| CVE-2026-116178 | medium | 5.9 | 0% | 2026 |
| CVE-2026-116174 | medium | 5.9 | 0% | 2026 |
| CVE-2026-116173 | medium | 5.9 | 0% | 2026 |
| CVE-2026-116172 | medium | 5.9 | 0% | 2026 |
| CVE-2026-105759 | medium | 5.9 | 0% | 2026 |
| CVE-2026-100652 | medium | 5.9 | 0% | 2026 |
| CVE-2026-34760 | medium | 5.9 | 0% | 2026 |
| CVE-2026-7141 | medium | 5.6 | 0% | 2026 |
| CVE-2026-105760 | medium | 5.3 | 0% | 2026 |
| CVE-2026-105758 | medium | 5.3 | 0% | 2026 |
| CVE-2026-103241 | medium | 5.3 | 1% | 2026 |
| CVE-2026-100648 | medium | 5.3 | 0% | 2026 |
| CVE-2026-100647 | medium | 5.3 | 0% | 2026 |
| CVE-2026-94625 | medium | 5.3 | — | 2026 |
| CVE-2026-78684 | medium | 5.3 | — | 2026 |
| CVE-2026-73558 | medium | 5.3 | — | 2026 |
| CVE-2026-73557 | medium | 5.3 | 0% | 2026 |
| CVE-2026-73556 | medium | 5.3 | — | 2026 |
12 older / lower-severity CVEs not shown — see vLLM's full record.
Is my vLLM version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your vLLM version → · Monitor vLLM for new CVEs →
vLLM vulnerabilities — frequently asked
How many known vulnerabilities does vLLM have?
IsItPatched tracks 92 CVEs for vLLM. 2 are critical-severity and 29 high-severity. These span every release line — what matters is whether the version you run is affected.
Does vLLM have any actively-exploited vulnerabilities?
None of vLLM's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.
What is the most severe vLLM vulnerability?
Among tracked issues, CVE-2026-22778 (CRITICAL, CVSS 9.8) ranks highest — a CWE-532 weakness.
Is vLLM safe to use?
It depends on the version. The latest supported vLLM release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: vLLM security status · vLLM end-of-life · actively-exploited CVEs. Always verify against vLLM's advisories — see our disclaimer.