CVE-2025-4656
Hashicorp Vault 1.14.8 – 1.16.22
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:LSummary
CVE-2025-4656 is a low-severity Synchronous Access of Remote Resource without Timeout (CWE-1088) vulnerability in Hashicorp Vault. Its CVSS base score is 3.1 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 14th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-10 (Network Disconnect) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-28064
Vulnerability Data
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,…
more
1.19.6, 1.18.11, 1.17.17, and 1.16.22.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
SC-10 requires terminating network connections after a defined period, directly enforcing timeouts on remote synchronous calls.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect missing timeouts, providing partial coverage of both the weakness and the control.
Redundancy and failover mechanisms can mitigate the impact of a hung synchronous call but do not enforce timeouts.
Network security controls can include connection-timeout policies, yet the weakness is a coding-level omission.
Secure SDLC practices require timeout handling for external calls, directly addressing the missing timeout.
Application security requirements typically mandate timeout settings for remote resource access.
Secure architecture principles encourage defensive coding patterns such as timeouts, but do not prescribe them explicitly.