Vault unauth denial-of-service blocks admin (CVE-2026-5807)
CVE-2026-5807
Vault is vulnerable to a denial-of-service condition where an unauthenticated attacker can repeatedly initiate or cancel root token generation or rekey operations, occupying the single in-progress ope...
Overview
A high-severity vulnerability in HashiCorp Vault allows an unauthenticated attacker on the network to cause a denial-of-service condition for critical administrative workflows. Tracked as CVE-2026-5807, this flaw has been addressed in the latest release.
Vulnerability Details
Vault manages sensitive root token generation and cryptographic rekeying operations through a single, system-wide slot for in-progress actions. The vulnerability allows any network-connected entity, without providing any credentials, to repeatedly initiate and then immediately cancel these operations. By doing so, an attacker can monopolize this single slot indefinitely, creating a permanent lockout for legitimate administrators.
Impact
The primary impact is a complete denial-of-service for two vital security procedures: generating new root tokens and performing cryptographic rekey operations. This prevents administrators from rotating master keys or recovering access via root tokens, which can halt security maintenance and disaster recovery efforts. The attack requires no authentication (Privileges Required: NONE) and no user interaction, making it simple to execute. The CVSS v3.1 base score is 7.5 (High).
Affected Products and Remediation
This vulnerability affects versions of HashiCorp Vault prior to 2.0.0.
The fix is to upgrade immediately.
- Upgrade Vault Community Edition to version 2.0.0 or later.
- Upgrade Vault Enterprise to version 2.0.0 or later.
There are no supported workarounds or configuration changes to mitigate this vulnerability. The only complete remediation is applying the patch. After upgrading, no further action is required.
Security Insight
This vulnerability highlights a recurring theme in security design: the risks of single-threaded or singleton resource management for critical functions without proper rate-limiting or authorization checks. Similar to past DoS flaws in other systems, it shows how a seemingly minor architectural constraint-a single operation slot-can be exploited to create a significant operational blockade. It serves as a reminder to audit administrative APIs for both authentication and logical availability guarantees. For the latest on security incidents and vulnerabilities, monitor our security news feed.
Further Reading
Never miss a critical vulnerability
Get real-time security alerts delivered to your preferred platform.
Related Advisories
OpenClaw before 2026.3.13 reads and buffers Telegram webhook request bodies before validating the x-telegram-bot-api-secret-token header, allowing unauthenticated attackers to exhaust server resources...
IBM i 7.6 could allow a remote attacker to cause a denial of service using failed authentication connections due to improper allocation of resources....
A vulnerability in the Remote Access SSL VPN functionality of Cisco Secure Firewall Adaptive Security Appliance (ASA) Software and Secure Firewall Threat Defense (FTD) Software could allow an unauthen...
joserfc is a Python library that provides an implementation of several JSON Object Signing and Encryption (JOSE) standards. In 1.6.2 and earlier, a resource exhaustion vulnerability in joserfc allows ...