VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/proglottis/gpgme: vulnerability history, versions and safety

github.com/proglottis/gpgme is a package in the Go ecosystem. Vulert records 5 vulnerabilities for it across 79 releases, from Apr 2021 to May 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded 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 github.com/proglottis/gpgme vulnerabilities

Vulert verdict on github.com/proglottis/gpgme v0.1.6 i

Updated on 23 Oct 2026

Action needed: v0.1.6 has 5 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 59/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

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 v0.1.6 — affected i
  • Vulnerabilities on record 5 over 1 year · 0 in the last year i
  • Latest disclosure 18 May 2021 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 16 i
  • OpenSSF scorecard 2/10 i
  • Last release 10 months ago i
  • Licence BSD-3-Clause i

Version list, release dates, licence and dependants published by the Go module proxy, 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 github.com/proglottis/gpgme, 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
v0.1.6 24 Nov 2025 H1 U4 BSD-3-Clause Yes Details →
v0.1.5 26 Jul 2025 H1 U4 BSD-3-Clause Yes Details →
v0.1.5-0.20250726071729-c7d6cfab3f11 26 Jul 2025 H1 U4 BSD-3-Clause Yes Details →
v0.1.4 23 Nov 2024 H1 U4 BSD-3-Clause Yes Details →
v0.1.4-0.20241123035352-de26861d2f7c 23 Nov 2024 H1 U4 BSD-3-Clause Yes Details →
v0.1.4-0.20240126025003-bf62a2143fe4 26 Jan 2024 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20220731162614-983fbcc2293b 31 Jul 2022 H1 U4 BSD-3-Clause Yes Details →
v0.1.4-0.20220731162614-983fbcc2293b 31 Jul 2022 H1 U4 BSD-3-Clause Yes Details →
v0.1.4-0.20220731161850-5e70e9786c54 31 Jul 2022 H1 U4 BSD-3-Clause Yes Details →
v0.1.4-0.20220731161850-9a9e1c4fa885 31 Jul 2022 H1 U4 BSD-3-Clause Yes Details →
v0.1.4-0.20220730121659-4d432bd35e68 30 Jul 2022 H1 U4 BSD-3-Clause Yes Details →
v0.1.4-0.20220730121547-b1948a305563 30 Jul 2022 H1 U4 BSD-3-Clause Yes Details →
v0.1.3 04 Jul 2022 H1 U4 BSD-3-Clause Yes Details →
v0.1.3-0.20220629211016-d32082c0e4a9 29 Jun 2022 H1 U4 BSD-3-Clause Yes Details →
v0.1.3-0.20220519023444-ce585e7dc431 19 May 2022 H1 U4 BSD-3-Clause Yes Details →
v0.1.3-0.20220519022648-3a30fb73ccd4 19 May 2022 H1 U4 BSD-3-Clause Yes Details →
v0.1.3-0.20220519022443-e39bcebdc077 19 May 2022 H1 U4 BSD-3-Clause Yes Details →
v0.1.3-0.20220519021756-877bc9db6dba 19 May 2022 H1 U4 BSD-3-Clause Yes Details →
v0.1.3-0.20220519020105-3058791e664c 19 May 2022 H1 U4 BSD-3-Clause Yes Details →
v0.1.3-0.20220519015741-a839534a68fd 19 May 2022 H1 U4 BSD-3-Clause Yes Details →
v0.1.2 19 May 2022 H1 U4 BSD-3-Clause Yes Details →
v0.1.2-0.20220428113623-74cc14c6c9b5 28 Apr 2022 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20200115214002-92153bcb59bd 15 Jan 2020 H1 U4 BSD-3-Clause Yes Details →
v0.1.1 15 Jan 2020 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20200110165031-d575e5df6a83 10 Jan 2020 H1 U4 BSD-3-Clause Yes Details →
v0.1.1-0.20200110165031-d575e5df6a83 10 Jan 2020 H1 U4 BSD-3-Clause Yes Details →
v0.1.1-0.20200110162647-7e8c79da5ec1 10 Jan 2020 H1 U4 BSD-3-Clause Yes Details →
v0.1.1-0.20200110162544-d43d199046c3 10 Jan 2020 H1 U4 BSD-3-Clause Yes Details →
v0.1.1-0.20191030043844-e5586b79c357 30 Oct 2019 H1 U4 BSD-3-Clause Yes Details →
v0.1.1-0.20191030003750-79fb273efc1b 30 Oct 2019 H1 U4 BSD-3-Clause Yes Details →
v0.1.0 29 Oct 2019 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20190226023825-8e0937a489db 26 Feb 2019 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20181127053519-3b0be0916cd5 27 Nov 2018 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20181127052109-afd55a7f2b2e 27 Nov 2018 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20181127031245-1aa8d0b693f5 27 Nov 2018 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20181127030354-a9993e266cea 27 Nov 2018 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20181113191242-d9595c94014e 13 Nov 2018 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20181113090829-bcfba8d192c4 13 Nov 2018 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20170503204531-3d8507427030 03 May 2017 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20170503105548-f9fce5c94f9d 03 May 2017 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20170503075853-82aa15ef87dd 03 May 2017 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20170426024346-49ea2555b6fc 26 Apr 2017 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20170423214904-90e4d2f268eb 23 Apr 2017 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20161212221802-67123d9ef9a4 12 Dec 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20161208171823-1326a98de4e9 08 Dec 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20161004010528-f71e4b8c428a 04 Oct 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20161003230756-8adc29782c63 03 Oct 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20161003230740-f52579b5679a 03 Oct 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20160925225035-e29cbe13dba1 25 Sep 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20160902003402-531a4c667ce6 02 Sep 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20160902001926-d09cdae26811 02 Sep 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20160901235521-473a05818f38 01 Sep 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20160824001542-fc3db61d7d47 24 Aug 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20160823230443-ed84ed78c99f 23 Aug 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20160823230433-b7748d0013a4 23 Aug 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20160531140711-3cc29321f877 31 May 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20160523210806-b38f7d8f2380 23 May 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20160507002408-d0d23da84cb8 07 May 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20160504075627-bf3d55cf2328 04 May 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20160426225621-2496f8bc34cf 26 Apr 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20160426155049-c2302e1b78ca 26 Apr 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20160322210503-226aab813a0b 22 Mar 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20160322193831-28dd1b754b81 22 Mar 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20160322193831-58c4a7983681 22 Mar 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20160322193831-65421b7a8638 22 Mar 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20160317171135-40486ba3fe26 17 Mar 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20160312092729-59a08c19ded5 12 Mar 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20160312074419-04abfadd3d53 12 Mar 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20160312074419-0d46d30925f7 12 Mar 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20160312074419-5afe380f14da 12 Mar 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20160312074419-5d8975fdc3a3 12 Mar 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20160312073416-19262e337e51 12 Mar 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20160312073416-59d33ceaf74f 12 Mar 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20160312073416-c5632509cea0 12 Mar 2016 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20151220110905-ba8241ed506f 20 Dec 2015 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20151220004318-9e9c74f24317 20 Dec 2015 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20151121215046-07b8d19f2d58 21 Nov 2015 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20151120004305-71d93ef1cf35 20 Nov 2015 H1 U4 BSD-3-Clause Yes Details →
v0.0.0-20151120003030-31e26994bb6d 20 Nov 2015 H1 U4 BSD-3-Clause Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 5

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/proglottis/gpgme

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-8945: Use After Free in GPGME Go Wrapper 7.5 high 0.1.1 18 May 2021
CVE-2020-8945: Use After Free in GPGME Go Wrapper N/A unrated 0.1.1 14 Apr 2021
CVE-2020-8945: Vulnerability in github.com/proglottis/gpgme N/A unrated 0.1.1 14 Apr 2021
CVE-2020-8945: Memory Corruption Vulnerability in github.com/proglottis/gpgme N/A unrated 0.1.1 14 Apr 2021
CVE-2020-8945: Memory corruption or code execution in github.com/proglottis/gpgme N/A unrated 0.1.1 14 Apr 2021

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 github.com/proglottis/gpgme

Is github.com/proglottis/gpgme safe to use?

Vulert records 5 vulnerabilities for github.com/proglottis/gpgme in Go: 0 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 github.com/proglottis/gpgme's Vulert package health score?

Vulert scores github.com/proglottis/gpgme 59/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 github.com/proglottis/gpgme affected?

Yes. v0.1.6, the version you would install today, has 5 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/proglottis/gpgme should I use?

v0.1.6 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 github.com/proglottis/gpgme have?

5 vulnerabilities are recorded for github.com/proglottis/gpgme in the Go ecosystem: 0 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 github.com/proglottis/gpgme vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/proglottis/gpgme in the last 12 months, and the oldest entry in this database dates to 14 Apr 2021. 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 github.com/proglottis/gpgme 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 github.com/proglottis/gpgme for upcoming vulnerabilities?

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