CVE-2025-6037 | Vault Certificate Auth Method Did Not Validate Common Name For Non-CA Certificates

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.

Published: 2025-08-01 Last update: 2025-08-13 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-6037 is rated Moderate Risk (42/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.20%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-6037

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-28 0.06% 0.20% +0.14%
2 2026-04-17 0.02% 0.06% +0.04%
3 2025-08-02 — 0.02% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-6037

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.8 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 0.9 5.9 [email protected]

Weakness enumeration for CVE-2025-6037

GitHub Security Advisory for CVE-2025-6037

GHSA-6c5r-4wfc-3mcx · Severity: medium · Ecosystem: go — Hashicorp Vault has Incorrect Validation for Non-CA Certificates

OS Trackers for CVE-2025-6037

vendor priority summary link
alpine — CVE-2025-6037: 1 source package rows (vault); 11 state rows across 1 repos (edge-community); fixed 0, open 11. https://security.alpinelinux.org/vuln/CVE-2025-6037
redhat medium — https://access.redhat.com/security/cve/CVE-2025-6037

Affected software / configurations for CVE-2025-6037

Vendor Product Version Raw CPE
hashicorp vault < 1.16.23 cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*
hashicorp vault < 1.20.1 cpe:2.3:a:hashicorp:vault:*:*:*:*:-:*:*:*
hashicorp vault >= 1.17.0, < 1.18.12 cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*
hashicorp vault >= 1.19.0, < 1.19.7 cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*
hashicorp vault 1.20.0 cpe:2.3:a:hashicorp:vault:1.20.0:*:*:*:enterprise:*:*:*

References for CVE-2025-6037

cvelogic Threat Intelligence