Vulnerability Database · Go · Package report

github.com/hashicorp/go-getter/v2: vulnerability history, versions and safety

github.com/hashicorp/go-getter/v2 is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 0 release, first recorded in Feb 2023. 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 U2
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/hashicorp/go-getter/v2 v2.2.6 i

Updated on 23 Oct 2026

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

Package health score 83/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release v2.2.6 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 17 Feb 2023 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1,826 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence MPL-2.0 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/hashicorp/go-getter/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.2.6 22 Oct 2026 none MPL-2.0 — Details →
v2.2.5 16 Sep 2026 none MPL-2.0 — Details →
v2.2.4 11 Sep 2026 none MPL-2.0 — Details →
v2.2.4-0.20260911052237-c2b656b78e5f 11 Sep 2026 none MPL-2.0 — Details →
v2.2.4-0.20260114142348-88847d8eea7f 14 Jan 2026 none MPL-2.0 — Details →
v2.2.3-0.20250815191153-e7698707f48e 15 Aug 2025 none MPL-2.0 — Details →
v2.2.4-0.20250815191153-e7698707f48e 15 Aug 2025 none MPL-2.0 — Details →
v2.2.3 23 Jul 2024 none MPL-2.0 — Details →
v2.2.2 17 May 2024 none MPL-2.0 — Details →
v2.2.1 13 Mar 2023 none MPL-2.0 — Details →
v2.2.0 13 Feb 2023 none MPL-2.0 — Details →
v2.0.0-20230210184905-017a2ee8897e 10 Feb 2023 none MPL-2.0 — Details →
v2.1.1 29 Nov 2022 none MPL-2.0 — Details →
v2.1.1-0.20220523190028-106ef8d80083 23 May 2022 none MPL-2.0 — Details →
v2.0.3-0.20220523170440-31c3313ffd18 23 May 2022 none MPL-2.0 — Details →
v2.1.0 23 May 2022 none MPL-2.0 — Details →
v2.0.0-20220519155656-38e97387488f 19 May 2022 none MPL-2.0 — Details →
v2.0.3-0.20220519155656-38e97387488f 19 May 2022 none MPL-2.0 — Details →
v2.0.2 21 Mar 2022 none MPL-2.0 — Details →
v2.0.1 01 Feb 2022 none MPL-2.0 — Details →
v2.0.1-0.20220131102235-ea452ad5355a 31 Jan 2022 none MPL-2.0 — Details →
v2.0.1-0.20220113143827-4dd0b87e5089 13 Jan 2022 none MPL-2.0 — Details →
v2.0.1-0.20210603112840-d38eed1cce85 03 Jun 2021 none MPL-2.0 — Details →
v2.0.0 04 Jan 2021 none MPL-2.0 — Details →
v2.0.0-20201008113253-331021918dba 08 Oct 2020 none MPL-2.0 — Details →
v2.0.0-20201001102414-74576d5f550a 01 Oct 2020 none MPL-2.0 — Details →
v2.0.0-20200930133925-54967114a29a 30 Sep 2020 none MPL-2.0 — Details →
v2.0.0-20200710154144-e9a334a7a252 10 Jul 2020 none MPL-2.0 — Details →
v2.0.0-20200710153759-d269410c9f14 10 Jul 2020 none MPL-2.0 — Details →
v2.0.0-20200604122502-a6995fa1edad 04 Jun 2020 none MPL-2.0 — Details →
v2.0.0-20200604090845-872c8edccae9 04 Jun 2020 none MPL-2.0 — Details →
v2.0.0-20200603151204-1ab379be7fbd 03 Jun 2020 none MPL-2.0 — Details →
v2.0.0-20200518081638-5b5e57151574 18 May 2020 none MPL-2.0 — Details →
v2.0.0-20200514151440-7b188cad6b7d 14 May 2020 none MPL-2.0 — Details →
v2.0.0-20200514142349-eacc0bb898b3 14 May 2020 none MPL-2.0 — Details →
v2.0.0-20200513115501-7327304c4db9 13 May 2020 none MPL-2.0 — Details →
v2.0.0-20200511090339-3107ec4af37a 11 May 2020 none MPL-2.0 — Details →
v2.0.0-20200511085045-ad575698c524 11 May 2020 none MPL-2.0 — Details →
v2.0.0-20200428131008-7ca0077af588 28 Apr 2020 none MPL-2.0 — Details →
v2.0.0-20200428121039-ea2d4f264fe2 28 Apr 2020 none MPL-2.0 — Details →
v2.0.0-20200427140258-32e0fe310a1d 27 Apr 2020 none MPL-2.0 — Details →
v2.0.0-20200427115226-0238bda28cb4 27 Apr 2020 none MPL-2.0 — Details →
v2.0.0-20200427114632-bd1290134e28 27 Apr 2020 none MPL-2.0 — Details →
v2.0.0-20200427112119-1ed5a3a41510 27 Apr 2020 none MPL-2.0 — Details →
v2.0.0-20200424131830-e520fc4911a2 24 Apr 2020 none MPL-2.0 — Details →
v2.0.0-20200422125728-075c9733a67d 22 Apr 2020 none MPL-2.0 — Details →
v2.0.0-20200422093134-62a9f0a23e9f 22 Apr 2020 none MPL-2.0 — Details →
v2.0.0-20200326134438-527b5c1ca52d 26 Mar 2020 none MPL-2.0 — Details →
v2.0.0-20200326133907-9ebf6d868bf5 26 Mar 2020 none MPL-2.0 — Details →
v2.0.0-20200318090939-0b1d527d9793 18 Mar 2020 none MPL-2.0 — Details →
v2.0.0-20200317165601-76824e3fe8cd 17 Mar 2020 none MPL-2.0 — Details →
v2.0.0-20200206160058-e2a28063d6e7 06 Feb 2020 none MPL-2.0 — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 2

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/hashicorp/go-getter/v2

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/hashicorp/go-getter/v2

Is github.com/hashicorp/go-getter/v2 safe to use?

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

Vulert scores github.com/hashicorp/go-getter/v2 83/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/hashicorp/go-getter/v2 affected?

No. v2.2.6, 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.

How many vulnerabilities does github.com/hashicorp/go-getter/v2 have?

2 vulnerabilities are recorded for github.com/hashicorp/go-getter/v2 in the Go ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 2 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/hashicorp/go-getter/v2 vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/hashicorp/go-getter/v2 in the last 12 months, and the oldest entry in this database dates to 17 Feb 2023. 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/hashicorp/go-getter/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/hashicorp/go-getter/v2 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/hashicorp/go-getter/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.