VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

lollms: vulnerability history, versions and safety

lollms is a package in the PyPI ecosystem. Vulert records 44 vulnerabilities for it across 120 releases, from May 2024 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
44 vulnerabilities recorded C4 H10 M5 L1 U24
i
17 with no fix published

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

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

Most recent disclosure 13 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all lollms vulnerabilities

Vulert verdict on lollms 11.0.0 i

Updated on 23 Oct 2026

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

Package health score 37/100
  • Security Unfixed issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Quiet

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 11.0.0 — affected i
  • Vulnerabilities on record 44 over 2 years · 25 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 17 i
  • Stars 101 i
  • Last release 20 months ago i
  • Licence Apache-2.0 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 lollms, 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
11.0.0 15 Feb 2025 H1 M1 U2 Apache-2.0 No Details →
9.5.1 23 Jun 2024 H4 M4 L1 U8 Apache-2.0 No Details →
9.5.0 10 Jun 2024 C1 H5 M4 L1 U10 Apache-2.0 No Details →
9.3.0 04 Mar 2024 C2 H9 M4 L1 U14 Apache-2.0 No Details →
7.2.0 25 Jan 2024 C2 H9 M4 L1 U14 Apache-2.0 No Details →
6.9.0 14 Dec 2023 C2 H9 M4 L1 U14 Apache-2.0 No Details →
6.7.0 05 Dec 2023 C2 H9 M4 L1 U14 Apache-2.0 No Details →
6.6.0 28 Nov 2023 C2 H9 M4 L1 U14 Apache-2.0 No Details →
6.5.2 27 Nov 2023 C2 H9 M4 L1 U14 Apache-2.0 No Details →
6.5.1 27 Nov 2023 C2 H9 M4 L1 U14 Apache-2.0 No Details →
6.5.0 26 Nov 2023 C2 H9 M4 L1 U14 Apache-2.0 No Details →
6.4.0 12 Nov 2023 C2 H9 M4 L1 U14 Apache-2.0 No Details →
6.2.0 09 Nov 2023 C2 H9 M4 L1 U14 Apache-2.0 No Details →
6.1.1 08 Nov 2023 C2 H9 M4 L1 U14 Apache-2.0 No Details →
6.0.9 06 Nov 2023 C2 H9 M4 L1 U14 Apache-2.0 No Details →
6.0.8 04 Nov 2023 C2 H9 M4 L1 U14 Apache-2.0 No Details →
6.0.7 31 Oct 2023 C2 H9 M4 L1 U14 Apache-2.0 No Details →
6.0.6 31 Oct 2023 C2 H9 M4 L1 U14 Apache-2.0 No Details →
6.0.5 30 Oct 2023 C2 H9 M4 L1 U14 Apache-2.0 No Details →
6.0.3 30 Oct 2023 C2 H9 M4 L1 U14 Apache-2.0 No Details →
6.0.2 30 Oct 2023 C2 H9 M4 L1 U14 Apache-2.0 No Details →
6.0.1 30 Oct 2023 C2 H9 M4 L1 U14 Apache-2.0 No Details →
6.0.0 30 Oct 2023 C2 H9 M4 L1 U14 Apache-2.0 No Details →
5.9.5 30 Oct 2023 C2 H9 M4 L1 U14 Apache-2.0 No Details →
5.9.4 29 Oct 2023 C2 H9 M4 L1 U14 Apache-2.0 No Details →
5.9.3 29 Oct 2023 C2 H9 M4 L1 U14 Apache-2.0 No Details →
5.9.2 29 Oct 2023 C2 H9 M4 L1 U14 Apache-2.0 No Details →
5.9.1 29 Oct 2023 C2 H9 M4 L1 U14 Apache-2.0 No Details →
5.9.0 22 Oct 2023 C2 H9 M4 L1 U14 Apache-2.0 No Details →
5.8.8 19 Oct 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.8.7 19 Oct 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.8.6 19 Oct 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.8.5 19 Oct 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.8.3 19 Oct 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.8.2 18 Oct 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.8.1 18 Oct 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.7.9 15 Oct 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.7.8 15 Oct 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.7.7 15 Oct 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.7.6 14 Oct 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.7.5 11 Oct 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.7.3 10 Oct 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.7.2 08 Oct 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.7.1 07 Oct 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.7.0 07 Oct 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.6.2 02 Oct 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.6.0 02 Oct 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.5.6 01 Oct 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.5.5 01 Oct 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.5.4 01 Oct 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.5.3 23 Sep 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.5.2 20 Sep 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.5.1 17 Sep 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.5.0 14 Sep 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.3.1 13 Sep 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.3.0 07 Sep 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.2.1 05 Sep 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.2.0 05 Sep 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.1.1 03 Sep 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.1.0 02 Sep 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.0.2 31 Aug 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.0.1 29 Aug 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
5.0.0 28 Aug 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
4.5.3 27 Aug 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
4.5.2 27 Aug 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
4.5.1 26 Aug 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
4.5.0 26 Aug 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
4.2.2 26 Aug 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
4.2.1 26 Aug 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
4.2.0 25 Aug 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
4.1.6 25 Aug 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
4.1.5 25 Aug 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
4.1.0 23 Aug 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
4.0.2 23 Aug 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
4.0.1 22 Aug 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
4.0.0 20 Aug 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
3.2.0 20 Aug 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
3.1.5 19 Aug 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
3.1.0 19 Aug 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
3.0.0 17 Aug 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
2.3.4 16 Aug 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
2.3.3 16 Aug 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
2.3.1 04 Aug 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
2.3.0 02 Aug 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
2.2.8 01 Aug 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
2.2.7 31 Jul 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
2.2.6 31 Jul 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
2.2.5 31 Jul 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
2.2.4 31 Jul 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
2.2.3 31 Jul 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
2.2.2 31 Jul 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
2.2.1 31 Jul 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
2.2.0 29 Jul 2023 C1 H9 M4 L1 U15 Apache-2.0 No Details →
2.1.60 27 Jul 2023 C3 H9 M4 L1 U16 Apache-2.0 No Details →
2.1.59 27 Jul 2023 C3 H9 M4 L1 U16 Apache-2.0 No Details →
2.1.56 26 Jul 2023 C3 H9 M4 L1 U16 Apache-2.0 No Details →
2.1.55 26 Jul 2023 C3 H9 M4 L1 U16 Apache-2.0 No Details →
2.1.54 23 Jul 2023 C3 H9 M4 L1 U16 Apache-2.0 No Details →
2.1.53 21 Jul 2023 C3 H9 M4 L1 U16 Apache-2.0 No Details →
2.1.51 21 Jul 2023 C3 H9 M4 L1 U16 Apache-2.0 No Details →
2.1.50 20 Jul 2023 C3 H9 M4 L1 U16 — No Details →
2.1.49 19 Jul 2023 C3 H9 M4 L1 U16 — No Details →
2.1.48 19 Jul 2023 C3 H9 M4 L1 U16 — No Details →
2.1.47 19 Jul 2023 C3 H9 M4 L1 U16 — No Details →
2.1.46 19 Jul 2023 C3 H9 M4 L1 U16 — No Details →
2.1.45 19 Jul 2023 C3 H9 M4 L1 U16 — No Details →
2.1.44 17 Jul 2023 C3 H9 M4 L1 U16 — No Details →
2.1.43 17 Jul 2023 C3 H9 M4 L1 U16 — No Details →
2.1.42 17 Jul 2023 C3 H9 M4 L1 U16 — No Details →
2.1.40 16 Jul 2023 C3 H9 M4 L1 U16 — No Details →
2.1.39 16 Jul 2023 C3 H9 M4 L1 U16 — No Details →
2.1.38 15 Jul 2023 C3 H9 M4 L1 U16 — No Details →
2.1.37 15 Jul 2023 C3 H9 M4 L1 U16 — No Details →
2.1.36 11 Jul 2023 C3 H9 M4 L1 U16 — No Details →
2.1.35 10 Jul 2023 C3 H9 M4 L1 U16 — No Details →
2.1.34 09 Jul 2023 C3 H9 M4 L1 U16 — No Details →
2.1.32 07 Jul 2023 C3 H9 M4 L1 U16 — No Details →
2.1.31 06 Jul 2023 C3 H9 M4 L1 U16 — No Details →
2.1.30 06 Jul 2023 C3 H9 M4 L1 U16 — No Details →
2.1.29 06 Jul 2023 C3 H9 M4 L1 U16 — No Details →

