How severe is CVE-2025-6013?

CVE-2025-6013 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2025-6013 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (39th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-6013?

CVE-2025-6013 primarily affects Hashicorp Vault. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2025-6013?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2025-6013 have an EU (EUVD) identifier?

Yes. CVE-2025-6013 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-23817.

When was CVE-2025-6013 published?

CVE-2025-6013 was published on 2025-08-06 and last updated on 2026-06-17.

CVE-2025-6013

CVE-2025-6013 is a medium-severity vulnerability in Hashicorp Vault with a CVSS 3.x base score of 6.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-156.

Key facts

Severity: Medium (CVSS 3.x base score 6.5)
EPSS exploit prediction: 1% (39th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-23817
Weakness: CWE-156
Affected product: Hashicorp Vault
Published: 2025-08-06
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2025-6013?: 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.
How severe is CVE-2025-6013?: CVE-2025-6013 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2025-6013 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (39th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-6013?: CVE-2025-6013 primarily affects Hashicorp Vault. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2025-6013?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-6013 have an EU (EUVD) identifier?: Yes. CVE-2025-6013 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-23817.
When was CVE-2025-6013 published?: CVE-2025-6013 was published on 2025-08-06 and last updated on 2026-06-17.

References

https://discuss.hashicorp.com/t/hcsec-2025-20-vault-ldap-mfa-enforcement-bypass-when-using-username-as-alias/76092

Affected products (2)

cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*
cpe:2.3:a:hashicorp:vault:*:*:*:*:-:*:*:*

More vulnerabilities in Hashicorp Vault

CVE-2020-35192 — Critical (CVSS 9.8): The official vault docker images before 0.11.6 contain a blank password for a root user. System using the vault docker…
CVE-2020-12757 — Critical (CVSS 9.8): HashiCorp Vault and Vault Enterprise 1.4.0 and 1.4.1, when configured with the GCP Secrets Engine, may incorrectly…
CVE-2025-6000 — Critical (CVSS 9.1): A privileged Vault operator within the root namespace with write permission to {{sys/audit}} may obtain code execution…
CVE-2022-40186 — Critical (CVSS 9.1): An issue was discovered in HashiCorp Vault and Vault Enterprise before 1.11.3. A vulnerability in the Identity Engine…
CVE-2022-36129 — Critical (CVSS 9.1): HashiCorp Vault Enterprise 1.7.0 through 1.9.7, 1.10.4, and 1.11.0 clusters using Integrated Storage expose an…
CVE-2020-10661 — Critical (CVSS 9.1): HashiCorp Vault and Vault Enterprise versions 0.11.0 through 1.3.3 may, under certain circumstances, have existing…

All CVEs affecting Hashicorp Vault →

Other CWE-156 vulnerabilities

CVE-2025-55001 — Medium (CVSS 6.5): OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including secrets,…
CVE-2025-55000 — Medium (CVSS 6.5): OpenBao exists to provide a software solution to manage, store, and distribute sensitive data including secrets,…
CVE-2025-6014 — Medium (CVSS 6.5): Vault and Vault Enterprise’s (“Vault”) TOTP Secrets Engine code validation endpoint is susceptible to code reuse…
CVE-2025-55127 — Medium (CVSS 5.4): HackerOne community member Dao Hoang Anh (yoyomiski) has reported an improper neutralization of whitespace in the…

Browse all CWE-156 vulnerabilities →