Skip to content
Noroxi
CVE-2025-4656· NVD / CVE Program· CNA HashiCorp

Vault Vulnerable to Recovery Key Cancellation Denial of Service

Vault Community and Vault Enterprise rekey and recovery key operations can lead to a denial of service due to uncontrolled cancellation by a Vault operator. This vulnerability (CVE-2025-4656) has been remediated in Vault Community Edition 1.20.0 and Vault Enterprise 1.20.0, 1.19.6, 1.18.11, 1.17.17, and 1.16.22.

LowCVSS 3.1 · v3.1—No exploit Fix available
Published
Jun 25, 2025
Updated
Jun 17, 2026
EPSS
0.3% · 17th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

12

Monitor

Low priority for now.

CVSS
12 / 40 · 3.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · HashiCorp
3.1
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
hashicorpvault

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • hashicorp vault1.14.8 and later · before 1.16.22
  • hashicorp vault1.14.8 and later · before 1.20.0
  • hashicorp vault1.17.0 and later · before 1.17.17
  • hashicorp vault1.18.0 and later · before 1.18.11
  • hashicorp vault1.19.0 and later · before 1.19.6

Versions reported by the vendor

Affected version ranges reported by the assigning authority (HashiCorp). Independent of NVD's CPE analysis and usually ahead of it.

  • HashiCorp Vault

    • 1.14.8 and later · before 1.20.0affected · semver
  • HashiCorp Vault Enterprise

    • 1.14.8 and later · before 1.20.0affected · semverfixed in 1.19.6, 1.18.11, 1.17.17, 1.16.22

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gogithub.com/hashicorp/vaultfrom 1.14.8 · before 1.20.01.20.0
openSUSE:Tumbleweedgovulncheck-vulndbbefore 0.0.20250730T213748-1.10.0.20250730T213748-1.1
openSUSE:Tumbleweedopenbaobefore 2.3.1-1.12.3.1-1.1

Other highest-scoring records for the same primary product.

  • CVE-2020-35192The official vault docker images before 0.11.6 contain a blank password for a root user.
    40Plan
  • CVE-2024-2048Vault Cert Auth Method Did Not Correctly Validate Non-CA Certificates
    39Monitor
  • CVE-2020-12757HashiCorp Vault and Vault Enterprise 1.4.0 and 1.4.1, when configured with the GCP Secrets Engine, may incorrectly generate GCP Credentials
    39Monitor
  • CVE-2025-6000Arbitrary Remote Code Execution via Plugin Catalog Abuse
    36Monitor
  • CVE-2022-40186An issue was discovered in HashiCorp Vault and Vault Enterprise before 1.11.3.
    36Monitor
  • CVE-2022-36129HashiCorp Vault Enterprise 1.7.0 through 1.9.7, 1.10.4, and 1.11.0 clusters using Integrated Storage expose an unauthenticated API endpoint
    36Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
HashiCorp Vault1.20.0Vendor (CNA)
HashiCorp Vault Enterprise1.16.22Vendor (CNA)
HashiCorp Vault Enterprise1.17.17Vendor (CNA)
HashiCorp Vault Enterprise1.18.11Vendor (CNA)
HashiCorp Vault Enterprise1.19.6Vendor (CNA)
HashiCorp Vault Enterprise1.20.0Vendor (CNA)
Go:github.com/hashicorp/vault1.20.0Package registry (OSV)
opensuse:govulncheck-vulndb0.0.20250730T213748-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:openbao2.3.1-1.1 · openSUSE:TumbleweedPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
low · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
Low

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records