HashiCorp Vault Login MFA accepts expired login requests
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- High
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-613.
Summary
HashiCorp Vault from 1.10.0 before 2.2.2 and Vault Enterprise from 1.10.0 before 2.2.2 do not consistently enforce the lifetime of pending two-phase login requests in the Login MFA feature. A user who completed the first authentication factor can finish MFA and obtain a Vault token after the request should have expired, even after the primary credential has been rotated. The flaw is classified as CWE-613 (insufficient session expiration). A network attacker with low privileges can exploit it, though the attack is hard to carry out.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
Description from the CNA
Vault's Login MFA feature did not consistently enforce the lifetime of pending two-phase login requests. This may allow a user who previously completed the first authentication factor to complete MFA and obtain a Vault token after the pending request should have expired, including after the user's primary credential has been rotated. This vulnerability (CVE-2026-92738) is fixed in Vault Community Edition 2.2.2 and Vault Enterprise 2.2.2, 1.21.14, and 1.19.26.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
Remediation
Upgrade Vault Community Edition to 2.2.2. Upgrade Vault Enterprise to 2.2.2, 1.21.14, or 1.19.26.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
- Fix · CNA Vault (HashiCorp) Fixed in 2.2.2
- Fix · CNA Vault Enterprise (HashiCorp) Fixed in 2.2.2
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
HashiCorp Vault, Vault Enterprise 2.2.2
2 records Highest priority Priority LOW 2 LOW
Other records, highest priority first
- TI-2026-91773 Case variant user and group names bypass Vault ACL deny rulesPriority LOW 29
Timeline
- 2026-11-13 Threatist record created from CVE-2026-92738
- 2026-11-13 Alias added: GHSA-w8f3-r2q9-xr6w
References
More HashiCorp vulnerabilities
- TI-2024-01904 Vault Cert Auth Method Did Not Correctly Validate Non-CA Certificates CVSS 3.1CRITICAL 9.8
- TI-2021-18437 HashiCorp Consul Enterprise before 1.8.17, 1.9.x before 1.9.11, and 1.10.x before 1.10.4… CVSS 3.1HIGH 8.8
- TI-2026-06570 Nomad vulnerable to path traversal in dynamic host volume which may lead to code execution CVSS 3.1HIGH 8.8
- TI-2020-17753 The official Consul Docker images 0.7.1 through 1.4.2 contain a blank password for a root… CVSS 3.1CRITICAL 9.8
- TI-2026-13641 consul-mcp-server vulnerable to cross-tenant credential reuse in streamable-HTTP stateless mode CVSS 3.1CRITICAL 10.0
- TI-2026-13778 terraform-mcp-server vulnerable to cross-tenant credential reuse in streamable-HTTP stateless mode CVSS 3.1CRITICAL 10.0
Sources
- CVE-2026-92738 · CVE Program
- CVE-2026-92738 · NVD
- FIRST EPSS
- GHSA-w8f3-r2q9-xr6w · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences