Kvv2 — CraftedSignal Threat Feedhttps://feed.craftedsignal.io/tags/kvv2/Trending threats, MITRE ATT&CK coverage, and detection metadata — refreshed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioFri, 17 Apr 2026 04:16:03 +0000Vault kvv2 Policy Bypass Vulnerability Leading to Denial-of-Service (CVE-2026-3605)https://feed.craftedsignal.io/briefs/2026-04-vault-kvv2-dos/Fri, 17 Apr 2026 04:16:03 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-04-vault-kvv2-dos/An authenticated user with access to a kvv2 path through a policy containing a glob may be able to delete secrets they were not authorized to read or write, resulting in denial-of-service, addressed in Vault versions 2.0.0, 1.21.5, 1.20.10, and 1.19.16.CVE-2026-3605 is a vulnerability in HashiCorp Vault’s kvv2 secrets engine where an authenticated user can delete secrets they lack read/write authorization for, leading to a denial-of-service. This occurs when a policy associated with the user contains a glob allowing access to a kvv2 path. The vulnerability does not permit cross-namespace secret deletion or unauthorized data reading. This issue impacts Vault Community Edition and Vault Enterprise. Affected versions include all releases prior to the fixes in Vault Community Edition 2.0.0 and Vault Enterprise 2.0.0, 1.21.5, 1.20.10, and 1.19.16. Successful exploitation allows an attacker to disrupt applications relying on the deleted secrets.

Attack Chain

  1. An attacker obtains valid credentials for a Vault user account.
  2. The attacker identifies a kvv2 secrets path protected by a policy containing a glob (e.g., secret/data/*).
  3. The attacker authenticates to Vault using their credentials via the Vault CLI or API (vault login -method=...).
  4. The attacker uses the Vault CLI or API to attempt to delete a secret within the globbed path (vault kv delete secret/data/unauthorized-secret).
  5. Due to the policy misconfiguration, the delete operation succeeds, even though the attacker lacks explicit read or write permissions for the specific secret.
  6. The target secret is removed from the Vault backend.
  7. Applications or services relying on the deleted secret experience failures or unexpected behavior.
  8. Repeated secret deletion leads to widespread application disruption, resulting in a denial-of-service.

Impact

Successful exploitation of CVE-2026-3605 allows an authenticated user to cause a denial-of-service by deleting secrets they are not authorized to manage. While the vulnerability does not allow unauthorized data access or cross-namespace deletion, the impact can be significant for organizations relying on Vault for secrets management. The number of affected systems depends on the scope of the vulnerable policy and the attacker’s access. The primary impact is application downtime and potential data loss due to deleted secrets.

Recommendation

  • Upgrade Vault Community Edition and Vault Enterprise to versions 2.0.0, 1.21.5, 1.20.10, or 1.19.16 to patch CVE-2026-3605.
  • Review and revise Vault policies containing globs (secret/data/*) to ensure appropriate least-privilege access control and prevent unauthorized deletion, referencing the vulnerability description in this brief.
  • Monitor Vault audit logs for secret/delete operations performed by users with policies containing broad globs, using the provided Sigma rule for guidance.
  • Implement regular backups of Vault secrets to mitigate the impact of accidental or malicious deletion, in case this vulnerability is exploited.
]]>mediumadvisoryvaultkvv2denial-of-servicecve-2026-3605