The newest 120 of 266 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 17
  • 2025 2
  • 2026 25

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

03 Vulnerabilities

Recorded vulnerabilities for lollms

The 5 most severe of 44 vulnerabilities recorded for this package

Search all 44 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-4078: LoLLMS Command Injection Vulnerability in lollms Package 9.8 critical 9.5.0 07 Jul 2026
CVE-2024-3429: Path Traversal Vulnerability in lollms Package 9.8 critical 9.5.0 07 Jul 2026
CVE-2024-3429: LoLLMS Path Traversal vulnerability in lollms 9.8 high 9.5.0 06 Jun 2024
CVE-2024-4320: Remote Code Execution via path traversal bypass in lollms 9.8 critical 9.5.1 22 Jun 2024
CVE-2024-4078: LoLLMS Command Injection vulnerability 9.8 high 9.5.0 16 May 2024

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 lollms

Is lollms safe to use?

Vulert records 44 vulnerabilities for lollms in PyPI: 4 critical, 10 high, 5 medium and 1 low, plus 24 not yet rated. 17 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is lollms's Vulert package health score?

Vulert scores lollms 37/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 lollms affected?

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

How many vulnerabilities does lollms have?

44 vulnerabilities are recorded for lollms in the PyPI ecosystem: 4 critical, 10 high, 5 medium and 1 low, plus 24 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 lollms vulnerabilities disclosed?

25 vulnerabilities were recorded for lollms in the last 12 months, and the oldest entry in this database dates to 16 May 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 lollms 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 lollms for upcoming vulnerabilities?

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