Skip to content

GHSA-fhc2-8qx8-6vj7 BIT-vault-2025-4656 CVE-2025-4656 GO-2025-3788

Vault Community Edition rekey and recovery key operations can cause denial of service

Low Go
Severity
3.1 / 10
Low · CVSS 3.1
Exploit chance (EPSS)
0.27%
Chance of exploitation in the next 30 days. Higher than 18.56% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-1088 Synchronous Access of Remote Resource without Timeout
Fix
1.20.0
Upgrade github.com/hashicorp/vault to this version or later

Description

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.

Affected versions

Go

PackageVulnerableFixed in
github.com/hashicorp/vault
>= 1.14.8, < 1.20.0
1.20.0

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

github.com/hashicorp/vault Go → 1.20.0

go
go get github.com/hashicorp/vault@v1.20.0 && go mod tidy

Severity breakdown

CVSS 3.1 3.1

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

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

Weakness

CWE-1088: Synchronous Access of Remote Resource without Timeout

The code has a synchronous call to a remote resource, but there is no timeout for the call, or the timeout is set to infinite.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-88v5-9hxc-f85r
HashiCorp Vault Vulnerable to Denial-of-Service via Unauthenticated Root Token Generation/Rekey Operations
High Also affects github.com/hashicorp/vault
GHSA-8r5m-3f66-qpr3
HashiCorp Vault has Server-Side Request Forgery in ACME Challenge Validation via Attacker-Controlled DNS
High Also affects github.com/hashicorp/vault
GHSA-72gw-fmmr-c4r4
HashiCorp Vault May Expose Tokens to Auth Plugins Due to Incorrect Header Sanitization
High Also affects github.com/hashicorp/vault
GHSA-m2w4-8ggf-rj47
HashiCorp Vault has a KVv2 Metadata and Secret Deletion Policy Bypass that leads to Denial-of-Service
High Also affects github.com/hashicorp/vault
GHSA-vp5w-xcfc-73wf
Hashicorp Vault and Vault Enterprise vulnerable to a denial of service when processing JSON
High Also affects github.com/hashicorp/vault
GHSA-9g4h-h484-3578
HashiCorp Vault and Vault Enterprise's AWS Auth method may be susceptible to authentication bypass
High Also affects github.com/hashicorp/vault
GHSA-8f82-53h8-2p34
HashiCorp Vault Community Edition Denial of Service Though Complex JSON Payloads
High Also affects github.com/hashicorp/vault
GHSA-7rx2-769v-hrwf
HashiCorp Vault ldap auth method may not have correctly enforced MFA
High Also affects github.com/hashicorp/vault
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor