CVE-2025-6011 | Timing Side-Channel in Vault’s Userpass Auth Method

A timing side channel in Vault and Vault Enterprise’s (“Vault”) userpass auth method allowed an attacker to distinguish between existing and non-existing users, and potentially enumerate valid usernames for Vault’s Userpass auth method. Fixed in Vault Community Edition 1.20.1 and Vault Enterprise 1.20.1, 1.19.7, 1.18.12, and 1.16.23.

Published: 2025-08-01 Last update: 2025-08-13 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-6011 is rated Low Risk (25.8/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.12%). 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-6011

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-05-28 0.02% 0.12% +0.11%
2 2025-11-21 0.06% 0.02% -0.04%
3 2025-11-18 — 0.06% —

Full EPSS history (4 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.7 3.1 LOW
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/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:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.2 1.4 [email protected]

Weakness enumeration for CVE-2025-6011

GitHub Security Advisory for CVE-2025-6011

GHSA-mwgr-84fv-3jh9 · Severity: low · Ecosystem: go — Hashicorp Vault has an Observable Discrepancy on Existing and Non-Existing Users

OS Trackers for CVE-2025-6011

vendor priority summary link
alpine — CVE-2025-6011: 1 source package rows (vault); 11 state rows across 1 repos (edge-community); fixed 0, open 11. https://security.alpinelinux.org/vuln/CVE-2025-6011
redhat low — https://access.redhat.com/security/cve/CVE-2025-6011

Affected software / configurations for CVE-2025-6011

Vendor Product Version Raw CPE
hashicorp vault < 1.16.23 cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*
hashicorp vault < 1.20.1 cpe:2.3:a:hashicorp:vault:*:*:*:*:-:*:*:*
hashicorp vault >= 1.17.0, < 1.18.12 cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*
hashicorp vault >= 1.19.0, < 1.19.7 cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*
hashicorp vault 1.20.0 cpe:2.3:a:hashicorp:vault:1.20.0:*:*:*:enterprise:*:*:*

References for CVE-2025-6011

cvelogic Threat Intelligence