Vulnerability Database · Go · Package report

github.com/cli/go-gh/v2: vulnerability history, versions and safety

github.com/cli/go-gh/v2 is a package in the Go ecosystem. Vulert records 3 vulnerabilities for it across 83 releases, from Nov 2024 to Jun 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded M2 U1
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.

Vulert verdict on github.com/cli/go-gh/v2 v2.17.0 i

Updated on 23 Oct 2026

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

Package health score 76/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • 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 v2.17.0 — affected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 03 Jun 2025 i
  • Highest CVSS 6.5 i
  • With no published fix 0 i
  • Stars 442 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence MIT 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/cli/go-gh/v2, 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
v2.17.1-0.20261021074434-ca859e006c93 21 Oct 2026 M2 U1 MIT Yes Details →
v2.17.0 20 Oct 2026 M2 U1 MIT Yes Details →
v2.16.3-0.20261016173312-7de215ca6ceb 16 Oct 2026 M2 U1 MIT Yes Details →
v2.16.3-0.20261012082145-7a33a08c5595 12 Oct 2026 M2 U1 MIT Yes Details →
v2.16.2 09 Oct 2026 M2 U1 MIT Yes Details →
v2.16.2-0.20261009094949-aadf36735579 09 Oct 2026 M2 U1 MIT Yes Details →
v2.16.2-0.20261002090206-68c032df142b 02 Oct 2026 M2 U1 MIT Yes Details →
v2.16.1-0.20260914233729-2ce792192e43 14 Sep 2026 M2 U1 MIT Yes Details →
v2.16.2-0.20260914233729-2ce792192e43 14 Sep 2026 M2 U1 MIT Yes Details →
v2.0.0-20260914155125-37aa5bbaf1a5 14 Sep 2026 M2 U1 MIT Yes Details →
v2.16.1 14 Sep 2026 M2 U1 MIT Yes Details →
v2.16.1-0.20260911214259-ef47bd5cae0e 11 Sep 2026 M2 U1 MIT Yes Details →
v2.16.1-0.20260911205210-08fb58763a65 11 Sep 2026 M2 U1 MIT Yes Details →
v2.16.1-0.20260911155017-01be1165a773 11 Sep 2026 M2 U1 MIT Yes Details →
v2.16.1-0.20260911133028-8478827a613d 11 Sep 2026 M2 U1 MIT Yes Details →
v2.16.1-0.20260911132635-9718bead72bb 11 Sep 2026 M2 U1 MIT Yes Details →
v2.16.1-0.20260909115003-3068cea6f3a9 09 Sep 2026 M2 U1 MIT Yes Details →
v2.16.1-0.20260907133657-ab7f98d5d569 07 Sep 2026 M2 U1 MIT Yes Details →
v2.16.0 03 Sep 2026 M2 U1 MIT Yes Details →
v2.15.0 02 Sep 2026 M2 U1 MIT Yes Details →
v2.14.0 02 Sep 2026 M2 U1 MIT Yes Details →
v2.13.1-0.20260828131725-441165930903 28 Aug 2026 M2 U1 MIT Yes Details →
v2.13.1-0.20260827124009-fe4cf1ccc1ff 27 Aug 2026 M2 U1 MIT Yes Details →
v2.13.1-0.20260807082810-f5ea1c2fae5f 07 Aug 2026 M2 U1 MIT Yes Details →
v2.13.1-0.20260731153212-dfdeaa076f09 31 Jul 2026 M2 U1 MIT Yes Details →
v2.13.1-0.20260722172001-55b71ca3a3e9 22 Jul 2026 M2 U1 MIT Yes Details →
v2.13.1-0.20260619211542-a89b68a441b2 19 Jun 2026 M2 U1 MIT Yes Details →
v2.13.1-0.20260608084553-9d8bff3aac78 08 Jun 2026 M2 U1 MIT Yes Details →
v2.13.1-0.20260522163928-edf1150052b1 22 May 2026 M2 U1 MIT Yes Details →
v2.13.1-0.20260213184604-55692c6b904c 13 Feb 2026 M2 U1 MIT Yes Details →
v2.13.0 03 Nov 2025 M2 U1 MIT Yes Details →
v2.12.3-0.20251031164033-41e1e0defcbe 31 Oct 2025 M2 U1 MIT Yes Details →
v2.12.2 08 Aug 2025 M2 U1 MIT Yes Details →
v2.12.1 29 May 2025 M2 U1 MIT Yes Details →
v2.12.1-0.20250529191032-1ecf6c49ecb0 29 May 2025 M2 U1 MIT Yes Details →
v2.12.1-0.20250529175520-56c6f10bd535 29 May 2025 M2 U1 MIT Yes Details →
v2.12.1-0.20250527202840-258949bd372e 27 May 2025 M2 U1 MIT Yes Details →
v2.12.1-0.20250522153424-0f8a22fe3a4b 22 May 2025 M2 U1 MIT Yes Details →
v2.12.1-0.20250520215444-df956a6624bc 20 May 2025 M2 U1 MIT Yes Details →
v2.12.1-0.20250331143807-6f2b21ff527c 31 Mar 2025 M2 U1 MIT Yes Details →
v2.12.0 25 Mar 2025 M2 U1 MIT Yes Details →
v2.11.3-0.20250307183052-7a6e5543a7f1 07 Mar 2025 M2 U1 MIT Yes Details →
v2.11.3-0.20250227191633-851d3c335462 27 Feb 2025 M2 U1 MIT Yes Details →
v2.11.3-0.20250214194101-607ac5b3631e 14 Feb 2025 M2 U1 MIT Yes Details →
v2.11.3-0.20250212232638-d2d3fcfc44d1 12 Feb 2025 M2 U1 MIT Yes Details →
v2.11.3-0.20250212001006-897a7fe80379 12 Feb 2025 M2 U1 MIT Yes Details →
v2.11.3-0.20250207180258-a5c6b5e31dad 07 Feb 2025 M2 U1 MIT Yes Details →
v2.11.2 06 Jan 2025 M2 U1 MIT Yes Details →
v2.11.1 27 Nov 2024 M2 U1 MIT Yes Details →
v2.11.1-0.20241127204506-65bd8d766abd 27 Nov 2024 M2 U1 MIT Yes Details →
v2.11.1-0.20241031145332-5f282a5481c2 31 Oct 2024 M2 U1 MIT Yes Details →
v2.11.1-0.20241031131156-5d6079f8ad16 31 Oct 2024 M2 U1 MIT Yes Details →
v2.10.1-0.20241014203859-71770357e0cb 14 Oct 2024 M2 U1 MIT Yes Details →
v2.11.0 14 Oct 2024 M2 U1 MIT Yes Details →
v2.10.0 16 Sep 2024 M2 U1 MIT Yes Details →
v2.9.1-0.20240916115548-267e1ca3975c 16 Sep 2024 M2 U1 MIT Yes Details →
v2.9.1-0.20240913123305-af31cb392106 13 Sep 2024 M2 U1 MIT Yes Details →
v2.9.1-0.20240519192257-25db6b99518c 19 May 2024 M2 U1 MIT Yes Details →
v2.8.1-0.20240429163221-dbd982eba2a0 29 Apr 2024 M2 U1 MIT Yes Details →
v2.9.0 29 Apr 2024 M2 U1 MIT Yes Details →
v2.8.1-0.20240429122414-5840c447a662 29 Apr 2024 M2 U1 MIT Yes Details →
v2.8.0 03 Apr 2024 M2 U1 MIT Yes Details →
v2.6.1-0.20240319201323-288843facfaf 19 Mar 2024 M2 U1 MIT Yes Details →
v2.7.0 19 Mar 2024 M2 U1 MIT Yes Details →
v2.5.1-0.20240304122105-45fa8a46ae55 04 Mar 2024 M2 U1 MIT Yes Details →
v2.6.0 04 Mar 2024 M2 U1 MIT Yes Details →
v2.4.1-0.20240123123157-d88d88f917cd 23 Jan 2024 M2 U1 MIT Yes Details →
v2.5.0 23 Jan 2024 M2 U1 MIT Yes Details →
v2.4.1-0.20231120145612-d32c104a9a25 20 Nov 2023 M2 U1 MIT Yes Details →
v2.4.1-0.20231027080202-debe718854c4 27 Oct 2023 M2 U1 MIT Yes Details →
v2.4.1-0.20231024095351-47a83eeb1778 24 Oct 2023 M2 U1 MIT Yes Details →
v2.4.1-0.20231019124728-ec1e1cd3e0cb 19 Oct 2023 M2 U1 MIT Yes Details →
v2.4.0 12 Oct 2023 M2 U1 MIT Yes Details →
v2.2.1-0.20230825170143-421eac2dc0ce 25 Aug 2023 M2 U1 MIT Yes Details →
v2.3.0 25 Aug 2023 M2 U1 MIT Yes Details →
v2.2.0 11 Aug 2023 M2 U1 MIT Yes Details →
v2.0.0-20230724172621-dadb47ad1c11 24 Jul 2023 M2 U1 MIT Yes Details →
v2.0.2-0.20230724172621-dadb47ad1c11 24 Jul 2023 M2 U1 MIT Yes Details →
v2.1.0 24 Jul 2023 M2 U1 MIT Yes Details →
v2.0.1 02 Jun 2023 M2 U1 MIT Yes Details →
v2.0.0 16 Apr 2023 M2 U1 MIT Yes Details →
v2.0.0-20230416050321-9330cac2bbd5 16 Apr 2023 M2 U1 MIT Yes Details →
v2.0.0-20230415232805-057bef2c5bb6 15 Apr 2023 M2 U1 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2025 2

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/cli/go-gh/v2

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 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/cli/go-gh/v2

Is github.com/cli/go-gh/v2 safe to use?

Vulert records 3 vulnerabilities for github.com/cli/go-gh/v2 in Go: 0 critical, 0 high, 2 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/cli/go-gh/v2's Vulert package health score?

Vulert scores github.com/cli/go-gh/v2 76/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/cli/go-gh/v2 affected?

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

How many vulnerabilities does github.com/cli/go-gh/v2 have?

3 vulnerabilities are recorded for github.com/cli/go-gh/v2 in the Go ecosystem: 0 critical, 0 high, 2 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/cli/go-gh/v2 vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/cli/go-gh/v2 in the last 12 months, and the oldest entry in this database dates to 27 Nov 2024. 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/cli/go-gh/v2 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/cli/go-gh/v2 for upcoming vulnerabilities?

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