CVE-2025-6013
Hashicorp Vault 1.10.0 – 1.15.16
Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2025-6013 is a medium-severity Improper Neutralization of Whitespace (CWE-156) vulnerability in Hashicorp Vault. Its CVSS base score is 6.5 (Medium).
Operationally, ranked at the 41th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-23817
Vulnerability Data
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…
more
1.20.2 and Vault Enterprise 1.20.2, 1.19.8, 1.18.13, and 1.16.24.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
SI-10 directly requires validation of inputs, which structurally prevents improper whitespace handling before data reaches downstream components.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input neutralization to prevent whitespace issues.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure coding standards directly require proper input sanitization and neutralization of special elements like whitespace.
Security testing can detect whitespace handling issues but does not prevent them at the source.
Secure development lifecycle includes input validation and sanitization practices that can prevent improper whitespace handling.
Application security requirements typically mandate proper input validation and neutralization of special characters including whitespace.
Secure system architecture principles may indirectly support input handling but do not specifically address whitespace neutralization.