Summary iPlain-English security verdict for vLLM, generated from its current health score, actively-exploited vulnerabilities, and latest supported version.
vLLM currently scores 20/100 — high risk. No tracked vulnerabilities are currently known to be exploited in the wild. Upgrade soon — serious vulnerabilities are open and a fix usually exists.
Disclosure trend iNew CVEs published for vLLM each year (NVD). A higher bar means more disclosures that year — more scrutiny, not necessarily less safe.
Patch priority — what to act on iThe issues to fix first — actively exploited (CISA KEV) first, then by exploitation probability (EPSS), then severity. Each row's "→ fixed in" is the earliest version that patches it; "see advisory" means no fixed version is published.
Most urgent first — actively exploited, then likeliest to be exploited.
CVE-2026-22778 CRITICAL CWE-532 EPSS 4% → fixed in 0.14.1 CVE-2026-48746 CRITICAL CWE-444 EPSS 1% → fixed in 0.22.0Get alerted about vLLM
Be emailed the moment vLLM gets a newly exploited vulnerability (CISA KEV) or a release reaches end of life. Free · double opt-in · unsubscribe anytime.
We email only on real events for vLLM — no marketing, no sharing, and we never know what you run. Track your whole stack →
Frequently asked
Is vLLM safe and patched?
vLLM currently scores 20/100 — high risk. No tracked vulnerabilities are currently known to be exploited in the wild. Upgrade soon — serious vulnerabilities are open and a fix usually exists.
What should I do about vLLM now?
Review the patch-priority list, apply the available fixes (or move to the latest release), and confirm against vLLM's official advisory.
lifecycle unknown — needs latest supported version
Informational only, from public data (NVD · CISA KEV · EPSS · endoflife.date), and can lag or miss vendor-specific fixes. Always confirm against vLLM's official advisory before you patch or upgrade — vLLM official site ↗