Is cheetah safe to use?

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

What is cheetah's Vulert package health score?

Vulert scores cheetah 58/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 cheetah affected?

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

Which version of cheetah should I use?

2.4.4 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 cheetah have?

2 vulnerabilities are recorded for cheetah 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 cheetah vulnerabilities disclosed?

1 vulnerability was recorded for cheetah in the last 12 months, and the oldest entry in this database dates to 01 May 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 cheetah 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 cheetah for upcoming vulnerabilities?

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

Vulnerability Database · PyPI · Package report

cheetah: vulnerability history, versions and safety

cheetah is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 14 releases, from May 2022 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.

2 vulnerabilities recorded H1 U1

2 with no fix published

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

See the unfixed vulnerabilities →

1 in the last 12 months

Most recent disclosure 02 Jul 2026.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all cheetah vulnerabilities

Vulert verdict on cheetah 2.4.4 i

Updated on 23 Oct 2026

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

Package health score 58/100

Security Minor issues
Maintenance Slowing
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 2.4.4 — affected i
Vulnerabilities on record 2 over 4 years · 1 in the last year i
Latest disclosure 02 Jul 2026 i
Highest CVSS n/a i
With no published fix 2 i
Depended on by 1 packages i
Last release 190 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for cheetah, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
2.4.4	13 Dec 2010	H1 U1	MIT	No	Details →
2.4.3	16 Sep 2010	H1 U1	MIT	No	Details →
2.4.2.1	01 Mar 2010	H1 U1	MIT	No	Details →
2.4.2	08 Feb 2010	H1 U1	MIT	No	Details →
2.4.1	20 Dec 2009	H1 U1	MIT	No	Details →
2.3.0	25 Oct 2009	H1 U1	MIT	No	Details →
2.4.0	25 Oct 2009	H1 U1	MIT	No	Details →
2.2.2	15 Sep 2009	H1 U1	MIT	No	Details →
2.2.1	02 Jul 2009	H1 U1	MIT	No	Details →
2.0.0rc7	08 Aug 2006	H1 U1	MIT	No	Details →
1.0.0	26 Jan 2006	H1 U1	—	No	Details →
2.2.2-1.src	—	H1 U1	—	No	Details →
2.2.2-1.x86_64	—	H1 U1	—	No	Details →
2.4.0-1.i586	—	H1 U1	—	No	Details →

All 14 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 1
2026 1

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

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for cheetah

Vulnerability	Severity	Fixed version ↓	Disclosed ↓
CVE-2005-1632: Cheetah Path Search Order Hijacking	N/A high	No fix published	01 May 2022
CVE-2005-1632: Cheetah Package Path Search Order Hijacking Vulnerability	N/A unrated	No fix published	02 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