CloudstackApplication · Apache
CVE-2025-66170
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 · uneditedThe CloudStack Backup plugin has an improper authorization logic in versions 4.21.0.0 and 4.22.0.0. Anyone with authenticated user-account access in CloudStack 4.21.0.0+ environments, where this plugin is enabled and has access to specific APIs can list backups from any account in the environment. This vulnerability does not allow them to see the contents of the backup. Users are recommended to upgrade to version 4.22.0.1, which fixes the 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 confidenceThe CloudStack Backup plugin versions 4.21.0.0 and 4.22.0.0 contain improper authorization logic that allows any authenticated user with access to specific APIs to list backups from any account in the environment, though it does not permit viewing backup contents.
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.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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 CloudStack management server versionLog into the CloudStack management server or UI and check the installed version. This is typically visible in the UI footer or via administrative commands like 'cloudmonkey' or API calls to 'listCapabilities'.Affected if The version is 4.21.0.0, 4.22.0.0, or any version >= 4.21.0.0 and < 4.22.0.1
-
Verify the Backup plugin is installed and enabledCheck the CloudStack plugins directory and confirm the Backup plugin is present and activated in the configuration. This is typically found in the plugins/ directory of the CloudStack installation and listed as enabled in the plugin configuration.Affected if The Backup plugin is installed and active in a vulnerable CloudStack version (4.21.0.0 to 4.22.0.0)
-
Confirm backup-related APIs are accessibleReview the API endpoint list and verify that backup-related API commands (such as 'listBackups' or similar backup listing commands) are available to authenticated users. The vulnerability allows any authenticated user access to these APIs.Affected if Backup listing APIs are exposed and accessible to standard authenticated users without role restrictions
You are affected if your CloudStack version is >= 4.21.0.0 and < 4.22.0.1 AND the Backup plugin is enabled and operational in your environment.
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.22.0.1
Upgrade the CloudStack Backup plugin to version 4.22.0.1 which contains the fix for the improper authorization vulnerability.
4.22.0.1
- Upgrade CloudStack from any version >= 4.21.0.0 and < 4.22.0.1 to version 4.22.0.1
- Follow the official CloudStack upgrade documentation for the upgrade process
- After upgrade, verify that the Backup plugin authorization is correctly enforced - users should only be able to list backups from their own account
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Cloudstack
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66170 — 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-66170 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