Is github.com/go-viper/mapstructure/v2 2.1 vulnerable?
Go · 1 release from 2.1.0 to 2.1.0 · latest github.com/go-viper/mapstructure/v2 is 2.5.0 · checked 18 Nov 2026
Yes: 4 known advisories
Yes. github.com/go-viper/mapstructure/v2 2.1.0, the last 2.1 release, is affected by 4 known security advisories (2 medium, 2 low), including CVE-2025-11065, CVE-2025-11065. Upgrade to 2.4.0 or later to fix all of them.
go get github.com/go-viper/mapstructure/v2@v2.4.0Is your project on an affected github.com/go-viper/mapstructure/v2?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/go-viper/mapstructure/v2 2.1.0
Go-viper's mapstructure May Leak Sensitive Information in Logs in github.com/go-viper/mapstructure
- Affected
- <2.4.0
- Fixed in
- 2.4.0
go-viper's mapstructure May Leak Sensitive Information in Logs When Processing Malformed Data
- Affected
- <2.4.0
- Fixed in
- 2.4.0
May leak sensitive information in logs when processing malformed data in github.com/go-viper/mapstructure
- Affected
- <2.3.0
- Fixed in
- 2.3.0
mapstructure May Leak Sensitive Information in Logs When Processing Malformed Data
- Affected
- <2.3.0
- Fixed in
- 2.3.0
Which of your client projects are still on github.com/go-viper/mapstructure/v2 2.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/go-viper/mapstructure/v2 version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/go-viper/mapstructure/v2 versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.