
Cloud Vulnerability DB
A community-led vulnerabilities database
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).
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).
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).
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).
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./v1/auth/mfa/validate) arriving well after the corresponding first-factor request, especially from the same source IP as the original login attempt.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).
Source: This report was generated using AI
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."