CVE-2026-5052

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

HIGH
8.6
CVSS Score
Published: April 17, 2026 at 02:55 AM UTC
Updated: June 17, 2026 at 10:58 AM UTC
1 product affected across 1 vendorVault

Using Vault by HashiCorp?

Get instant alerts when new vulnerabilities affect Vault - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.6
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

1.14.0 ≤ v < 1.19.161.14.0 ≤ v < 2.0.01.15.0 ≤ v < 2.0.01.20.0 ≤ v < 1.20.101.21.0 ≤ v < 1.21.51.15.0
Affected range stops below 2.0.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
CHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-918

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card