VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

vllm: vulnerability history, versions and safety

vllm is a package in the PyPI ecosystem. Vulert records 171 vulnerabilities for it across 100 releases, from Sep 2024 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
171 vulnerabilities recorded C9 H21 M46 L4 U91
i
22 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
132 in the last 12 months

Most recent disclosure 15 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all vllm vulnerabilities

Vulert verdict on vllm 0.32.0 i

Updated on 23 Oct 2026

Careful: 0.32.0 has 29 known vulnerabilities, and 22 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 50/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 0.32.0 — affected i
  • Vulnerabilities on record 171 over 2 years · 132 in the last year i
  • Latest disclosure 15 Oct 2026 i
  • Highest CVSS 10.0 i
  • With no published fix 22 i
  • Depended on by 95 packages i
  • Stars 94,691 i
  • Last release this month i
  • Licence Apache-2.0 i
  • Similar names llm i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for vllm, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.32.0 18 Oct 2026 C3 H1 M8 U17 Apache-2.0 No Details →
0.31.0 05 Oct 2026 U1 Apache-2.0 Yes Details →
0.30.0 22 Sep 2026 U1 Apache-2.0 Yes Details →
0.29.0 09 Sep 2026 M6 L1 U17 Apache-2.0 Yes Details →
0.28.0 26 Aug 2026 M6 L1 U18 Apache-2.0 Yes Details →
0.27.1 11 Aug 2026 M8 L1 U22 Apache-2.0 Yes Details →
0.27.0 10 Aug 2026 M8 L1 U22 Apache-2.0 Yes Details →
0.26.0 25 Jul 2026 M9 L1 U25 Apache-2.0 Yes Details →
0.25.1 14 Jul 2026 M15 L1 U31 Apache-2.0 Yes Details →
0.25.0 11 Jul 2026 M15 L1 U31 Apache-2.0 Yes Details →
0.24.0 30 Jun 2026 M15 L1 U31 Apache-2.0 Yes Details →
0.23.0 13 Jun 2026 H3 M22 L1 U41 Apache-2.0 No Details →
0.22.1 05 Jun 2026 H3 M21 L1 U40 Apache-2.0 No Details →
0.22.0 29 May 2026 H3 M21 L1 U41 Apache-2.0 No Details →
0.21.0 15 May 2026 C1 H4 M21 L1 U43 Apache-2.0 No Details →
0.20.2 10 May 2026 C1 H4 M20 L1 U42 Apache-2.0 No Details →
0.20.1 03 May 2026 C1 H4 M20 L1 U42 Apache-2.0 No Details →
0.20.0 27 Apr 2026 C1 H4 M20 L1 U42 Apache-2.0 No Details →
0.19.1 18 Apr 2026 C1 H4 M22 L1 U44 Apache-2.0 No Details →
0.19.0 03 Apr 2026 C1 H4 M23 L2 U46 Apache-2.0 No Details →
0.18.1 31 Mar 2026 C1 H5 M25 L2 U49 Apache-2.0 No Details →
0.18.0 20 Mar 2026 C1 H5 M25 L2 U49 Apache-2.0 No Details →
0.17.1 11 Mar 2026 C1 H6 M25 L2 U50 Apache-2.0 No Details →
0.17.0 07 Mar 2026 C1 H5 M25 L2 U49 Apache-2.0 No Details →
0.16.0 26 Feb 2026 C1 H5 M26 L2 U50 Apache-2.0 No Details →
0.15.1 05 Feb 2026 C1 H5 M25 L2 U49 Apache-2.0 No Details →
0.15.0 29 Jan 2026 C1 H5 M24 L2 U48 Apache-2.0 No Details →
0.14.1 24 Jan 2026 C1 H5 M24 L2 U48 Apache-2.0 No Details →
0.14.0 20 Jan 2026 C2 H6 M24 L2 U50 Apache-2.0 No Details →
0.13.0 19 Dec 2025 C2 H7 M24 L2 U51 Apache-2.0 No Details →
0.12.0 03 Dec 2025 C2 H9 M24 L2 U52 Apache-2.0 No Details →
0.11.2 20 Nov 2025 C2 H8 M25 L2 U52 Apache-2.0 No Details →
0.11.1 19 Nov 2025 C2 H8 M25 L2 U52 Apache-2.0 No Details →
0.11.0 04 Oct 2025 C2 H11 M26 L2 U56 Apache-2.0 No Details →
0.10.2 13 Sep 2025 C2 H13 M25 L2 U58 Apache-2.0 No Details →
0.10.1.1 20 Aug 2025 C2 H10 M25 L2 U56 Apache-2.0 No Details →
0.10.1 19 Aug 2025 C2 H12 M25 L2 U58 Apache-2.0 No Details →
0.10.0 25 Jul 2025 C2 H10 M25 L2 U56 Apache-2.0 No Details →
0.9.2 08 Jul 2025 C2 H9 M25 L2 U56 Apache-2.0 No Details →
0.9.1 10 Jun 2025 C2 H9 M25 L2 U56 Apache-2.0 No Details →
0.9.0.1 30 May 2025 C2 H9 M25 L2 U56 Apache-2.0 No Details →
0.9.0 28 May 2025 C2 H9 M25 L2 U56 Apache-2.0 No Details →
0.8.5.post1 02 May 2025 C2 H10 M32 L3 U62 Apache-2.0 No Details →
0.8.5 28 Apr 2025 C2 H10 M32 L3 U62 Apache-2.0 No Details →
0.8.4 15 Apr 2025 C4 H11 M33 L3 U66 non-standard No Details →
0.8.3 06 Apr 2025 C4 H11 M34 L3 U66 non-standard No Details →
0.8.2 25 Mar 2025 C3 H11 M34 L3 U65 non-standard No Details →
0.8.1 19 Mar 2025 C4 H11 M34 L3 U66 non-standard No Details →
0.8.0 18 Mar 2025 C4 H11 M34 L3 U66 non-standard No Details →
0.7.3 20 Feb 2025 C6 H10 M31 L3 U63 non-standard No Details →
0.7.2 06 Feb 2025 C6 H10 M31 L3 U63 Apache-2.0 No Details →
0.7.1 01 Feb 2025 C6 H10 M31 L4 U64 Apache-2.0 No Details →
0.7.0 27 Jan 2025 C6 H10 M31 L4 U64 Apache-2.0 No Details →
0.6.6.post1 27 Dec 2024 C6 H11 M29 L4 U64 Apache-2.0 No Details →
0.6.6 27 Dec 2024 C6 H11 M29 L4 U64 Apache-2.0 No Details →
0.6.5 18 Dec 2024 C6 H11 M29 L4 U64 Apache-2.0 No Details →
0.6.4.post1 15 Nov 2024 C3 H11 M28 L4 U61 Apache-2.0 No Details →
0.6.4 15 Nov 2024 C3 H11 M28 L4 U61 Apache-2.0 No Details →
0.6.3.post1 17 Oct 2024 C3 H11 M26 L4 U59 Apache-2.0 No Details →
0.6.3 14 Oct 2024 C3 H11 M26 L4 U59 Apache-2.0 No Details →
0.6.2 25 Sep 2024 C4 H11 M24 L4 U60 Apache-2.0 No Details →
0.6.1.post2 13 Sep 2024 C4 H11 M24 L4 U60 Apache-2.0 No Details →
0.6.1.post1 13 Sep 2024 C4 H11 M24 L4 U60 Apache-2.0 No Details →
0.6.1 11 Sep 2024 C4 H11 M24 L4 U60 Apache-2.0 No Details →
0.6.0 05 Sep 2024 C5 H11 M23 L4 U59 Apache-2.0 No Details →
0.5.5 23 Aug 2024 C5 H11 M23 L4 U59 Apache-2.0 No Details →
0.5.4 05 Aug 2024 C5 H11 M20 L4 U56 Apache-2.0 No Details →
0.5.3.post1 23 Jul 2024 C5 H11 M20 L4 U56 Apache-2.0 No Details →
0.5.3 23 Jul 2024 C5 H11 M20 L4 U56 Apache-2.0 No Details →
0.5.2 15 Jul 2024 C5 H11 M20 L4 U56 Apache-2.0 No Details →
0.5.1 06 Jul 2024 C5 H9 M20 L4 U54 Apache-2.0 No Details →
0.5.0.post1 14 Jun 2024 C5 H9 M20 L4 U54 Apache-2.0 No Details →
0.5.0 11 Jun 2024 C5 H9 M20 L4 U54 Apache-2.0 No Details →
0.4.3 01 Jun 2024 C5 H8 M20 L4 U53 Apache-2.0 No Details →
0.4.2 05 May 2024 C5 H8 M20 L4 U53 Apache-2.0 No Details →
0.4.1 24 Apr 2024 C5 H8 M20 L4 U53 Apache-2.0 No Details →
0.4.0.post1 03 Apr 2024 C5 H8 M20 L4 U53 Apache-2.0 No Details →
0.4.0 31 Mar 2024 C5 H8 M20 L4 U53 Apache-2.0 No Details →
0.3.3 01 Mar 2024 C5 H8 M20 L4 U53 Apache-2.0 No Details →
0.3.2 21 Feb 2024 C5 H8 M20 L4 U53 Apache-2.0 No Details →
0.3.1 17 Feb 2024 C5 H8 M20 L4 U53 Apache-2.0 No Details →
0.3.0 31 Jan 2024 C5 H8 M20 L4 U53 Apache-2.0 No Details →
0.2.7 04 Jan 2024 C4 H8 M20 L4 U52 Apache-2.0 No Details →
0.2.6 17 Dec 2023 C4 H8 M20 L4 U52 Apache-2.0 No Details →
0.2.5 14 Dec 2023 C4 H8 M20 L4 U52 Apache-2.0 No Details →
0.2.4 11 Dec 2023 C4 H8 M20 L4 U52 Apache-2.0 No Details →
0.2.3 03 Dec 2023 C4 H8 M20 L4 U52 Apache-2.0 No Details →
0.2.2 19 Nov 2023 C4 H8 M20 L4 U52 Apache-2.0 No Details →
0.2.1.post1 17 Oct 2023 C4 H8 M20 L4 U52 Apache-2.0 No Details →
0.2.1 16 Oct 2023 C4 H8 M20 L4 U52 Apache-2.0 No Details →
0.2.0 28 Sep 2023 C4 H8 M20 L4 U52 Apache-2.0 No Details →
0.1.7 11 Sep 2023 C4 H8 M20 L4 U52 Apache-2.0 No Details →
0.1.6 08 Sep 2023 C4 H8 M20 L4 U52 Apache-2.0 No Details →
0.1.5 08 Sep 2023 C4 H8 M20 L4 U52 Apache-2.0 No Details →
0.1.4 25 Aug 2023 C4 H8 M20 L4 U52 Apache-2.0 No Details →
0.1.3 02 Aug 2023 C4 H8 M20 L4 U52 Apache-2.0 No Details →
0.1.2 05 Jul 2023 C4 H8 M20 L4 U52 Apache-2.0 No Details →
0.1.1 22 Jun 2023 C4 H8 M20 L4 U52 Apache-2.0 No Details →
0.1.0 20 Jun 2023 C4 H8 M20 L4 U52 Apache-2.0 No Details →
0.0.1 19 Jun 2023 C4 H7 M19 L4 U50 Apache-2.0 No Details →

