EUVD-2026-23344
GHSA-8r5m-3f66-qpr3
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
6DescriptionCVE.org
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.
AnalysisAI
Server-side request forgery (SSRF) in HashiCorp Vault's PKI engine ACME validation allows unauthenticated remote attackers to send http-01 and tls-alpn-01 challenge requests to local network targets by controlling DNS responses, potentially disclosing sensitive information from internal services. The vulnerability affects Vault Community Edition before 2.0.0 and Vault Enterprise before 1.19.16, 1.20.10, or 1.21.5. HashiCorp has released patched versions; no public exploit code has been identified at the time of analysis.
Technical ContextAI
HashiCorp Vault's PKI (Public Key Infrastructure) engine implements ACME (Automated Certificate Management Environment) challenge validation as specified in RFC 8555. The http-01 and tls-alpn-01 challenge types require the server to validate control of a domain by connecting to the subject domain at specified ports (typically 80 for http-01 and 443 for tls-alpn-01). The vulnerability stems from CWE-918 (Server-Side Request Forgery), where the ACME validation logic fails to reject challenge requests that resolve to private/local network addresses (RFC 1918 ranges, loopback, link-local, multicast). By controlling DNS responses (through DNS hijacking, cache poisoning, or rogue authoritative servers), an attacker can cause Vault to send ACME challenge validation requests to internal network targets instead of public-facing infrastructure, enabling reconnaissance and information disclosure from services not directly accessible externally.
RemediationAI
Upgrade to Vault Community Edition 2.0.0 or later, or Vault Enterprise to version 1.19.16, 1.20.10, 1.21.5, or later, as specified in the HashiCorp advisory. If immediate upgrade is not feasible, restrict network access to Vault's ACME endpoints by implementing firewall rules or reverse-proxy ACLs that limit ACME requests to trusted certificate management systems and clients. Additionally, monitor and log all ACME challenge validation requests (including destination IP and hostname) to detect suspicious outbound connections to private network ranges. Disable the PKI engine's ACME feature entirely if not in use. Implement DNS security controls such as DNSSEC validation, DNS query logging, and isolation of Vault's DNS resolver from untrusted networks to mitigate DNS hijacking attacks that could redirect challenge validation to local targets. Be aware that blocking private IP ranges at the firewall level will prevent legitimate use cases where ACME validation must reach internal services; evaluate your certificate issuance workflow before applying this control.
Credential-harvesting malware compromised 84 versions of 42 TanStack npm packages on 2026-05-11 via chained GitHub Actio
Unauthenticated remote attackers can trigger complete database overwrites, server-side file reads, and SSRF attacks agai
HashiCorp Terraform’s Vault Provider (terraform-provider-vault) did not correctly configure GCE-type bound labels for Va
An XML external entity (XXE) vulnerability in the Password Vault Web Access (PVWA) of CyberArk Enterprise Password Vault
PhotoRange Photo Vault 1.2 appends the password to the URI for authorization, which makes it easier for remote attackers
The REST API in CyberArk Password Vault Web Access before 9.9.5 and 10.x before 10.1 allows remote attackers to execute
Server-side request forgery in bank-vaults vault-secrets-webhook (<= 1.22.2) lets a low-privileged tenant with ConfigMap
Account takeover in self-hosted Bitwarden Server before 2026.6.0 lets a low-privileged organization member steal any oth
vault-cli is a configurable command-line interface tool (and python library) to interact with Hashicorp Vault. Rated cri
The SRP-6a implementation in Kee Vault KeePassRPC before 1.12.0 is missing validation for a client-provided parameter, w
The SRP-6a implementation in Kee Vault KeePassRPC before 1.12.0 generates insufficiently random numbers, which allows re
Server-side request forgery in the Ruby css_parser gem (< 3.0.0) lets a remote unauthenticated attacker force the parsin
Same weakness CWE-918 – Server-Side Request Forgery (SSRF)
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Important| Product | Status |
|---|---|
| SUSE Linux Enterprise Server 16.1 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.1 | Affected |
| SUSE Linux Enterprise Module for Package Hub 15 SP5 | Affected |
| SUSE Linux Enterprise Module for Package Hub 15 SP6 | Affected |
| openSUSE Leap 15.5 | Affected |
| openSUSE Leap 15.6 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today