VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

leo: vulnerability history, versions and safety

leo is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 11 releases, first recorded in Sep 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all leo vulnerabilities

Vulert verdict on leo 6.8.10 i

Updated on 23 Oct 2026

Good news: 6.8.10, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 73/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

What to do: Stay on 6.8.10 or newer. This can change: a vulnerability disclosed tomorrow can affect 6.8.10 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 6.8.10 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 23 Sep 2021 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 1,611 i
  • OpenSSF scorecard 4/10 i
  • Last release 2 months ago i
  • Licence MIT 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 leo, 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
6.8.10 17 Aug 2026 none MIT — Details →
6.8.10.dev4 13 Aug 2026 none MIT — Details →
6.8.9 03 Jun 2026 none MIT — Details →
6.8.8 14 Apr 2026 none MIT — Details →
6.8.7 11 Oct 2025 none MIT — Details →
6.8.6.1 04 Aug 2025 none MIT — Details →
6.8.6 31 Jul 2025 none MIT — Details →
6.8.5 02 Jul 2025 none MIT — Details →
6.8.4 16 May 2025 none MIT — Details →
6.8.4b1 11 May 2025 none MIT — Details →
6.8.3 05 Dec 2024 none MIT — Details →
6.8.2 08 Nov 2024 none MIT — Details →
6.8.1 27 Jul 2024 none MIT — Details →
6.8.0 03 Jul 2024 none MIT — Details →
6.7.8.post3 21 Mar 2024 none MIT — Details →
6.7.8.post1 19 Mar 2024 none MIT — Details →
6.7.8 17 Mar 2024 none MIT — Details →
6.7.7 20 Jan 2024 none MIT — Details →
6.7.6 19 Dec 2023 none MIT — Details →
6.7.5 07 Nov 2023 none MIT — Details →
6.7.4 17 Aug 2023 none MIT — Details →
6.7.3 12 May 2023 none MIT — Details →
6.7.2 01 Mar 2023 none MIT — Details →
6.7.1 10 Nov 2022 none MIT — Details →
6.7.0 26 Sep 2022 none MIT — Details →
6.6.4 01 Sep 2022 none MIT — Details →
6.6.3 22 Jul 2022 none MIT — Details →
6.6.2 25 May 2022 none MIT — Details →
6.6.1 28 Apr 2022 none MIT — Details →
6.6.0 31 Mar 2022 none MIT — Details →
6.6.0b2 25 Feb 2022 none MIT — Details →
6.6.0b1 11 Nov 2021 none MIT — Details →
6.5.0 22 Oct 2021 none MIT — Details →
6.4.0 25 Sep 2021 none MIT — Details →
6.3.0 06 Nov 2020 none MIT — Details →
6.2.1 30 Mar 2020 H1 U1 MIT Yes Details →
6.2.0 27 Mar 2020 H1 U1 MIT Yes Details →
6.1.0 08 Nov 2019 H1 U1 MIT Yes Details →
6.0.0 02 Aug 2019 H1 U1 MIT Yes Details →
5.9.0 01 May 2019 H1 U1 MIT Yes Details →
5.8.0 20 Jan 2019 H1 U1 MIT Yes Details →
5.7.3 14 Jun 2018 H1 U1 MIT Yes Details →
5.7.2 10 May 2018 H1 U1 MIT Yes Details →
5.7.0 01 Mar 2018 H1 U1 MIT Yes Details →
5.0-final 26 Nov 2014 H1 U1 MIT Yes Details →
4.11-final 17 Nov 2013 H1 U1 MIT Yes Details →
6.4.0.post3 — none MIT — Details →
6.5.0.post2 — none MIT — Details →
6.6.2.post2 — none MIT — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2

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

03 Vulnerabilities

Recorded vulnerabilities for leo

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-23478: Regular Expression Denial of Service in Leo Editor 7.5 high 6.3 23 Sep 2021
CVE-2020-23478: Regular Expression Denial of Service (ReDoS) in Leo Editor v6.2.1 N/A unrated 6.3 22 Sep 2021

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 leo

Is leo safe to use?

Vulert records 2 vulnerabilities for leo in PyPI: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is leo's Vulert package health score?

Vulert scores leo 73/100, which reads as in good shape. 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).

Is the latest version of leo affected?

No. 6.8.10, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of leo should I use?

6.8.10 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 leo have?

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

0 vulnerabilities were recorded for leo in the last 12 months, and the oldest entry in this database dates to 22 Sep 2021. 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 leo 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 leo for upcoming vulnerabilities?

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