CVE-2026-92735: 
HashiCorp Vault vulnerability analysis and mitigation

Overview

CVE-2026-92735 is a Server-Side Request Forgery (SSRF) vulnerability in HashiCorp Vault and Vault Enterprise affecting the integrated storage join process. An unauthenticated attacker with network access to a new, uninitialized Vault node can cause that node to send server environment credentials to an attacker-controlled server. Affected versions span from 1.2.0 up to (but not including) 2.2.2 for both Vault Community Edition and Vault Enterprise. The vulnerability was published on November 13, 2026, and carries a CVSS v3.1 base score of 5.9 (Medium) (GitHub Advisory).

Technical details

The vulnerability is classified as CWE-918 (Server-Side Request Forgery) and is rooted in the integrated storage (Raft) join process, which fails to sufficiently validate or restrict outbound connections initiated during node initialization. An unauthenticated attacker who can reach a new, uninitialized Vault node over the network can manipulate the join process to redirect the node's credential-bearing requests to an attacker-controlled server, thereby disclosing server environment credentials. Exploitation requires high attack complexity — specifically, the target node must be in an uninitialized state — and no privileges or user interaction are needed (GitHub Advisory, HashiCorp Advisory).

Impact

Successful exploitation results in the disclosure of server environment credentials (e.g., cloud provider credentials, tokens, or other secrets present in the node's environment) to an attacker-controlled server, representing a high confidentiality impact. There is no integrity or availability impact. Exposed credentials could enable an attacker to pivot into cloud infrastructure, access other services, or escalate privileges within the environment where Vault is deployed (GitHub Advisory, HashiCorp Advisory).

Exploitability

There is no public proof-of-concept exploit and no evidence of in-the-wild exploitation at the time of disclosure (GitHub Advisory). The EPSS score is 0.0, reflecting a very low current probability of exploitation. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation is constrained by the requirement that the target node must be newly deployed and uninitialized, limiting the attack window.

Exploitation steps

  1. Reconnaissance: Identify newly deployed, uninitialized HashiCorp Vault nodes (versions 1.2.0–2.2.2) exposed on the network, particularly during infrastructure provisioning or scaling events.
  2. Set up attacker-controlled server: Stand up a server capable of receiving HTTP/HTTPS requests and logging all incoming headers, bodies, and credentials.
  3. Intercept or influence the join process: Position the attacker-controlled server to respond to or redirect the Vault node's integrated storage (Raft) join requests, exploiting the lack of destination validation in the join process.
  4. Receive disclosed credentials: The uninitialized Vault node sends its server environment credentials (e.g., cloud IAM tokens, environment variable secrets) to the attacker-controlled server as part of the manipulated join process.
  5. Leverage obtained credentials: Use the captured credentials to authenticate to cloud providers or other services, enabling lateral movement or privilege escalation within the target environment (HashiCorp Advisory, GitHub Advisory).

Indicators of compromise

  • Network: Unexpected outbound connections from a Vault node to unknown external IP addresses during the initialization/join phase; Raft join requests directed to non-cluster IP addresses.
  • Logs: Vault audit logs or system logs showing join attempts to unexpected or external endpoints during node startup; errors or anomalies in integrated storage join logs.
  • Process/Environment: Evidence of environment variable access or credential retrieval during the Vault initialization sequence outside of normal operational patterns.
  • Cloud Provider Logs: Unexpected API calls or authentication events using Vault server credentials from IP addresses not associated with the Vault cluster (HashiCorp Advisory).

Mitigation and workarounds

HashiCorp has released patches addressing this vulnerability: upgrade to Vault Community Edition 2.2.2 or Vault Enterprise 2.2.2, 1.21.14, or 1.19.25. As a workaround prior to patching, restrict network access to new, uninitialized Vault nodes during deployment so that only trusted cluster members can reach the join endpoint. Ensure that Vault nodes complete their initialization process in a controlled, network-isolated environment before being exposed to broader network access (HashiCorp Advisory, GitHub Advisory).

Additional resources


Source: This report was generated using AI

Related HashiCorp Vault vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-92738MEDIUM6.8
  • HashiCorp Vault logoHashiCorp Vault
  • cpe:2.3:a:hashicorp:vault
NoYesNov 13, 2026
CVE-2026-128100MEDIUM6.5
  • HashiCorp Vault logoHashiCorp Vault
  • cpe:2.3:a:hashicorp:vault
NoYesNov 13, 2026
CVE-2026-93335MEDIUM6.5
  • HashiCorp Vault logoHashiCorp Vault
  • cpe:2.3:a:hashicorp:vault
NoYesNov 13, 2026
CVE-2026-92735MEDIUM5.9
  • HashiCorp Vault logoHashiCorp Vault
  • cpe:2.3:a:hashicorp:vault
NoYesNov 13, 2026
CVE-2026-93333LOW2.7
  • HashiCorp Vault logoHashiCorp Vault
  • cpe:2.3:a:hashicorp:vault
NoYesNov 13, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management