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.

Published: 2026-01-26 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-11065 is rated Low Risk (21.5/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.01%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-11065

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-01-27 0.01%

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-11065

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
1.6 3.6 [email protected]

Weakness enumeration for CVE-2025-11065

GitHub Security Advisory for CVE-2025-11065

GHSA-2464-8j7c-4cjm · Severity: medium · Ecosystem: go — go-viper's mapstructure May Leak Sensitive Information in Logs When Processing Malformed Data

OS Trackers for CVE-2025-11065

vendor priority summary link
debian not yet assigned CVE-2025-11065 not yet assigned priority: Debian including 1 source packages (golang-github-go-viper-mapstructure), 3 status rows across 3 suites (forky, sid, trixie): resolved 2, open 1. https://security-tracker.debian.org/tracker/CVE-2025-11065
redhat medium https://access.redhat.com/security/cve/CVE-2025-11065
suse medium CVE-2025-11065 severity moderate: SUSE including 382 source package names (1.1.0-1.1:trivy-0.67.2-150000.1.6.1, 2.2.1-5.22:libaudit1-3.1.1-slfo.1.1_2.1, …), 708 product×package rows across 79 product lines (Container private-registry/harbor-trivy-adapter, Container suse/manager/4.3/proxy-httpd, … (79 product lines)): Known Not Affected 278, Known Affected 231, Fixed 197, First Fixed 2. https://www.suse.com/security/cve/CVE-2025-11065/
ubuntu medium CVE-2025-11065 medium priority: Ubuntu including 1 source packages (golang-github-go-viper-mapstructure), 5 status rows across 5 suites (jammy, noble, plucky, questing, upstream): DNE 2, needs-triage 2, ignored 1. https://ubuntu.com/security/CVE-2025-11065

Affected software / configurations for CVE-2025-11065

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-11065

cvelogic Threat Intelligence