Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.newCreate a CVE report
Check your stack
CVE-2026-92738

Expired Vault login MFA requests may remain redeemable

Products / packages HashiCorp Vault · HashiCorp Vault Enterprise

Published

Share

Severity and exploitation

Not in CISA KEV

KEV coverage does not rule out exploitation.

KEV checked 14/11/2026, 22:45:30 UTC
HashiCorp · CVSS:3.1 · 6.8
Assessment vectorCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

Severity

medium6.8

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Not established by this record

Missing evidence does not mean no public exploit exists.

Remediation

Fix status not established

No structured fix or guidance is available here. Check the latest publisher advisory.

What this means

HashiCorp Vault's Login MFA feature may not enforce the lifetime of pending requests, allowing users to complete MFA after the request should have expired. This affects Vault versions before 2.2.2, 1.21.14, and 1.19.26. An attacker with previous authentication factor completion may obtain a Vault token.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Attack conditions

No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

HashiCorp · HashiCorp

Vault

1 range
HashiCorp version evidence
Platforms: 64 bit, 32 bit, x86, ARM, MacOS, Windows, Linux

Compare with this publisher’s ranges. This does not inspect your installation.

affected

1.10.0 → before 2.2.2

semver versions

unaffected

unknown

Other versions: unaffected

HashiCorp · HashiCorp

Vault Enterprise

1 range
HashiCorp version evidence
Platforms: 64 bit, 32 bit, x86, ARM, MacOS, Windows, Linux

Compare with this publisher’s ranges. This does not inspect your installation.

affected

1.10.0 → before 2.2.2

semver versions

From 1.19.26: unaffected

From 1.20.0: affected

From 1.21.14: unaffected

From 2.0.0: affected

unaffected

unknown

Other versions: unaffected

Automatic dependency matching is unavailable for this record. Use the product evidence and publisher’s instructions to check your installation.

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

No structured fix or remediation guidance is available here. Check the full source description and vendor’s latest advisory for a patch or workaround; do not assume another version is safe.

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.

Original source description

Read the full publisher description

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.

References

1 sources
discuss.hashicorp.com/t/hcsec-2026-59-expired-vault-login-mfa-requests-may-remain-redeemable/78257
Source referenceHashiCorp

Inside the record

Evidence available

Package identity · not supplied
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-92738

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-613 ↗

CWE-613: Insufficient Session Expiration

HashiCorp

Related →
Contributing organizations · 2
HashiCorp

Assigning organization

2026-11-13
CISA-ADP

Additional data publisher

2026-11-13

Timeline

All times UTC

  1. Advisory published

    Publication date supplied by the source.

  2. Source updated

    Latest modification date supplied by the source.

  3. Last imported by cve.new

    Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes
  1. CVE · CVE-2026-92738

    Observed 2026-11-13T21:42:21.402Z · upstream updated 2026-11-13T21:09:35.483Z

    Prioritization updated

    before

    []

    after

    [
  {
    "source": "CISA-ADP",
    "type": "SSVC",
    "role": "CISA Coordinator",
    "timestamp": "2026-11-13T21:09:27.624686Z",
    "decisions": [
      {
        "name": "Exploitation",
        "value": "none"
      },
      {
        "name": "Automatable",
        "value": "no"
      },
      {
        "name": "Technical Impact",
        "value": "total"
      }
    ]
  }
]

Large field values are marked as truncated previews. Original source snapshots remain retained.

Showing up to 50 most recent observed changes.