Threats Tagged 'cve-2026-66722'
View all threats tagged with 'cve-2026-66722'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'cve-2026-66722'
Click on any threat for detailed analysis and mitigation recommendations
Improper authorization for CRUD operations on Project Roles and Project Role permissions for domain admins in CloudStack. (CVE-2026-66722)CVE-2026-66722 0 A vulnerability in Apache CloudStack allows Domain Admins to improperly perform create, read, update, and delete (CRUD) operations on project roles and permissions across domains. The authorization check only verifies that the caller is a Domain Admin but does not confirm if the target project belongs to their domain or subdomain. This flaw affects versions from 4.15.0.0 through 4.20.3.0 and from 4.21.0.0 through 4.22.1.0. Fixed versions are 4.20.3.1 and 4.22.1.1 or later. Join the discussion | GCVE Database | 08/21/2026, 09:32:06 UTC Added: 08/21/2026, 14:22:26 UTC |
CVE-2026-66722: CWE-285 Improper Authorization in Apache Software Foundation Apache CloudStackCVE-2026-66722 0 CVE-2026-66722 is an improper authorization vulnerability in Apache CloudStack affecting domain admins. It allows a domain admin to create, update, delete, and list project roles and permissions across any domain, not limited to their own. This occurs because the authorization check only verifies the caller is a domain admin without confirming domain ownership of the target project. The issue affects Apache CloudStack versions from 4.15.0.0 through 4.20.3.0 and 4.21.0.0 through 4.22.1.0. Upgrading to versions 4.20.3.1 or 4.22.1.1 or later resolves the vulnerability. Join the discussion | CVE Database V5 | 08/21/2026, 08:22:36 UTC Added: 08/21/2026, 11:03:59 UTC |
Showing 1 to 2 of 2 results