Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-5052: CWE-918: Server-Side Request Forgery (SSRF) in HashiCorp Vault

0
Medium
VulnerabilityCVE-2026-5052cvecve-2026-5052cwe-918
Published: Fri Apr 17 2026 (04/17/2026, 02:55:25 UTC)
Source: CVE Database V5
Vendor/Project: HashiCorp
Product: Vault

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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/17/2026, 11:06:50 UTC

Technical Analysis

The vulnerability CVE-2026-5052 in HashiCorp Vault's PKI engine relates to improper validation of ACME challenge targets. Specifically, the ACME validation process failed to reject local network addresses when issuing http-01 and tls-alpn-01 challenges. This allows an attacker to cause the Vault server to send requests to internal network targets, which may result in information disclosure. The vulnerability is classified as CWE-918 (Server-Side Request Forgery). It affects Vault version 1.15.0 and was addressed in subsequent releases including Vault Community Edition 2.0.0 and Vault Enterprise versions 2.0.0, 1.21.5, 1.20.10, and 1.19.16. The CVSS score of 5.3 reflects a medium impact primarily on confidentiality with no impact on integrity or availability.

Potential Impact

Successful exploitation of this SSRF vulnerability could lead to information disclosure by allowing unauthorized requests to internal network resources through the Vault server. There is no indication of impact on data integrity or availability. No known exploits have been reported in the wild.

Mitigation Recommendations

A fix for this vulnerability is available in Vault Community Edition 2.0.0 and Vault Enterprise versions 2.0.0, 1.21.5, 1.20.10, and 1.19.16. Users should upgrade to one of these fixed versions to remediate the vulnerability. Patch status is confirmed by the vendor advisory. No additional mitigation steps are indicated.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
HashiCorp
Date Reserved
2026-03-27T17:50:20.727Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 69e2142082d89c981fcd7c31

Added to database: 4/17/2026, 11:06:08 AM

Last enriched: 4/17/2026, 11:06:50 AM

Last updated: 4/17/2026, 5:26:48 PM

Views: 7

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses