Missing MinIO policy cleanup on bucket deletion via Apache CloudStack allows users to retain access to buckets which they previously owned. If another user creates a new bucket with the same name, the previous owners can gain unauthorized read and write access to it by using the previously generated access and secret keys. Users are recommended to upgrade to Apache CloudStack versions 4.20.3.0 or 4.22.0.1, or later, which fixes this issue.
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
CVE-2025-66467 is a critical access control vulnerability in Apache CloudStack that fails to properly clean up MinIO bucket policies when buckets are deleted. When a bucket is removed, the associated access and secret keys remain valid and retain their permissions. If another user subsequently creates a new bucket with the same name, the previous owner can exploit their still-valid credentials to gain unauthorized read and write access to the new bucket. This affects any organization using CloudStack with MinIO object storage backends, particularly those with multi-tenant environments where bucket name reuse is likely. The vulnerability is especially dangerous in regulated industries where data isolation is mandatory, as it enables cross-tenant data breaches and unauthorized data modification.
While this CVE doesn't map to specific MITRE ATT&CK techniques, practitioners using Casky.ai would benefit from skills that detect anomalous credential usage patterns and unauthorized access attempts. The underlying attack pattern involves Credential Access (obtaining valid keys that should be revoked) followed by Lateral Movement or Privilege Escalation (using those credentials to access resources they shouldn't). Casky's extended reasoning capabilities would help identify suspicious indicators such as: access key usage patterns that predate current bucket ownership, authentication succeeding with credentials from deleted resources, or unusual cross-tenant access patterns in CloudStack audit logs. Security teams should monitor for failed and succeeded authentication attempts using aged credentials, implement strict bucket naming conventions to prevent reuse, and audit all credentials associated with deleted buckets to ensure proper revocation across all services.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2025-66467. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation