Skip to content
OpenAdvisories
Medium · 6.8 CVE-2025-6037 BIT-vault-2025-6037EUVD-2025-23391GHSA-6c5r-4wfc-3mcxGO-2025-3836

Vault Certificate Auth Method Did Not Validate Common Name For Non-CA Certificates

Published Aug 1, 2025 · Updated Feb 26, 2026 · Assigned by HashiCorp

Description

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.

Affected products

VendorProductAffectedFixed
HashiCorp Vault < 1.20.1 1.20.1
HashiCorp Vault Enterprise < 1.20.1 1.20.1

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
SLES 15 SP6 govulncheck-vulndb 0.0.20250814T182633-150000.1.98.1 SUSE-SU-2025:02912-1
ReleasePackageFixed inAdvisory
openSUSE Tumbleweed govulncheck-vulndb 0.0.20250811T192933-1.1 openSUSE-SU-2025:15434-1
openSUSE Leap 15.6 govulncheck-vulndb 0.0.20250814T182633-150000.1.98.1 SUSE-SU-2025:02912-1

Wolfi

ReleasePackageFixed inAdvisory
Wolfi rolling splunk-otel-collector 0.138.0-r0 —

Affected packages

EcosystemPackageAffectedFixedRecord
Go github.com/hashicorp/vault < 1.20.1 1.20.1 GHSA-6c5r-4wfc-3mcx

Advisories 3

References