VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

gerapy: vulnerability history, versions and safety

gerapy is a package in the PyPI ecosystem. Vulert records 8 vulnerabilities for it across 65 releases, from Jul 2020 to Mar 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded C3 H1 U4
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 gerapy vulnerabilities

Vulert verdict on gerapy 0.9.13 i

Updated on 23 Oct 2026

Action needed: 0.9.13 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 66/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Moderate

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 0.9.13 — affected i
  • Vulnerabilities on record 8 over 1 year · 0 in the last year i
  • Latest disclosure 11 Mar 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Stars 3,515 i
  • OpenSSF scorecard 5/10 i
  • Last release 39 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 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 gerapy, 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
0.9.13 19 Jul 2023 U1 MIT Yes Details →
0.9.12 27 Dec 2022 U1 MIT Yes Details →
0.9.11 24 Jul 2022 U1 MIT Yes Details →
0.9.10 30 Dec 2021 U1 MIT Yes Details →
0.9.10rc1 30 Dec 2021 U1 MIT Yes Details →
0.9.9 26 Dec 2021 U1 MIT Yes Details →
0.9.8 26 Dec 2021 H1 U1 MIT Yes Details →
0.9.7 31 Jul 2021 C2 H1 U3 MIT Yes Details →
0.9.6 27 Aug 2020 C2 H1 U3 MIT Yes Details →
0.9.6a1 26 Aug 2020 C2 H1 U3 MIT Yes Details →
0.9.5 08 Aug 2020 C2 H1 U3 MIT Yes Details →
0.9.3 06 Jul 2020 C2 H1 U3 MIT Yes Details →
0.9.3b1 06 Jul 2020 C3 H1 U4 MIT Yes Details →
0.9.3a2 02 Dec 2019 C3 H1 U4 MIT Yes Details →
0.9.3a1 02 Dec 2019 C3 H1 U4 MIT Yes Details →
0.9.2 25 Nov 2019 C3 H1 U4 MIT Yes Details →
0.9.2rc1 25 Nov 2019 C3 H1 U4 MIT Yes Details →
0.9.2a0 25 Nov 2019 C3 H1 U4 MIT Yes Details →
0.9.1 21 Nov 2019 C3 H1 U4 MIT Yes Details →
0.9.0 21 Nov 2019 C3 H1 U4 MIT Yes Details →
0.8.8 21 Nov 2019 C3 H1 U4 MIT Yes Details →
0.8.7 20 Nov 2019 C3 H1 U4 MIT Yes Details →
0.8.6 20 Nov 2019 C3 H1 U4 MIT Yes Details →
0.8.6rc2 20 Nov 2019 C3 H1 U4 MIT Yes Details →
0.8.5rc2 20 Nov 2019 C3 H1 U4 MIT Yes Details →
0.8.6rc1 27 Oct 2019 C3 H1 U4 MIT Yes Details →
0.8.6b1 04 Jul 2018 C3 H1 U4 MIT Yes Details →
0.8.6b0 04 Jul 2018 C3 H1 U4 MIT Yes Details →
0.8.6a0 05 Jun 2018 C3 H1 U4 MIT Yes Details →
0.8.5 24 Jan 2018 C3 H1 U4 MIT Yes Details →
0.8.4rc2 23 Jan 2018 C3 H1 U4 MIT Yes Details →
0.8.3 23 Jan 2018 C3 H1 U4 MIT Yes Details →
0.8.2 20 Jan 2018 C3 H1 U4 MIT Yes Details →
0.8.1 19 Jan 2018 C3 H1 U4 MIT Yes Details →
0.8.0 19 Jan 2018 C3 H1 U4 MIT Yes Details →
0.7.9 19 Jan 2018 C3 H1 U4 MIT Yes Details →
0.7.8 19 Jan 2018 C3 H1 U4 MIT Yes Details →
0.7.7 29 Oct 2017 C3 H1 U4 MIT Yes Details →
0.7.6 20 Oct 2017 C3 H1 U4 MIT Yes Details →
0.7.3 16 Oct 2017 C3 H1 U4 MIT Yes Details →
0.7.2 12 Oct 2017 C3 H1 U4 MIT Yes Details →
0.7.1 10 Oct 2017 C3 H1 U4 MIT Yes Details →
0.7.0 08 Oct 2017 C3 H1 U4 MIT Yes Details →
0.6.9 05 Jul 2017 C3 H1 U4 MIT Yes Details →
0.6.8 04 Jul 2017 C3 H1 U4 MIT Yes Details →
0.6.7 04 Jul 2017 C3 H1 U4 MIT Yes Details →
0.6.6 04 Jul 2017 C3 H1 U4 MIT Yes Details →
0.7.0-py3.6 — C3 H1 U3 — Yes Details →
0.7.1-py3.6 — C3 H1 U3 — Yes Details →
0.7.2-py3.6 — C3 H1 U3 — Yes Details →
0.7.3-py3.6 — C3 H1 U3 — Yes Details →
0.7.6-py3.6 — C3 H1 U3 — Yes Details →
0.7.7-py3.6 — C3 H1 U3 — Yes Details →
0.7.8-py3.6 — C3 H1 U3 — Yes Details →
0.7.9-py3.6 — C3 H1 U3 — Yes Details →
0.8.0-py3.6 — C3 H1 U3 — Yes Details →
0.8.1-py3.6 — C3 H1 U3 — Yes Details →
0.8.2-py3.6 — C3 H1 U3 — Yes Details →
0.8.3-py3.6 — C3 H1 U3 — Yes Details →
0.8.4rc2-py3.6 — C3 H1 U3 — Yes Details →
0.8.5-py3.6 — C3 H1 U3 — Yes Details →
0.8.6a0-py3.6 — C3 H1 U3 — Yes Details →
0.8.6b0-py3.6 — C3 H1 U3 — Yes Details →
0.8.6b1-py3.6 — C3 H1 U3 — Yes Details →
0.8.6rc1-py3.7 — C3 H1 U3 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2021 2
  • 2022 5

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

03 Vulnerabilities

Recorded vulnerabilities for gerapy

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-44597: Incorrect Authorization in Gerapy 9.8 critical 0.9.8 11 Mar 2022
CVE-2021-43857: Gerapy < 0.9.8 Remote Code Execution 9.8 critical 0.9.8 06 Jan 2022
CVE-2020-7698: Command Injection in Gerapy 9.8 critical 0.9.3 06 May 2021
CVE-2021-32849: Arbitrary Command Execution in Gerapy 8.8 high 0.9.9 06 Jan 2022
CVE-2020-7698: Gerapy Package Command Injection N/A unrated e8446605eb2424717418eae199ec7aad573da2d2 29 Jul 2020

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 gerapy

Is gerapy safe to use?

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

Vulert scores gerapy 66/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 gerapy affected?

Yes. 0.9.13, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of gerapy should I use?

0.9.13 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 gerapy have?

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

0 vulnerabilities were recorded for gerapy in the last 12 months, and the oldest entry in this database dates to 29 Jul 2020. 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 gerapy 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 gerapy for upcoming vulnerabilities?

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