VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

lmdeploy: vulnerability history, versions and safety

lmdeploy is a package in the PyPI ecosystem. Vulert records 19 vulnerabilities for it across 58 releases, from Apr 2025 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
19 vulnerabilities recorded C2 H6 M2 U9
i
8 with no fix published

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

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

Most recent disclosure 01 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all lmdeploy vulnerabilities

Vulert verdict on lmdeploy 0.18.0 i

Updated on 23 Oct 2026

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

Package health score 45/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

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.18.0 — affected i
  • Vulnerabilities on record 19 over 1 year · 17 in the last year i
  • Latest disclosure 01 Oct 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 8 i
  • Depended on by 1 packages i
  • Last release this month i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 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 lmdeploy, 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.18.0 28 Sep 2026 H2 M2 U4 — No Details →
0.17.0 02 Sep 2026 H2 M2 U4 — No Details →
0.16.0 19 Aug 2026 H2 M2 U4 — No Details →
0.15.0 31 Jul 2026 C1 U1 — Yes Details →
0.14.0 24 Jun 2026 C1 H1 U1 — Yes Details →
0.13.0 12 May 2026 C1 H1 U1 — Yes Details →
0.12.3 22 Apr 2026 C1 H3 U3 — No Details →
0.12.2 18 Mar 2026 C1 H4 U5 — No Details →
0.12.1 13 Feb 2026 C1 H4 U5 — No Details →
0.12.0 04 Feb 2026 C1 H3 U4 — No Details →
0.11.1 24 Dec 2025 C1 H3 U4 — No Details →
0.11.0 04 Dec 2025 C1 H4 U5 — No Details →
0.10.2 28 Oct 2025 C1 H4 U5 — No Details →
0.10.1 26 Sep 2025 C2 H4 U6 — No Details →
0.10.0 09 Sep 2025 C2 H4 U6 — No Details →
0.9.2.post1 25 Aug 2025 C2 H4 U6 — No Details →
0.9.2 26 Jul 2025 C2 H4 U6 — No Details →
0.9.1 04 Jul 2025 C1 H4 U5 — No Details →
0.9.0 19 Jun 2025 H4 U4 — No Details →
0.8.0 04 May 2025 H4 U4 Apache-2.0 No Details →
0.7.3 14 Apr 2025 H4 U4 Apache-2.0 No Details →
0.7.2.post1 21 Mar 2025 H4 U4 Apache-2.0 No Details →
0.7.2 19 Mar 2025 H4 U4 Apache-2.0 No Details →
0.7.1 27 Feb 2025 H4 M2 U6 Apache-2.0 No Details →
0.7.0.post3 10 Feb 2025 H4 M2 U6 Apache-2.0 No Details →
0.7.0.post2 27 Jan 2025 H4 M2 U6 Apache-2.0 No Details →
0.7.0.post1 25 Jan 2025 H4 M2 U6 Apache-2.0 No Details →
0.7.0 15 Jan 2025 H4 M2 U6 Apache-2.0 No Details →
0.6.5 30 Dec 2024 H4 M2 U6 Apache-2.0 No Details →
0.6.4 09 Dec 2024 H4 M2 U6 Apache-2.0 No Details →
0.6.3 16 Nov 2024 H4 M2 U6 Apache-2.0 No Details →
0.6.2.post1 07 Nov 2024 H4 M2 U6 Apache-2.0 No Details →
0.6.2 29 Oct 2024 H4 M2 U6 Apache-2.0 No Details →
0.6.1 28 Sep 2024 H4 M2 U6 Apache-2.0 No Details →
0.6.0 13 Sep 2024 H4 M2 U6 Apache-2.0 No Details →
0.6.0a0 26 Aug 2024 H4 M2 U6 Apache-2.0 No Details →
0.5.3 07 Aug 2024 H4 M2 U6 Apache-2.0 No Details →
0.5.2.post1 28 Jul 2024 H4 M2 U6 Apache-2.0 No Details →
0.5.2 26 Jul 2024 H4 M2 U6 Apache-2.0 No Details →
0.5.1 16 Jul 2024 H4 M2 U6 Apache-2.0 No Details →
0.5.0 01 Jul 2024 H4 M2 U6 Apache-2.0 No Details →
0.4.2 27 May 2024 H4 M2 U6 Apache-2.0 No Details →
0.4.1 07 May 2024 H4 M2 U6 Apache-2.0 No Details →
0.4.0 23 Apr 2024 H4 M2 U6 Apache-2.0 No Details →
0.3.0 03 Apr 2024 H4 M2 U6 Apache-2.0 No Details →
0.2.6 19 Mar 2024 H4 M2 U6 Apache-2.0 No Details →
0.2.5 05 Mar 2024 H4 M2 U6 Apache-2.0 No Details →
0.2.4 22 Feb 2024 H4 M2 U6 Apache-2.0 No Details →
0.2.3 06 Feb 2024 H4 M2 U6 Apache-2.0 No Details →
0.2.2 31 Jan 2024 H4 M2 U6 Apache-2.0 No Details →
0.2.1 19 Jan 2024 H4 M2 U6 Apache-2.0 No Details →
0.2.0 17 Jan 2024 H4 M2 U6 Apache-2.0 No Details →
0.1.0 18 Dec 2023 H4 M2 U6 Apache-2.0 No Details →
0.0.14 09 Nov 2023 H4 M2 U6 Apache-2.0 No Details →
0.0.13 30 Oct 2023 H4 M2 U6 Apache-2.0 No Details →
0.0.12 24 Oct 2023 H4 M2 U6 Apache-2.0 No Details →
0.0.11 17 Oct 2023 H4 M2 U6 Apache-2.0 No Details →
0.0.10 26 Sep 2023 H4 M2 U6 Apache-2.0 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 3
  • 2026 16

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

03 Vulnerabilities

Recorded vulnerabilities for lmdeploy

The 5 most severe of 19 vulnerabilities recorded for this package

Search all 19 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-66455: LMDeploy Remote Code Execution via Pickle Deserialization 9.8 critical 0.16.0 18 Sep 2026
CVE-2025-59953: LMdeploy Remote Code Execution via Pickle Deserialization 9.8 critical 0.10.2 01 Oct 2026
CVE-2025-59953: LMdeploy Remote Code Execution via Pickle Deserialization 9.8 critical 0.10.2 16 Sep 2026
CVE-2025-66455: LMDeploy Remote Code Execution via Pickle Deserialization 9.8 critical 0.16.0 01 Oct 2026
CVE-2025-67729: lmdeploy Arbitrary Code Execution via Insecure Deserialization 8.8 high 0.11.1 07 Jul 2026

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 lmdeploy

Is lmdeploy safe to use?

Vulert records 19 vulnerabilities for lmdeploy in PyPI: 2 critical, 6 high, 2 medium and 0 low, plus 9 not yet rated. 8 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is lmdeploy's Vulert package health score?

Vulert scores lmdeploy 45/100, which reads as risky. 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 lmdeploy affected?

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

Which version of lmdeploy should I use?

0.18.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 lmdeploy have?

19 vulnerabilities are recorded for lmdeploy in the PyPI ecosystem: 2 critical, 6 high, 2 medium and 0 low, plus 9 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 lmdeploy vulnerabilities disclosed?

17 vulnerabilities were recorded for lmdeploy in the last 12 months, and the oldest entry in this database dates to 03 Apr 2025. 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 lmdeploy 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 lmdeploy for upcoming vulnerabilities?

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