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

Published Aug 1, 2025
·
Updated

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 Software

8 affected componentsFixes available
HashiCorp Vault Community Edition<1.20.1
HashiCorp Vault Enterprise>=1.16.23<1.20.1
go/github.com/hashicorp/vault<1.20.1
1.20.1
HashiCorp Vault<1.16.23
HashiCorp Vault<1.20.1
HashiCorp Vault>=1.17.0<1.18.12
HashiCorp Vault>=1.19.0<1.19.7
HashiCorp Vault=1.20.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/github.com/hashicorp/vault to a version that resolves this vulnerability.

    Fixed in 1.20.1
  2. Upgrade

    Upgrade HashiCorp Vault Community Edition to a version that resolves this vulnerability.

    Fixed in 1.20.1
  3. Upgrade

    Upgrade HashiCorp Vault Enterprise to a version that resolves this vulnerability.

    Fixed in 1.20.1
  4. Upgrade

    Upgrade HashiCorp Vault Enterprise to a version that resolves this vulnerability.

    Fixed in 1.19.7
  5. Upgrade

    Upgrade HashiCorp Vault Enterprise to a version that resolves this vulnerability.

    Fixed in 1.18.12
  6. Upgrade

    Upgrade HashiCorp Vault Enterprise to a version that resolves this vulnerability.

    Fixed in 1.16.23

Event History

Aug 1, 2025
CVE Published
via MITRE·05:52 PM
Data Sourced
via MITRE·05:52 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·06:31 PM
Data Sourced
via GitHub·06:31 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-6037?

CVE-2025-6037 is classified as a critical vulnerability due to improper validation of client certificates.

2

How do I fix CVE-2025-6037?

To fix CVE-2025-6037, ensure that Vault is configured to use a CA certificate for client authentication.

3

What systems are affected by CVE-2025-6037?

CVE-2025-6037 affects HashiCorp Vault Community Edition versions up to 1.20.1 and HashiCorp Vault Enterprise versions from 1.16.23 to 1.20.1.

4

What are the implications of CVE-2025-6037?

The implications of CVE-2025-6037 include the potential for unauthorized access to the Vault due to incorrect certificate validation.

5

Is there a workaround for CVE-2025-6037?

A possible workaround for CVE-2025-6037 is to temporarily disable the TLS certificate authentication method until a proper fix is implemented.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203