All 100 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 2
  • 2025 41
  • 2026 128

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 132 of the 171 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for vllm

The 5 most severe of 171 vulnerabilities recorded for this package

Search all 171 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-32444: vLLM Remote Code Execution Vulnerability via Mooncake Integration 10.0 critical 0.8.5 29 Apr 2025
CVE-2026-22778: vLLM Remote Code Execution Vulnerability in Video Processing 9.8 critical 0.14.1 29 Jun 2026
Critical Remote Code Execution Vulnerability in vLLM Due to JPEG2000 Decoder Flaw 9.8 critical 0.14.1 02 Feb 2026
CVE-2024-11041: vLLM Remote Code Execution Vulnerability Due to Untrusted Data Deserialization 9.8 critical No fix published 29 Jun 2026
Remote Code Execution Vulnerability in vLLM Package 9.8 critical a5450f11c95847cf51a17207af9a3ca5ab569b2c 30 Apr 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About vllm

Is vllm safe to use?

Vulert records 171 vulnerabilities for vllm in PyPI: 9 critical, 21 high, 46 medium and 4 low, plus 91 not yet rated. 22 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is vllm's Vulert package health score?

Vulert scores vllm 50/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of vllm affected?

Yes. 0.32.0, the version you would install today, has 29 known vulnerabilities, and 22 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of vllm should I use?

0.32.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does vllm have?

171 vulnerabilities are recorded for vllm in the PyPI ecosystem: 9 critical, 21 high, 46 medium and 4 low, plus 91 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new vllm vulnerabilities disclosed?

132 vulnerabilities were recorded for vllm in the last 12 months, and the oldest entry in this database dates to 17 Sep 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of vllm are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor vllm for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the vllm version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.