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. This vulnerability did not allow a malicious user to delete secrets across namespaces, nor read any secret data. Fxed in Vault Community Edition 2.0.0 and Vault Enterprise 2.0.0, 1.21.5, 1.20.10, and 1.19.16.
Weakness
The product requires authentication, but the product has an alternate path or channel that does not require authentication.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Vault | Hashicorp | 0.10.0 (including) | 1.19.16 (excluding) |
| Vault | Hashicorp | 0.10.0 (including) | 2.0.0 (excluding) |
| Vault | Hashicorp | 1.20.0 (including) | 1.20.10 (excluding) |
| Vault | Hashicorp | 1.21.0 (including) | 1.21.5 (excluding) |
Potential Mitigations
Related Attack Patterns
References
- https://discuss.hashicorp.com/t/hcsec-2026-05-vault-kvv2-metadata-and-secret-deletion-policy-bypass-denial-of-service/77342
- https://access.redhat.com/security/cve/CVE-2026-3605
- https://bugzilla.redhat.com/show_bug.cgi?id=2459105
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-3605.json