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...
High CVSS 8.1
- CVE id
- CVE-2025-6013
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| HashiCorp Vault Runtimes and servers |
>= 1.10.0, < 1.20.2 | 1.20.2 |
| HashiCorp Vault Enterprise Runtimes and servers |
>= 1.10.0, <= 1.15.16 >= 1.10.0, < 1.20.2 >= 1.16.0, < 1.16.24 >= 1.17.0, < 1.18.13 >= 1.19.0, < 1.19.8 >= 1.20.0, < 1.20.2 |
1.16.24, 1.18.13, 1.19.8, 1.20.2 |
How to fix it
HashiCorp Vault (Runtimes and servers)
Upgrade HashiCorp Vault to 1.20.2 or later.
vault version
- Upgrade Vault (the hashicorp/vault image or binary) to the patched release.
HashiCorp Vault Enterprise (Runtimes and servers)
Upgrade HashiCorp Vault Enterprise to the fixed release of the line you run: 1.16.24, 1.18.13, 1.19.8, 1.20.2.
vault version
- Upgrade Vault Enterprise (the hashicorp/vault-enterprise image or binary) to the patched release.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
Vault and Vault Enterprise’s (“Vault”) ldap auth method may not have correctly enforced MFA if usernameasalias 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.
References
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.