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

Overview

CVE-2026-92738 is an insufficient session expiration vulnerability in HashiCorp Vault's Login MFA feature that allows a user who previously completed the first authentication factor to complete MFA and obtain a valid Vault token after the pending request should have expired — including after the user's primary credential has been rotated or revoked. It affects HashiCorp Vault (Community Edition) and Vault Enterprise versions 1.10.0 through 2.2.2 (exclusive). The vulnerability was published on November 13, 2026, and carries a CVSS v3.1 base score of 6.8 (Medium) (GitHub Advisory, HashiCorp Advisory).

Technical details

The root cause is classified as CWE-613 (Insufficient Session Expiration): Vault's Login MFA subsystem does not consistently enforce the expiration lifetime of pending two-phase login requests. When a user initiates a login and completes the first authentication factor, a pending MFA request is created with an intended expiration window. Due to the inconsistent enforcement, this pending request may remain redeemable beyond its intended lifetime, allowing the second factor to be completed and a Vault token to be issued even after the request should have been invalidated — including scenarios where the user's primary credential has since been rotated. The attack requires network access and low-level privileges (the attacker must have previously completed the first authentication factor), and exploitation complexity is rated High (GitHub Advisory, HashiCorp Advisory).

Impact

Successful exploitation allows an attacker to obtain a valid Vault token after their pending MFA request should have expired, effectively bypassing the intended session lifecycle controls. This is particularly dangerous in credential rotation scenarios: if an administrator rotates or revokes a user's primary credentials in response to a suspected compromise, the attacker may still complete the stale MFA request and gain authenticated access to Vault. The confidentiality and integrity impacts are rated High, as a valid Vault token can be used to access secrets, policies, and other sensitive resources managed by the Vault instance (GitHub Advisory).

Exploitability

There is no public proof-of-concept exploit code and no evidence of in-the-wild exploitation at the time of disclosure. The EPSS score is 0.0, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation is not automatable and requires the attacker to have previously completed the first authentication factor, limiting the attack surface to users with at least partial prior access (GitHub Advisory, HashiCorp Advisory).

Exploitation steps

  1. Initial Access: The attacker initiates a Vault login using valid primary credentials (first authentication factor), generating a pending two-phase MFA login request in the Vault system.
  2. Delay or Interruption: The attacker deliberately delays completing the second factor (MFA), allowing the pending request's intended expiration window to pass, or waits until the primary credential is rotated or revoked by an administrator.
  3. Exploit Expired Request: Due to the inconsistent expiration enforcement, the attacker submits the MFA response (second factor) after the request should have expired, using the original pending request identifier.
  4. Token Issuance: Vault incorrectly accepts the late MFA completion and issues a valid Vault token to the attacker, granting authenticated access to secrets and resources despite the expired or revoked credential state.
  5. Post-Exploitation: The attacker uses the obtained Vault token to access sensitive secrets, credentials, or policies stored in Vault, potentially enabling lateral movement within the environment (GitHub Advisory, HashiCorp Advisory).

Indicators of compromise

  • Logs: Vault audit logs showing MFA login completions (login events with MFA method) occurring significantly after the initial first-factor authentication timestamp — particularly where the elapsed time exceeds the configured MFA request TTL.
  • Logs: Vault token issuance events for users whose primary credentials were rotated or revoked prior to the MFA completion timestamp.
  • Logs: Audit log entries showing Vault token activity from accounts that were recently disabled or had credentials rotated, indicating a stale MFA request was redeemed.
  • Network: Vault API calls to MFA login completion endpoints (e.g., /v1/auth/mfa/validate) arriving well after the corresponding first-factor request, especially from the same source IP as the original login attempt.

Mitigation and workarounds

HashiCorp has released patches addressing this vulnerability. Users should upgrade to Vault Community Edition 2.2.2 or Vault Enterprise 2.2.2, 1.21.14, or 1.19.26. As an interim measure, administrators should monitor MFA completion audit logs for tokens issued after expected credential rotation or revocation events, and enforce stricter MFA request timeout policies where configurable. Credential rotation should be followed by explicit review of any pending MFA requests to ensure they are invalidated (GitHub Advisory, HashiCorp 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