build: bump mapstructure/v2 to v2.4.0 to fix CVEs - #393
Merged
Conversation
hoshank10
changed the title
Fixes GO-2025-3787 (GHSA-fv92-fjc5-jj9h) and GO-2025-3900 (GHSA-2464-8j7c-4cjm), where sensitive information may leak in logs. GO-2025-3787 is reachable from the logger config-decoding path. Verified: make build and make test-unit pass; go directive unchanged.
hoshank10
force-pushed
the
bump-x-net-mapstructure-cves
branch
from
June 12, 2026 20:35
527c3b1 to
af3b60e
Compare
hoshank10
changed the title
xxx0624
approved these changes
Jun 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Bump
github.com/go-viper/mapstructure/v2v2.2.1 → v2.4.0.Why
govulncheck flags mapstructure via GO-2025-3787 (GHSA-fv92-fjc5-jj9h) and
GO-2025-3900 (GHSA-2464-8j7c-4cjm) — "sensitive information may leak in logs".
Source-mode (call-graph) analysis confirms GO-2025-3787 is reachable from
the logger config-decoding path. v2.4.0 clears both (3787 fixed in v2.3.0,
3900 in v2.4.0).
Verification
make build✅make test-unit✅ (the previously-failing job — now passes; go directive stays 1.23.0)Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.