CVE-2025-6037 Affecting vault package, versions <1.20.1-r0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-MINIMOSLATEST-VAULT-13312358
- published6 Oct 2025
- disclosed1 Aug 2025
Introduced: 1 Aug 2025
CVE-2025-6037 (opens in a new tab)How to fix?
Upgrade Minimos:latest vault to version 1.20.1-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream vault package and not the vault package as distributed by Minimos.
See How to fix? for Minimos:latest relevant fixed versions and status.
Vault and Vault Enterprise (“Vault”) TLS certificate auth method did not correctly validate client certificates when configured with a non-CA certificate as [+trusted certificate+|https://developer.hashicorp.com/vault/api-docs/auth/cert#certificate]. In this configuration, an attacker may be able to craft a malicious certificate that could be used to impersonate another user. Fixed in Vault Community Edition 1.20.1 and Vault Enterprise 1.20.1, 1.19.7, 1.18.12, and 1.16.23.
References
- https://www.cve.org/CVERecord?id=CVE-2025-6037
- https://github.com/advisories/GHSA-6c5r-4wfc-3mcx
- https://osv.dev/vulnerability/MINI-whj8-4wpm-p4gj
- https://osv.dev/vulnerability/CVE-2025-6037
- https://discuss.hashicorp.com/t/hcsec-2025-18-vault-certificate-auth-method-did-not-validate-common-name-for-non-ca-certificates/76037