HashiCorp Vault/Vault Enterprise up to 1.21.0 PKI Engine ACME Validation server-side request forgery

Summaryinfo

A vulnerability classified as critical has been found in HashiCorp Vault and Vault Enterprise. This impacts an unknown function of the component PKI Engine ACME Validation. Performing a manipulation results in server-side request forgery. This vulnerability was named CVE-2026-5052. The attack may be initiated remotely. There is no available exploit. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical has been found in HashiCorp Vault and Vault Enterprise. This affects some unknown processing of the component PKI Engine ACME Validation. The manipulation with an unknown input leads to a server-side request forgery vulnerability. CWE is classifying the issue as CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at discuss.hashicorp.com. This vulnerability is uniquely identified as CVE-2026-5052 since 03/27/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.

Upgrading to version 2.0.0 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• HashiCorp

Name

• Vault
• Vault Enterprise

Version

• 1.2.5
• 1.3.4
• 1.3.6
• 1.3.7
• 1.3.8
• 1.4.0
• 1.4.1
• 1.4.2
• 1.4.3
• 1.4.4
• 1.5.0
• 1.5.1
• 1.5.6
• 1.5.7
• 1.5.8
• 1.5.9
• 1.6.0
• 1.6.1
• 1.6.2
• 1.6.3
• 1.6.4
• 1.6.5
• 1.6.6
• 1.7.0
• 1.7.1
• 1.7.2
• 1.7.3
• 1.7.4
• 1.7.5
• 1.7.6
• 1.7.7
• 1.8.0
• 1.8.3
• 1.8.4
• 1.8.5
• 1.8.6
• 1.9.0
• 1.9.1
• 1.9.10
• 1.10.0
• 1.10.1
• 1.10.2
• 1.10.3
• 1.10.6
• 1.10.7
• 1.10.11
• 1.11.3
• 1.11.4
• 1.11.7
• 1.11.8
• 1.11.9
• 1.12.0
• 1.12.3
• 1.12.4
• 1.12.5
• 1.12.11
• 1.13.0
• 1.13.1
• 1.13.5
• 1.13.7
• 1.13.8
• 1.13.9
• 1.13.10
• 1.14.0
• 1.14.1
• 1.14.3
• 1.14.4
• 1.14.5
• 1.14.6
• 1.14.10
• 1.15
• 1.15.0
• 1.15.1
• 1.15.2
• 1.15.4
• 1.15.15
• 1.16.0
• 1.16.9
• 1.16.10
• 1.17.5
• 1.17.6
• 1.18.0
• 1.18.1
• 1.20.0
• 1.20.1
• 1.20.2
• 1.21.0

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion