dbcve.org
VaultApplication · Hashicorp

CVE-2025-6014

MEDIUM · 6.5 CVSS v3.1 Published 2025-08-01
Fix available
A fix is available. Upgrade to 1.16.23 / 1.18.12 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vault and Vault Enterprise’s (“Vault”) TOTP Secrets Engine code validation endpoint is susceptible to code reuse within its validity period. Fixed in Vault Community Edition 1.20.1 and Vault Enterprise 1.20.1, 1.19.7, 1.18.12, and 1.16.23.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Vault's TOTP Secrets Engine code validation endpoint permits code reuse within its validity period, allowing an attacker to reuse the same TOTP code multiple times during the standard 30-second window instead of requiring a new code each validation attempt.

MitigationUpgrade Vault to version 1.20.1 (Community) or 1.20.1/1.19.7/1.18.12/1.16.23 (Enterprise) to patch the vulnerable TOTP validation logic.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
VaultApplication
Affected:< 1.16.23< 1.20.1>= 1.17.0, < 1.18.12>= 1.19.0, < 1.19.7= 1.20.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Vault version
    Run 'vault version' to obtain the installed Vault version number
    Affected if The version is less than 1.16.23, 1.18.12, or 1.19.7; or is 1.20.0; or is between 1.20.0 (exclusive) and 1.20.1 (exclusive)
  2. Confirm TOTP secrets engine is enabled
    Run 'vault secrets list' to enumerate enabled secrets engines and look for entries of type 'totp'
    Affected if An enabled secrets engine with type 'totp' exists at any path (commonly 'totp/')
  3. Identify TOTP mount paths
    Run 'vault secrets list -format=json' and filter for mount_point where engine_type equals 'totp'
    Affected if Any mount_point returns 'totp' as the engine_type value
  4. Test TOTP code reuse behavior
    Generate a valid TOTP code using the mounted TOTP engine, then submit the same code to the validate endpoint multiple times within 30 seconds using the Vault API
    Affected if The same TOTP code is accepted on multiple validation attempts within its 30-second validity window

A user is affected if their Vault version falls within the vulnerable ranges AND the TOTP secrets engine is enabled and actively validating codes, allowing reuse of the same TOTP code within the 30-second window.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.16.23 / 1.18.12 / 1.19.7 or later
Fixed in 1.16.231.18.121.19.7
Interim mitigation

Upgrade Vault to version 1.20.1 (Community) or 1.20.1/1.19.7/1.18.12/1.16.23 (Enterprise) to patch the vulnerable TOTP validation logic.

Recommended fix High confidence

Vault 1.20.1 or later (or 1.19.7, 1.18.12, or 1.16.23 depending on your current minor version branch)

  1. 1. Review current Vault version using `vault version`
  2. 2. Schedule a maintenance window for the upgrade
  3. 3. Take a backup of Vault data directory and configuration files
  4. 4. For single-server deployments: stop Vault, replace binary with new version, restart Vault
  5. 5. For clustered deployments: follow rolling upgrade procedure - upgrade standby nodes first, then perform leadership transfer and upgrade primary
  6. 6. After upgrade, verify Vault is operational using `vault status`
  7. 7. Verify TOTP secrets engine functionality by reading a TOTP code
  8. 8. Review Vault audit logs for any errors
Caveat Standard Vault upgrade considerations apply - review breaking changes in Vault changelogs for your version jump; ensure client applications are compatible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vault Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6014 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-6014 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data