VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/go-viper/mapstructure/v2: vulnerability history, versions and safety

github.com/go-viper/mapstructure/v2 is a package in the Go ecosystem. Vulert records 3 vulnerabilities for it across 43 releases, from Jun 2025 to Jan 2026. 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 M3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 26 Jan 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/go-viper/mapstructure/v2 vulnerabilities

Vulert verdict on github.com/go-viper/mapstructure/v2 v2.5.0 i

Updated on 23 Oct 2026

Action needed: v2.5.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 71/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.5.0 — affected i
  • Vulnerabilities on record 3 over 1 year · 1 in the last year i
  • Latest disclosure 26 Jan 2026 i
  • Highest CVSS 5.3 i
  • With no published fix 0 i
  • Stars 485 i
  • OpenSSF scorecard 4/10 i
  • Last release 9 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 22 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/go-viper/mapstructure/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.5.1-0.20260127154336-52aa5c6dc1d2 27 Jan 2026 M3 MIT Yes Details →
v2.5.1-0.20260127154234-41eafd1297d5 27 Jan 2026 M3 MIT Yes Details →
v2.5.1-0.20260112174959-cd52f897d661 12 Jan 2026 M3 MIT Yes Details →
v2.5.0 12 Jan 2026 M3 MIT Yes Details →
v2.4.1-0.20251217034126-6ffa40ae9136 17 Dec 2025 M3 MIT Yes Details →
v2.4.1-0.20251213031937-cf810d943440 13 Dec 2025 M3 MIT Yes Details →
v2.4.1-0.20251209172413-af2cf2a8a32d 09 Dec 2025 M3 MIT Yes Details →
v2.4.1-0.20251013204233-b54ec8245e54 13 Oct 2025 M3 MIT Yes Details →
v2.4.1-0.20250820154410-f9d9e58287f2 20 Aug 2025 M3 MIT Yes Details →
v2.4.1-0.20250807142409-bbfe61d1af95 07 Aug 2025 M3 MIT Yes Details →
v2.4.0 15 Jul 2025 M3 MIT Yes Details →
v2.3.1-0.20250714172930-9a861bc115f2 14 Jul 2025 M3 MIT Yes Details →
v2.3.1-0.20250712081825-de5deae90d84 12 Jul 2025 M3 MIT Yes Details →
v2.3.1-0.20250712055023-742921c9ba28 12 Jul 2025 M3 MIT Yes Details →
v2.3.1-0.20250626042247-5d1b937024c6 26 Jun 2025 M3 MIT Yes Details →
v2.2.2-0.20250616141124-8c61ec1924fc 16 Jun 2025 M3 MIT Yes Details →
v2.3.0 16 Jun 2025 M3 MIT Yes Details →
v2.2.2-0.20250616133344-ed3f92181528 16 Jun 2025 M3 MIT Yes Details →
v2.2.2-0.20250614130746-d0d489ccca2f 14 Jun 2025 M3 MIT Yes Details →
v2.2.2-0.20250606113443-1a66224d5e54 06 Jun 2025 M3 MIT Yes Details →
v2.2.2-0.20250510134510-396544120c0d 10 May 2025 M3 MIT Yes Details →
v2.2.2-0.20250419225903-232c7c6d592e 19 Apr 2025 M3 MIT Yes Details →
v2.2.2-0.20250417123055-ef196921ef24 17 Apr 2025 M3 MIT Yes Details →
v2.2.2-0.20250326061814-8cfa81661a59 26 Mar 2025 M3 MIT Yes Details →
v2.2.2-0.20250315140719-1072f346635a 15 Mar 2025 M3 MIT Yes Details →
v2.2.2-0.20250218145611-71e356cd8b5f 18 Feb 2025 M3 MIT Yes Details →
v2.2.2-0.20250109111121-7aa50a4e78df 09 Jan 2025 M3 MIT Yes Details →
v2.2.2-0.20241118124956-8101c0bc3534 18 Nov 2024 M3 MIT Yes Details →
v2.2.2-0.20241006081944-0b972d9949e7 06 Oct 2024 M3 MIT Yes Details →
v2.2.1 22 Sep 2024 M3 MIT Yes Details →
v2.2.0 20 Sep 2024 M3 MIT Yes Details →
v2.1.0 12 Aug 2024 M3 MIT Yes Details →
v2.0.1-0.20240811220347-2842dc86cbc8 11 Aug 2024 M3 MIT Yes Details →
v2.0.1-0.20240805221037-cafeac4f3556 05 Aug 2024 M3 MIT Yes Details →
v2.0.1-0.20240720132425-fd1be46fa74d 20 Jul 2024 M3 MIT Yes Details →
v2.0.1-0.20240602085007-0382e5b7e398 02 Jun 2024 M3 MIT Yes Details →
v2.0.0 02 Jun 2024 M3 MIT Yes Details →
v2.0.0-alpha.1.0.20240602075001-57a3d74ac329 02 Jun 2024 M3 MIT Yes Details →
v2.0.0-alpha.1.0.20240227123954-cb699d2a12c6 27 Feb 2024 M3 MIT Yes Details →
v2.0.0-alpha.1.0.20240226124921-b71c54176d2b 26 Feb 2024 M3 MIT Yes Details →
v2.0.0-alpha.1.0.20231222143158-7017a6863b51 22 Dec 2023 M3 MIT Yes Details →
v2.0.0-20231219210202-579c0fe9ed2f 19 Dec 2023 M3 MIT Yes Details →
v2.0.0-alpha.1 19 Dec 2023 M3 MIT Yes Details →

All 43 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
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/go-viper/mapstructure/v2

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Sensitive Information Leak in Mapstructure Package: GHSA-fv92-fjc5-jj9h 5.3 medium 2.3.0 27 Jun 2025
Sensitive Information Leak in go-viper's mapstructure Package 5.3 medium 2.4.0 21 Aug 2025
Sensitive Information Leak in go-viper's mapstructure - GHSA-86rf-68f4-2cph 5.3 medium 2.4.0 26 Jan 2026

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/go-viper/mapstructure/v2

Is github.com/go-viper/mapstructure/v2 safe to use?

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

Vulert scores github.com/go-viper/mapstructure/v2 71/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/go-viper/mapstructure/v2 affected?

Yes. v2.5.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.

Which version of github.com/go-viper/mapstructure/v2 should I use?

v2.5.0 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/go-viper/mapstructure/v2 have?

3 vulnerabilities are recorded for github.com/go-viper/mapstructure/v2 in the Go ecosystem: 0 critical, 0 high, 3 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/go-viper/mapstructure/v2 vulnerabilities disclosed?

1 vulnerability was recorded for github.com/go-viper/mapstructure/v2 in the last 12 months, and the oldest entry in this database dates to 27 Jun 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/go-viper/mapstructure/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/go-viper/mapstructure/v2 for upcoming vulnerabilities?

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