CVE-2025-6013 | Vault LDAP MFA Enforcement Bypass When Using Username As Alias

Vault and Vault Enterprise’s (“Vault”) ldap auth method may not have correctly enforced MFA if username_as_alias was set to true and a user had multiple CNs that are equal but with leading or trailing spaces. Fixed in Vault Community Edition 1.20.2 and Vault Enterprise 1.20.2, 1.19.8, 1.18.13, and 1.16.24.

Published: 2025-08-06 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-6013 is rated Low Risk (39.1/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.47%). 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-6013

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-06-15 0.16% 0.47% +0.30%
2 2026-06-02 0.05% 0.16% +0.11%
3 2026-05-02 0.05%

Full EPSS history (4 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
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:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
1.2 5.2 [email protected]
8.1 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
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:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
2.8 5.2 [email protected]

Weakness enumeration for CVE-2025-6013

GitHub Security Advisory for CVE-2025-6013

GHSA-7rx2-769v-hrwf · Severity: medium · Ecosystem: go — HashiCorp Vault ldap auth method may not have correctly enforced MFA

OS Trackers for CVE-2025-6013

vendor priority summary link
alpine CVE-2025-6013: 1 source package rows (vault); 3 state rows across 1 repos (edge-community); fixed 0, open 3. https://security.alpinelinux.org/vuln/CVE-2025-6013
redhat medium https://access.redhat.com/security/cve/CVE-2025-6013
suse medium CVE-2025-6013 severity moderate: SUSE including 14 source package names (ca-certificates-mozilla-2.84-slfo.1.1_1.1, govulncheck-vulndb-0.0.20250811T192933-1.1, …), 25 product×package rows across 13 product lines (Container suse/sl-micro/6.0/base-os-container, Container suse/sl-micro/6.0/toolbox, … (13 product lines)): Fixed 25. https://www.suse.com/security/cve/CVE-2025-6013/

Affected software / configurations for CVE-2025-6013

Vendor Product Version Raw CPE
hashicorp vault >= 1.10.0, <= 1.15.16 cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*
hashicorp vault >= 1.10.0, < 1.20.2 cpe:2.3:a:hashicorp:vault:*:*:*:*:-:*:*:*
hashicorp vault >= 1.16.0, < 1.16.24 cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*
hashicorp vault >= 1.17.0, < 1.18.13 cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*
hashicorp vault >= 1.19.0, < 1.19.8 cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*
hashicorp vault >= 1.20.0, < 1.20.2 cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*

References for CVE-2025-6013

cvelogic Threat Intelligence