CloudstackApplication · Apache
CVE-2025-66467
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMissing 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceApache CloudStack fails to remove MinIO policies when buckets are deleted. Users retain valid access/secret keys after bucket deletion, and if another user creates a bucket with the same name, the original owner can use their old credentials to gain unauthorized read/write access to the new bucket.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
CloudstackApplication
>= 4.19.0.0, < 4.20.3.0>= 4.21.0.0, < 4.22.0.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Apache CloudStack versionLocate the CloudStack management server version file or check the UI/CLI for the version number. Common locations: /etc/cloudstack-release, management server logs, or admin UI dashboard.Affected if The installed version falls within >= 4.19.0.0 and < 4.20.3.0, OR >= 4.21.0.0 and < 4.22.0.1
-
Confirm MinIO is the object storage providerCheck the CloudStack configuration for the secondary storage or object storage settings. Look for MinIO-specific configuration in the CloudStack database or configuration files.Affected if MinIO is configured as the object storage backend for CloudStack
-
Identify orphaned MinIO policiesQuery the MinIO IAM system for policies associated with deleted buckets. List all MinIO user policies and compare against active CloudStack bucket records in the database. Look for policies referencing bucket names that no longer exist in CloudStack.Affected if MinIO policies exist for buckets that have been deleted from CloudStack but the policies remain
-
Check for stale credentialsReview CloudStack user access keys and secret keys in the CloudStack database or IAM system. Identify keys associated with deleted buckets that should no longer be valid.Affected if User credentials exist and remain active for buckets that have been deleted
A user is affected if CloudStack version is within the vulnerable range AND MinIO is used as storage AND orphaned policies or stale credentials exist from previously deleted buckets.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.20.3.04.22.0.1
Upgrade Apache CloudStack to version 4.20.3.0 or 4.22.0.1 or later to ensure MinIO policies are properly cleaned up when buckets are deleted.
4.20.3.0 (for 4.19.x branches) or 4.22.0.1 (for 4.21.x branches)
- 1. Create a complete backup of your current Apache CloudStack installation and database
- 2. For CloudStack versions >= 4.19.0.0 and < 4.20.3.0: upgrade to version 4.20.3.0
- 3. For CloudStack versions >= 4.21.0.0 and < 4.22.0.1: upgrade to version 4.22.0.1
- 4. Verify the upgrade was successful by checking the CloudStack management server logs
- 5. Test bucket deletion to confirm MinIO policies are now properly cleaned up
- 6. Revoke any previously generated access/secret keys that may have been associated with deleted buckets to prevent unauthorized access
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Cloudstack
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66467 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-66467 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data