Timing Side-Channel in Vault’s Userpass Auth Method
cve-program · CVE-2025-6011
PublishedA 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.
Read the publisher's advisoryeuvd · EUVD-2025-23395
PublishedA 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.
Read the publisher's advisorynvd · CVE-2025-6011
PublishedA 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.
Read the publisher's advisoryosv · GHSA-mwgr-84fv-3jh9
PublishedA 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.
Read the publisher's advisoryosv · GO-2025-3839
PublishedHashicorp Vault has an Observable Discrepancy on Existing and Non-Existing Users in github.com/hashicorp/vault
Read the publisher's advisoryAffected versions, risk and source history
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2025-6011
PublishedTiming 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.
- Source published
- 1 Aug 2025 18:00:24 UTC
- Source modified
- 1 Aug 2025 19:06:58 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
euvd · EUVD-2025-23395
PublishedA 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. Fix…
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.
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Aug 1, 2025, 6:00:24 PM
dateUpdated: Aug 1, 2025, 7:06:58 PM
3 related source bulletins · separate from aliases
openSUSE-SU-2025:15460-1: openbao-2.3.2-1.1 on GA media
CVE-2025-54996 · CVE-2025-55000 · CVE-2025-55003 · CVE-2025-5999 · CVE-2025-6000 · CVE-2025-6004 · CVE-2025-6010 · CVE-2025-6011 · CVE-2025-6013 · CVE-2025-6014 · CVE-2025-6015
WID-SEC-W-2025-1702: Hashicorp Vault Community und Enterprise: Mehrere Schwachstellen
CVE-2025-5999 · CVE-2025-6000 · CVE-2025-6004 · CVE-2025-6011 · CVE-2025-6015 · CVE-2025-6037 · CVE-2025-6014
openSUSE-SU-2025:15434-1: govulncheck-vulndb-0.0.20250811T192933-1.1 on GA media
CVE-2021-21411 · CVE-2025-44779 · CVE-2025-50738 · CVE-2025-53534 · CVE-2025-53942 · CVE-2025-54386 · CVE-2025-54388 · CVE-2025-54410 · CVE-2025-54424 · CVE-2025-54576 · CVE-2025-54799 · CVE-2025-54801 · CVE-2025-54996 · CVE-2025-54997 · CVE-2025-54998 · CVE-2025-54999 · CVE-2025-55000 · CVE-2025-55001 · CVE-2025-55003 · CVE-2025-5999 · CVE-2025-6000 · CVE-2025-6004 · CVE-2025-6011 · CVE-2025-6013 · CVE-2025-6014 · CVE-2025-6015 · CVE-2025-6037 · CVE-2025-7195 · CVE-2025-8341
- Source published
- Aug 1, 2025, 6:00:24 PM (timezone not stated)
- Source modified
- Aug 1, 2025, 7:06:58 PM (timezone not stated)
- Saved here
- 15 Nov 2026 05:33:56 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 3.1 · 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
nvd · CVE-2025-6011
PublishedA 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. Fix…
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.
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Analyzed
Weakness classifications: CWE-203
Original publisher date fields
published: 2025-08-01T18:15:56.713
lastModified: 2026-06-17T10:00:59.130
3 source CPE criteria · context only
- cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*
- cpe:2.3:a:hashicorp:vault:*:*:*:*:-:*:*:*
- cpe:2.3:a:hashicorp:vault:1.20.0:*:*:*:enterprise:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
- Source published
- 1 Aug 2025 18:15:56 UTC
- Source modified
- 17 Jun 2026 10:00:59 UTC
- Saved here
- 25 Oct 2026 03:17:27 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · [email protected] · Secondary · 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
osv · GHSA-mwgr-84fv-3jh9
PublishedHashicorp Vault has an Observable Discrepancy on Existing and Non-Existing Users
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.
- Source published
- 1 Aug 2025 18:31:19 UTC
- Source modified
- 10 Sep 2026 03:50:27 UTC
- Saved here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Publisher rating · LOW
osv · GO-2025-3839
PublishedHashicorp Vault has an Observable Discrepancy on Existing and Non-Existing Users in github.com/hashicorp/vault
Hashicorp Vault has an Observable Discrepancy on Existing and Non-Existing Users in github.com/hashicorp/vault
- Source published
- 11 Aug 2025 17:24:51 UTC
- Source modified
- 4 Feb 2026 03:13:41 UTC
- Saved here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.