CVE-2025-11065: Github.com/go-viper/mapstructure/v2: go-viper's mapstructure may leak sensitive information in logs in github.com/go-viper/mapstructure
A flaw was found in github.com/go-viper/mapstructure/v2, in the field processing component using mapstructure.WeakDecode. This vulnerability allows information disclosure through detailed error messages that may leak sensitive input values via malformed user-supplied data processed in security-critical contexts.
Security readout for executives and security teams
Plain-English summary
CVE-2025-11065 is an information disclosure issue in Go Viper’s mapstructure v2 library. Under certain malformed input conditions, detailed decoding errors may expose sensitive input values in logs. This is not described as code execution or service takeover, but it can create business risk if secrets, tokens, or personal data are processed and logged.
Executive priority
Handle as a scheduled confidentiality-risk remediation. Prioritize systems handling secrets, credentials, customer data, or regulated information, especially where logs are broadly accessible or exported to centralized platforms.
Technical view
The flaw is classified as CWE-209. It affects field processing using mapstructure.WeakDecode, where verbose error messages may disclose sensitive input values. The CVSS 3.1 score is 5.3: network reachable, high complexity, no privileges required, user interaction required, high confidentiality impact, and no integrity or availability impact.
Likely exposure
Exposure is most likely in Go applications or Red Hat-shipped components that use github.com/go-viper/mapstructure/v2 and process malformed user-supplied data in sensitive contexts. Risk depends on whether decode errors are logged, who can trigger those errors, and who can read the logs.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. Successful abuse appears situational: an attacker would need a path to supply malformed data and cause detailed errors to be logged where sensitive values are retained or accessible.
Researcher notes
Affected Red Hat products and packages are listed, but exact fixed versions are not provided in the source bundle. The upstream commit and GitHub advisory are relevant references. Do not assume exploitability without confirming application-specific use of WeakDecode and logging behavior.
Mitigation direction
Check the GitHub advisory and Red Hat CVE page for fixed versions or official guidance.
Update affected dependencies or Red Hat packages when vendor-provided fixes are available.
Reduce logging of detailed decode errors in security-critical paths.
Avoid processing secrets through WeakDecode when handling untrusted input.
Restrict access to application, platform, and collector logs that may contain sensitive data.
Validation and detection
Inventory Go applications using github.com/go-viper/mapstructure/v2.
Search code for mapstructure.WeakDecode in user-input processing paths.
Identify Red Hat listed products or packages deployed in your environment.
Review logs for decode errors that may include sensitive values.
Confirm remediation status against vendor advisories, not only package presence.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-209: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-209 · source CWE mapping
Generation of Error Message Containing Sensitive Information
Generation of Error Message Containing Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.