Widely-used cloud orchestration infrastructure; bucket access risk could affect many tenants.
CVE-2025-66467
Policy cleanup bug lets former bucket owners access new buckets with same name.
Is CVE-2025-66467 being exploited?
Not confirmed. CVE-2025-66467 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.37% probability of exploitation in the next 30 days.
How severe is CVE-2025-66467?
CVE-2025-66467 is rated High with a CVSS score of 8.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-66467?
Yes. A fix has been recorded for CVE-2025-66467. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-66467 affect?
CVE-2025-66467 affects Apache CloudStack, MinIO. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2025-66467?
Upgrade to CloudStack 4.20.3.0+ or 4.22.0.1+ to fix.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Former bucket owners can read/write into a newly created bucket with the same name due to missing policy cleanup.
Patch when possible
- affected>= 4.19.0.0 and <= 4.20.2.0
- affected>= 4.21.0.0 and <= 4.22.0.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.