CVE-2026-5052: Vault Vulnerable to Server-Side Request Forgery in ACME Challenge Validation via Attacker-Controlled DNS

Published Apr 17, 2026
·
Updated

Vault’s PKI engine’s ACME validation did not reject local targets when issuing http-01 and tls-alpn-01 challenges. This may lead to these requests being sent to local network targets, potentially leading to information disclosure. Fixed in Vault Community Edition 2.0.0 and Vault Enterprise 2.0.0, 1.21.5, 1.20.10, and 1.19.16.

Affected Software

7 affected components
HashiCorp Vault Community Edition<2.0.0
HashiCorp Vault Enterprise<2.0.0, <1.21.5, <1.20.10, <1.19.16
go/github.com/hashicorp/vault>=1.14.0<=1.21.4
HashiCorp Vault>=1.14.0<1.19.16
HashiCorp Vault>=1.14.0<2.0.0
HashiCorp Vault>=1.20.0<1.20.10
HashiCorp Vault>=1.21.0<1.21.5

Event History

Apr 17, 2026
CVE Published
via MITRE·02:55 AM
Data Sourced
via MITRE·02:55 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:16 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:16 AM
Affected Software
Advisory Published
via GitHub·06:31 AM
Data Sourced
via GitHub·06:31 AM
DescriptionSeverityWeaknessAffected Software
Jul 26, 58290
Event
via NVD·03:03 AM
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-2026-5052?

CVE-2026-5052 is considered a high-severity vulnerability due to the potential for server-side request forgery attacks.

2

How do I fix CVE-2026-5052?

To fix CVE-2026-5052, upgrade to Vault version 2.0.0 or later, or apply any available patches recommended by HashiCorp.

3

Which versions of Vault are affected by CVE-2026-5052?

Vault Community Edition versions prior to 2.0.0 and Vault Enterprise versions up to 2.0.0, 1.21.5, 1.20.10, and 1.19.16 are affected by CVE-2026-5052.

4

What are the potential impacts of CVE-2026-5052?

The potential impacts of CVE-2026-5052 include exposing local network targets to unauthorized requests through server-side request forgery.

5

Who is responsible for addressing CVE-2026-5052?

The responsibility for addressing CVE-2026-5052 lies with administrators of affected Vault installations, who should implement recommended updates.

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