CVE-2025-6037
mediumpriority · track · 0EPSS 0.003 · 17 %ileDEEURUUSEPSS · scored 2026-10-27
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (35)
Products and version ranges known to be affected.
advisories (4)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2025-1702Hashicorp Vault Community und Enterprise: Mehrere SchwachstellenDeutsch2025-08-03csaf · cert_bundDE
Ein Angreifer kann mehrere Schwachstellen in Hashicorp Vault ausnutzen, um erhöhte Rechte zu erlangen, Sicherheitsmaßnahmen zu umgehen, beliebigen Code auszuführen und vertrauliche Informationen preiszugeben.
- GHSA-6c5r-4wfc-3mcxHashicorp Vault has Incorrect Validation for Non-CA Certificates2025-08-01ghsa · osvUS
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.
- BIT-vault-2025-6037Vault Certificate Auth Method Did Not Validate Common Name For Non-CA Certificates2025-08-05vendor · osvUS
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.
- GO-2025-3836Hashicorp Vault has Incorrect Validation for Non-CA Certificates in github.com/hashicorp/vault2025-08-11vendor · osvUS
Hashicorp Vault has Incorrect Validation for Non-CA Certificates in github.com/hashicorp/vault
also known as (7)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (3)
External citations — patches, advisories, analysis.
- https://discuss.hashicorp.com/t/hcsec-2025-18-vault-certificate-auth-method-did-not-validate-common-name-for-non-ca-certificates/76037cnnvd
- https://discuss.hashicorp.com/t/hcsec-2025-18-vault-certificate-auth-method-did-not-validate-common-name-for-non-ca-certificates/76037enisa_euvd
- https://discuss.hashicorp.com/t/hcsec-2025-18-vault-certificate-auth-method-did-not-validate-common-name-for-non-ca-certificates/76037Vendor Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan