Vulnerability Database · Go · Package report

github.com/cloudflare/gokey: vulnerability history, versions and safety

github.com/cloudflare/gokey is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 26 releases, first recorded in Dec 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 02 Dec 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on github.com/cloudflare/gokey v0.2.1 i

Updated on 23 Oct 2026

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

Package health score 75/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

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.2.1 — affected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 02 Dec 2025 i
  • Highest CVSS 7.1 i
  • With no published fix 0 i
  • Stars 2,438 i
  • OpenSSF scorecard 3/10 i
  • Last release 6 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/cloudflare/gokey, 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.2.1 31 Mar 2026 H1 U1 BSD-3-Clause Yes Details →
v0.2.1-0.20251120095330-79f478658a0c 20 Nov 2025 H1 U1 BSD-3-Clause Yes Details →
v0.1.4-0.20251118190258-f261819e99ea 18 Nov 2025 H1 U1 BSD-3-Clause Yes Details →
v0.2.0 18 Nov 2025 H1 U1 BSD-3-Clause Yes Details →
v0.1.4-0.20250206220553-c218168412a2 06 Feb 2025 H1 U1 BSD-3-Clause Yes Details →
v0.1.4-0.20240920015212-e09598278b8e 20 Sep 2024 H1 U1 BSD-3-Clause Yes Details →
v0.1.3 29 Apr 2024 H1 U1 BSD-3-Clause Yes Details →
v0.1.3-0.20240429165959-b5342a3cf158 29 Apr 2024 H1 U1 BSD-3-Clause Yes Details →
v0.1.3-0.20231116131901-26fcef24d123 16 Nov 2023 H1 U1 BSD-3-Clause Yes Details →
v0.1.2 02 Sep 2022 H1 U1 BSD-3-Clause Yes Details →
v0.1.2-0.20220902115317-3875268291dc 02 Sep 2022 H1 U1 BSD-3-Clause Yes Details →
v0.1.2-0.20220728212719-5b47b9d46977 28 Jul 2022 H1 U1 BSD-3-Clause Yes Details →
v0.1.1 28 Jul 2022 H1 U1 BSD-3-Clause Yes Details →
v0.1.1-0.20220713212929-657b7cbf970a 13 Jul 2022 H1 U1 BSD-3-Clause Yes Details →
v0.1.1-0.20220713201142-41aa3d530ea6 13 Jul 2022 H1 U1 BSD-3-Clause Yes Details →
v0.1.1-0.20220712205232-a7a2ab980535 12 Jul 2022 H1 U1 BSD-3-Clause Yes Details →
v0.1.1-0.20220304163902-751c284a3a4c 04 Mar 2022 H1 U1 BSD-3-Clause Yes Details →
v0.1.1-0.20210809112735-2d48d3b71b42 09 Aug 2021 H1 U1 BSD-3-Clause Yes Details →
v0.1.1-0.20210506115400-a65836c0776b 06 May 2021 H1 U1 BSD-3-Clause Yes Details →
v0.1.1-0.20200830211046-de4542d057e8 30 Aug 2020 H1 U1 BSD-3-Clause Yes Details →
v0.1.1-0.20190814050400-c96dd73ff7ff 14 Aug 2019 H1 U1 BSD-3-Clause Yes Details →
v0.1.0 08 Jul 2019 H1 U1 BSD-3-Clause Yes Details →
v0.0.0-20190306104503-5e0814070a40 06 Mar 2019 H1 U1 BSD-3-Clause Yes Details →
v0.0.0-20190103152100-40eba7eeee23 03 Jan 2019 H1 U1 BSD-3-Clause Yes Details →
v0.0.0-20181023060409-b4e27806d502 23 Oct 2018 H1 U1 BSD-3-Clause Yes Details →
v0.0.0-20180619232149-6bb729016058 19 Jun 2018 H1 U1 BSD-3-Clause Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 2

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/cloudflare/gokey

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →

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/cloudflare/gokey

Is github.com/cloudflare/gokey safe to use?

Vulert records 2 vulnerabilities for github.com/cloudflare/gokey in Go: 0 critical, 1 high, 0 medium and 0 low, plus 1 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/cloudflare/gokey's Vulert package health score?

Vulert scores github.com/cloudflare/gokey 75/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 github.com/cloudflare/gokey affected?

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

Which version of github.com/cloudflare/gokey should I use?

v0.2.1 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/cloudflare/gokey have?

2 vulnerabilities are recorded for github.com/cloudflare/gokey in the Go 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 github.com/cloudflare/gokey vulnerabilities disclosed?

2 vulnerabilities were recorded for github.com/cloudflare/gokey in the last 12 months, and the oldest entry in this database dates to 02 Dec 2025. 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/cloudflare/gokey 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/cloudflare/gokey for upcoming vulnerabilities?

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