Skip to content
Fencer Vulns
medium 5.3

CVE-2026-5052 json

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

published 2026-04-17 6 mo ago modified 2026-10-26 13 d ago also BIT-vault-2026-5052 , EUVD-2026-23344 , GHSA-8r5m-3f66-qpr3 , GO-2026-5262

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 28%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitnami vault 2.0.0
  • HashiCorp Vault 2.0.0
  • HashiCorp Vault Enterprise 1.19.16, 1.20.10, 1.21.5, 2.0.0
  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-5052 updated cvss 5.8

Vault: Vault: Information disclosure via Server-Side Request Forgery in ACME challenge validation

  • Red Hat OpenShift Container Platform 4 openshift4/ose-installer-rhel9, openshift4/ose-baremetal-installer-rhel9 Red Hat Openshift Data Foundation 4 cephcsi-rhel8, cephcsi-rhel9, mcg-cli-rhel9, mcg-rhel8-operator, mcg-rhel9-operator, ocs4/cephcsi-rhel8, +5 more
    affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
6 mo ago

Exploit prediction

0.34% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
OSV 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/hashicorp/vault
>=1.14.0, <=1.21.4
>=1.14.0
 no fix listed
bitnami vault
>=0.10.0, <2.0.0
2.0.0

Affected products

  • HashiCorp Vault
  • HashiCorp Vault Enterprise

Classification

Weakness
  • CWE-918 Server-Side Request Forgery

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.