VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

python-gnupg: vulnerability history, versions and safety

python-gnupg is a package in the PyPI ecosystem. Vulert records 12 vulnerabilities for it across 14 releases, from Jun 2014 to Mar 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
12 vulnerabilities recorded C1 H4 M1 U6
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 python-gnupg vulnerabilities

Vulert verdict on python-gnupg 0.5.7 i

Updated on 22 Oct 2026

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

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

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

  • Current release 0.5.7 — unaffected i
  • Vulnerabilities on record 12 over 5 years · 0 in the last year i
  • Latest disclosure 13 Mar 2020 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 382 packages i
  • Stars 143 i
  • Last release this month i
  • Licence non-standard 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 python-gnupg, 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.5.7 29 Sep 2026 none non-standard — Details →
0.5.6 31 Dec 2025 none non-standard — Details →
0.5.5 04 Aug 2025 none non-standard — Details →
0.5.4 07 Jan 2025 none non-standard — Details →
0.5.3 20 Sep 2024 none non-standard — Details →
0.5.2 12 Dec 2023 none non-standard — Details →
0.5.2.dev0 12 Dec 2023 none non-standard — Details →
0.5.1 22 Jul 2023 none non-standard — Details →
0.5.0 23 Aug 2022 none non-standard — Details →
0.4.9 20 May 2022 none non-standard — Details →
0.4.8 24 Nov 2021 none non-standard — Details →
0.4.7 11 Mar 2021 none non-standard — Details →
0.4.6 17 Apr 2020 none non-standard — Details →
0.4.5 12 Aug 2019 none — — Details →
0.4.4 24 Jan 2019 none — — Details →
0.4.3 13 Jun 2018 H1 M1 U2 — Yes Details →
0.4.2 28 Mar 2018 H1 M1 U2 — Yes Details →
0.4.1 06 Jul 2017 H1 M1 U2 — Yes Details →
0.4.0 29 Jan 2017 H1 M1 U2 — Yes Details →
0.3.9 10 Sep 2016 H1 M1 U2 — Yes Details →
0.3.8 24 Sep 2015 H1 M1 U2 non-standard Yes Details →
0.3.7 07 Dec 2014 H1 M1 U2 non-standard Yes Details →
0.3.6 05 Feb 2014 C1 H2 M1 U3 non-standard Yes Details →
0.3.5 30 Aug 2013 C1 H4 M1 U5 non-standard Yes Details →
0.3.4 05 Jun 2013 H2 M1 U4 non-standard Yes Details →
0.3.3 04 Jun 2013 H2 M1 U4 non-standard Yes Details →
0.3.6.win32 — C1 H4 M1 U5 — Yes Details →
0.3.7.win32 — C1 H2 M1 U3 — Yes Details →
0.3.8.win32 — H1 M1 U2 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2014 4
  • 2018 4
  • 2019 3
  • 2020 1

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

03 Vulnerabilities

Recorded vulnerabilities for python-gnupg

The 5 most severe of 12 vulnerabilities recorded for this package

Search all 12 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2013-7323: python-gnupg Command Execution Vulnerability 9.8 high 0.3.7 06 Nov 2018
CVE-2014-1929: python-gnupg - Option Injection through Positional Arguments 9.8 critical 0.3.7 06 Nov 2018
CVE-2014-1928: python-gnupg - Arbitrary Code Execution Vulnerability 7.5 high 0.3.6 06 Nov 2018
CVE-2019-6690: Improper Input Validation in python-gnupg 7.5 high 0.4.4 25 Mar 2019
CVE-2014-1927: High severity vulnerability in python-gnupg 7.5 high 0.3.6 06 Nov 2018

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 python-gnupg

Is python-gnupg safe to use?

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

Vulert scores python-gnupg 77/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 python-gnupg affected?

No. 0.5.7, 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 python-gnupg should I use?

0.5.7 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 python-gnupg have?

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

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

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