VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

cleo: vulnerability history, versions and safety

cleo is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 30 releases, first recorded in Nov 2022. 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 M1 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 cleo vulnerabilities

Vulert verdict on cleo 2.2.1 i

Updated on 23 Oct 2026

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

Package health score 45/100
  • Security No known security issues
  • Maintenance Deprecated
  • Popularity Widely used
  • Community Moderate

The registry marks the latest release as deprecated, which caps this score.

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

  • Current release 2.2.1 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 10 Nov 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 713 packages i
  • Stars 1,358 i
  • Last release 23 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 cleo, 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
2.2.1 18 Nov 2024 none MIT — Details →
2.2.0 18 Nov 2024 none MIT — Details →
2.1.0 30 Oct 2023 none MIT — Details →
2.0.1 22 Nov 2022 none MIT — Details →
2.0.0 22 Nov 2022 none MIT — Details →
1.0.0 22 Nov 2022 M1 U1 MIT Yes Details →
1.0.0a5 03 Jun 2022 M1 U1 MIT Yes Details →
1.0.0a4 30 Jul 2021 M1 U1 MIT Yes Details →
1.0.0a3 21 Feb 2021 M1 U1 MIT Yes Details →
1.0.0a2 13 Feb 2021 M1 U1 MIT Yes Details →
1.0.0a1 29 Jan 2021 M1 U1 MIT Yes Details →
0.8.1 17 Apr 2020 M1 U1 MIT Yes Details →
0.8.0 26 Mar 2020 M1 U1 MIT Yes Details →
0.7.6 25 Oct 2019 M1 U1 MIT Yes Details →
0.7.5 28 Jun 2019 M1 U1 MIT Yes Details →
0.7.4 15 May 2019 M1 U1 MIT Yes Details →
0.7.3 11 May 2019 M1 U1 MIT Yes Details →
0.7.2 08 Dec 2018 M1 U1 MIT Yes Details →
0.7.1 07 Dec 2018 M1 U1 MIT Yes Details →
0.7.0 07 Dec 2018 M1 U1 MIT Yes Details →
0.6.8 25 Jun 2018 M1 U1 MIT Yes Details →
0.6.7 25 Jun 2018 M1 U1 MIT Yes Details →
0.6.6 21 May 2018 M1 U1 MIT Yes Details →
0.6.5 04 Apr 2018 M1 U1 MIT Yes Details →
0.6.4 15 Mar 2018 M1 U1 MIT Yes Details →
0.6.4b1 15 Mar 2018 M1 U1 MIT Yes Details →
0.6.3 15 Mar 2018 M1 U1 MIT Yes Details →
0.6.2 15 Mar 2018 M1 U1 MIT Yes Details →
0.6.1 07 Aug 2017 M1 U1 MIT Yes Details →
0.6.0 21 Apr 2017 M1 U1 MIT Yes Details →
0.5.0 21 Sep 2016 M1 U1 MIT Yes Details →
0.4.1 09 Feb 2016 M1 U1 MIT Yes Details →
0.4.0 11 Jan 2016 M1 U1 MIT Yes Details →
0.3.0 24 May 2015 M1 U1 MIT Yes Details →
0.2.0 24 Mar 2014 M1 U1 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 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 cleo

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-42966: cleo Package Exponential ReDoS Vulnerability 7.5 high 2.0.0 09 Nov 2022
CVE-2022-42966: Regular Expression Denial of Service (ReDoS) in cleo 5.9 medium 2.0.0 10 Nov 2022

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 cleo

Is cleo safe to use?

Vulert records 2 vulnerabilities for cleo in PyPI: 0 critical, 0 high, 1 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 cleo's Vulert package health score?

Vulert scores cleo 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 registry marks the latest release as deprecated, which caps this score.

Is the latest version of cleo affected?

No. 2.2.1, 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 cleo should I use?

2.1.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 cleo have?

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

0 vulnerabilities were recorded for cleo in the last 12 months, and the oldest entry in this database dates to 09 Nov 2022. 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 cleo 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 cleo for upcoming vulnerabilities?

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