VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

cherrypy: vulnerability history, versions and safety

cherrypy is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 5 releases, from Feb 2006 to May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H2 U2
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 cherrypy vulnerabilities

Vulert verdict on cherrypy 18.10.0 i

Updated on 23 Oct 2026

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

Package health score 68/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Quiet

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

  • Current release 18.10.0 — unaffected i
  • Vulnerabilities on record 4 over 16 years · 0 in the last year i
  • Latest disclosure 01 May 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 430 packages i
  • Stars 1,947 i
  • OpenSSF scorecard 3/10 i
  • Last release 28 months ago i
  • Licence BSD-3-Clause 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 cherrypy, 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
18.10.0 14 Jun 2024 none BSD-3-Clause — Details →
18.9.0 13 Dec 2023 none BSD-3-Clause — Details →
18.8.0 17 Jul 2022 none BSD-3-Clause — Details →
18.7.0 11 Jul 2022 none BSD-3-Clause — Details →
18.6.1 03 Jul 2021 none BSD-3-Clause — Details →
18.6.0 17 Apr 2020 none non-standard — Details →
18.5.0 27 Nov 2019 none non-standard — Details →
18.4.0 03 Nov 2019 none non-standard — Details →
18.3.0 03 Oct 2019 none non-standard — Details →
18.2.0 04 Sep 2019 none non-standard — Details →
17.4.2 23 Jun 2019 none non-standard — Details →
18.1.2 23 Jun 2019 none non-standard — Details →
18.1.1 27 Mar 2019 none non-standard — Details →
18.1.0 09 Dec 2018 none non-standard — Details →
17.4.1 23 Nov 2018 none non-standard — Details →
17.4.0 26 Sep 2018 none non-standard — Details →
18.0.1 09 Sep 2018 none non-standard — Details →
18.0.0 01 Sep 2018 none non-standard — Details →
17.3.0 16 Aug 2018 none non-standard — Details →
17.2.0.post0 15 Aug 2018 none non-standard — Details →
17.2.0 14 Aug 2018 none non-standard — Details →
17.1.0 14 Aug 2018 none non-standard — Details →
17.0.0 13 Jul 2018 none non-standard — Details →
16.0.3 10 Jul 2018 none non-standard — Details →
16.0.2 18 Jun 2018 none non-standard — Details →
16.0.0 16 Jun 2018 none non-standard — Details →
15.0.0 11 May 2018 none non-standard — Details →
14.2.0 22 Apr 2018 none non-standard — Details →
14.1.0 19 Apr 2018 none non-standard — Details →
14.0.1 22 Mar 2018 none non-standard — Details →
14.0.0 04 Feb 2018 none non-standard — Details →
13.1.0 17 Dec 2017 none non-standard — Details →
13.0.1 17 Dec 2017 none non-standard — Details →
13.0.0 05 Dec 2017 none non-standard — Details →
12.0.2 04 Dec 2017 none non-standard — Details →
11.2.0 29 Nov 2017 none non-standard — Details →
12.0.1 21 Nov 2017 none non-standard — Details →
12.0.0 18 Nov 2017 none non-standard — Details →
11.1.0 29 Oct 2017 none non-standard — Details →
11.0.0 08 Jul 2017 none non-standard — Details →
10.2.2 17 May 2017 none non-standard — Details →
10.2.1 13 Mar 2017 none non-standard — Details →
10.2.0 12 Mar 2017 none non-standard — Details →
10.1.1 18 Feb 2017 none non-standard — Details →
10.1.0 08 Feb 2017 none non-standard — Details →
10.0.0 20 Jan 2017 none non-standard — Details →
9.0.0 19 Jan 2017 none non-standard — Details →
8.9.1 17 Jan 2017 none non-standard — Details →
8.9.0 13 Jan 2017 none non-standard — Details →
8.8.0 10 Jan 2017 none non-standard — Details →
8.7.0 31 Dec 2016 none non-standard — Details →
8.6.0 27 Dec 2016 none non-standard — Details →
8.5.0 26 Dec 2016 none non-standard — Details →
8.4.0 26 Dec 2016 none non-standard — Details →
8.4.0a2 26 Dec 2016 none non-standard — Details →
8.3.1 26 Dec 2016 none non-standard — Details →
8.3.0 25 Dec 2016 none non-standard — Details →
8.2.0 24 Dec 2016 none non-standard — Details →
8.1.3 17 Dec 2016 none non-standard — Details →
8.1.2 28 Sep 2016 none non-standard — Details →
8.1.1 28 Sep 2016 none non-standard — Details →
8.1.0 04 Sep 2016 none non-standard — Details →
8.0.1 03 Sep 2016 none non-standard — Details →
8.0.0 02 Sep 2016 none non-standard — Details →
7.1.0 25 Jul 2016 none non-standard — Details →
7.0.0 24 Jul 2016 none non-standard — Details →
6.2.1 24 Jul 2016 none non-standard — Details →
6.2.0 19 Jul 2016 none non-standard — Details →
6.1.1 17 Jul 2016 none non-standard — Details →
6.1.0 14 Jul 2016 none non-standard — Details →
6.0.2 23 Jun 2016 none non-standard — Details →
6.0.1 06 Jun 2016 none non-standard — Details →
6.0.0 06 Jun 2016 none non-standard — Details →
5.6.0 05 Jun 2016 none non-standard — Details →
5.5.0 05 Jun 2016 none non-standard — Details →
5.4.0 11 May 2016 none non-standard — Details →
5.3.0 30 Apr 2016 none non-standard — Details →
5.2.0 30 Apr 2016 none non-standard — Details →
5.1.0 10 Mar 2016 none non-standard — Details →
5.0.1 06 Feb 2016 none non-standard — Details →
5.0.0 04 Feb 2016 none non-standard — Details →
4.0.0 20 Dec 2015 none non-standard — Details →
3.8.2 17 Dec 2015 none non-standard — Details →
3.8.1 03 Dec 2015 none non-standard — Details →
3.8.0 26 Jun 2015 none non-standard — Details →
3.7.0 24 Apr 2015 none non-standard — Details →
0.10.0 24 Mar 2015 H2 U2 — Yes Details →
2.2.0 24 Mar 2015 none non-standard — Details →
2.2.1 24 Mar 2015 none non-standard — Details →
2.3.0 24 Mar 2015 none non-standard — Details →
3.0.0 24 Mar 2015 U1 non-standard Yes Details →
3.0.4 24 Mar 2015 none non-standard — Details →
3.1.0 24 Mar 2015 none non-standard — Details →
3.1.2 24 Mar 2015 none non-standard — Details →
3.2.0 24 Mar 2015 none non-standard — Details →
3.2.2 24 Mar 2015 none non-standard — Details →
3.6.0 14 Sep 2014 none non-standard — Details →
3.5.0 27 Jun 2014 none non-standard — Details →
3.4.0 27 Jun 2014 none non-standard — Details →
3.3.0 16 Apr 2014 none non-standard — Details →
3.2.6 12 Apr 2014 none — — Details →
3.2.5 23 Feb 2014 none — — Details →
3.2.4 28 Mar 2013 none — — Details →
3.2.3 18 Mar 2013 none — — Details →
2.2.0b0 27 Jan 2006 none — — Details →
2.1.1 11 Jan 2006 none — — Details →
2.0.0 — H2 U2 — Yes Details →
2.1.0-py2.3 — H2 U2 — Yes Details →
2.1.0-py2.4 — H2 U2 — Yes Details →
3.1.2.win32 — none — — Details →
3.2.0-py2.5 — none — — Details →
3.2.0-py2.6 — none — — Details →
3.2.0-py2.win32 — none — — Details →
3.2.0-py3.1 — none — — Details →
3.2.0-py3.win32 — none — — Details →
3.2.2.win32 — none — — Details →
3.2.5.win-amd64 — none — — Details →
3.2.6.win-amd64 — none — — Details →
3.4.0.win-amd64 — none — — Details →
3.5.0.win-amd64 — none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2006 1
  • 2008 1
  • 2022 2

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

03 Vulnerabilities

Recorded vulnerabilities for cherrypy

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2008-0252: CherryPy Malicious cookies allow access to files outside the session directory 7.5 high 2.1.1 01 May 2022
CVE-2006-0847: CherryPy Directory Traversal Vulnerability 7.5 high 2.1.1 01 May 2022
CVE-2006-0847: Directory Traversal Vulnerability in CherryPy N/A unrated 2.1.1 22 Feb 2006
CVE-2008-0252: Directory Traversal Vulnerability in CherryPy N/A unrated 2.1.1 12 Jan 2008

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 cherrypy

Is cherrypy safe to use?

Vulert records 4 vulnerabilities for cherrypy in PyPI: 0 critical, 2 high, 0 medium and 0 low, plus 2 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 cherrypy's Vulert package health score?

Vulert scores cherrypy 68/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).

Is the latest version of cherrypy affected?

No. 18.10.0, 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 cherrypy should I use?

18.10.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 cherrypy have?

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

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

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