Is CVE-2026-5052 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-5052 being exploited in the wild.

How severe is CVE-2026-5052?

Medium severity, with a CVSS score of 5.3, published 17 April 2026.

Which products and versions are affected?

github.com/hashicorp/vault (Go) >= 1.14.0, <= 1.21.4, SEMVER:introduced=1.14.0, SEMVER:introduced=1.14.0,last_affected=1.21.4; HashiCorp Vault Community Edition 1.14.0 to 1.21.4; HashiCorp Vault Enterprise 1.14.0 to 1.21.4, 1.20.9, 1.19.15.

Is there a fix for CVE-2026-5052?

A patch was published on 2026-04-17: Fixes released in multiple versions Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-5052 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-5052?

Check whether you run github.com/hashicorp/vault (Go), HashiCorp Vault, HashiCorp Vault Community Edition or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-5052: HashiCorp Vault SSRF in PKI engine ACME validation

Q: Is there a fix for CVE-2026-5052?

A patch was published on 2026-04-17: Fixes released in multiple versions Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-5052 attacked?

It is attacked over the network, in a hosted service.

Q: Am I affected by CVE-2026-5052?

Check whether you run github.com/hashicorp/vault (Go), HashiCorp Vault, HashiCorp Vault Community Edition or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-5052 · Severity: medium · CVSS 5.3 · Published 2026-04-17

HashiCorp Vault, a tool for managing sensitive secrets and certificates, contains a flaw in how it validates requests during automated certificate issuance. An attacker could potentially trick the system into sending requests to internal network services that should not be accessible from the outside. This could lead to the exposure of sensitive internal information or details about the private network infrastructure.

Technologies: github.com/hashicorp/vault (Go), HashiCorp Vault, HashiCorp Vault Enterprise. Vendors: Go, HashiCorp.

Quick answers

Is CVE-2026-5052 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-5052 being exploited in the wild.
How severe is CVE-2026-5052?: Medium severity, with a CVSS score of 5.3, published 17 April 2026.
Which products and versions are affected?: github.com/hashicorp/vault (Go) >= 1.14.0, <= 1.21.4, SEMVER:introduced=1.14.0, SEMVER:introduced=1.14.0,last_affected=1.21.4; HashiCorp Vault Community Edition 1.14.0 to 1.21.4; HashiCorp Vault Enterprise 1.14.0 to 1.21.4, 1.20.9, 1.19.15.
Is there a fix for CVE-2026-5052?: A patch was published on 2026-04-17: Fixes released in multiple versions Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-5052 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-5052?: Check whether you run github.com/hashicorp/vault (Go), HashiCorp Vault, HashiCorp Vault Community Edition or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A Server-Side Request Forgery (SSRF) vulnerability exists in the HashiCorp Vault PKI engine's ACME implementation. The root cause is a failure to reject local or internal network targets when performing http-01 and tls-alpn-01 challenge validations. By controlling DNS responses for a domain undergoing ACME validation, a remote attacker can redirect Vault's validation requests to internal IP addresses. Depending on configuration, the challenge endpoint may be unauthenticated or require an External Account Binding (EAB) token. This can result in unauthorized information disclosure from internal services. The issue is fixed in Vault Community Edition 2.0.0 and Vault Enterprise versions 2.0.0, 1.21.5, 1.20.10, and 1.19.16.

Affected products

HashiCorp Vault Community Edition 1.14.0 to 1.21.4
HashiCorp Vault Enterprise 1.14.0 to 1.21.4, 1.20.9, 1.19.15

Identifiers

CVE-2026-5052
GHSA-8r5m-3f66-qpr3
GO-2026-5262

Timeline

2026-04-16: disclosed: Initial publication date by HashiCorp
2026-04-17: advisory: GitHub and NVD advisory publication
2026-04-17: patched: Fixes released in multiple versions

References

https://discuss.hashicorp.com/t/hcsec-2026-06-vault-vulnerable-to-server-side-request-forgery-in-acme-challenge-validation-via-attacker-controlled-dns/77343

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.