Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAccess CloudStack API
-
DeliveryEnumerate predictable Proxmox VM IDs
-
ExploitModify own VM's proxmox_vmid to victim's ID
-
ExecutionIssue VM control commands
-
PersistCloudStack executes against victim VM
-
ImpactAchieve cross-tenant control
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the target CloudStack deployment uses the Proxmox hypervisor extension - deployments using KVM, VMware, XenServer, or other hypervisors are not vulnerable. The attacker must have network access to the CloudStack API endpoint and either valid tenant credentials or exploit unauthenticated API access if misconfigured (CVSS vector indicates PR:N but typical IaaS platforms enforce authentication). The 'user.vm.denied.details' configuration parameter must NOT include 'proxmox_vmid' in its restriction list (default configuration allows user editing). Exploitation does NOT require administrative privileges, special hypervisor configurations, or user interaction. The vulnerability is limited to CloudStack 4.21.0.0 through 4.22.0.0 and does not affect earlier versions lacking the Proxmox extension or later patched versions. Cross-tenant isolation via network segmentation or firewalls does NOT prevent exploitation since the attack manipulates CloudStack's control plane, not data plane network traffic. |
| Impact | Real-world risk is CRITICAL for multi-tenant CloudStack deployments using the Proxmox extension. The CVSS 9.1 score accurately reflects severity: network attack vector (AV:N), low complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), with high confidentiality and integrity impact. The S:U (unchanged scope) understates the cross-tenant boundary violation, which in practice represents a catastrophic multi-tenancy failure. EPSS probability and KEV status are unavailable, preventing assessment of active exploitation trends. However, the attack requires only knowledge of the API endpoint and predictable VM ID enumeration - both trivial for authenticated or unauthenticated attackers who can call CloudStack APIs. The vulnerability is NOT automatable at scale without CloudStack API access, but once accessed, exploitation is trivial. Apache's prompt public disclosure (EUVD-2026-28550) and patch release suggest vendor awareness of exploitation risk. CRITICAL MISSING DATA: No information on whether default CloudStack installations expose the API endpoint unauthenticated (CVSS assumes PR:N, but typical IaaS platforms require authentication for VM management). If authentication is required in practice, real-world exploitability drops significantly - defenders should verify their deployment's API authentication posture. |
| Exploit ScenarioDerived | An attacker with access to a CloudStack tenant account (or exploiting unauthenticated API access if exposed) enumerates Proxmox VM IDs by incrementing numeric values starting from common ranges (e.g., 100-999). Using the CloudStack API, the attacker modifies the 'proxmox_vmid' instance detail of their own VM to reference a target VM ID belonging to another tenant. The attacker then issues legitimate CloudStack management commands (start, stop, reboot, destroy) which CloudStack executes against the victim's VM due to the manipulated reference, achieving full control without triggering authentication or authorization failures. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 08, 2026
Unauthorized cross-tenant access in Apache CloudStack 4.21.0 through 4.22.0 allows remote unauthenticated attackers to gain full control over virtual machines belonging to other tenants via the Proxmox extension. Attackers exploit a user-editable 'proxmox_vmid' setting that lacks tenant ownership validation and predictable VM IDs to reference and control VMs across tenant boundaries, enabling VM start/stop/destroy operations. CVSS 9.1 indicates critical severity with network attack vector and no authentication required, though EPSS data and KEV status are not available to confirm active exploitation patterns.
RemediationAI
Upgrade Apache CloudStack to version 4.22.0.1 or later, which implements proper tenant ownership validation for the proxmox_vmid parameter as documented in the Apache mailing list advisory (https://lists.apache.org/thread/n8mt5b7wkpysstb8w7rr9f02kc5cq2xm). For environments unable to immediately upgrade, implement the vendor-provided workaround by adding 'proxmox_vmid' to the global configuration parameter 'user.vm.denied.details', which prevents non-administrative users from editing this instance detail. This workaround preserves functionality for legitimate CloudStack operations while blocking user-initiated VMID manipulation. Note that the workaround does not retroactively audit or fix existing instances with attacker-modified proxmox_vmid values - administrators should audit VM associations post-mitigation using Proxmox and CloudStack logs to identify potential unauthorized access. The workaround may require administrative intervention for legitimate VM management operations that previously allowed user self-service VMID changes.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Apache CloudStack (CPE: cpe:2.3:a:apache_software_foundation:apache_cloudstack) is an open-source Infrastructure-as-a-Service platform for managing cloud computing environments. The Proxmox extension enables CloudStack integration with Proxmox Virtual Environment hypervisors. The vulnerability stems from CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), manifesting as an Insecure Direct Object Reference (IDOR) flaw. The extension uses a customer-controlled parameter 'proxmox_vmid' to map CloudStack instances to underlying Proxmox VMs without server-side validation of tenant ownership. Proxmox VM IDs follow a predictable numeric sequence, creating an enumeration vulnerability. This architectural flaw bypasses CloudStack's multi-tenancy isolation model by allowing direct manipulation of the hypervisor-level object reference through the management API.
Know when Apache Cloudstack gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Primary rating from Vendor (apache) · only source for this CVE.
CVSS VectorVendor: apache
Lifecycle Timeline
3DescriptionCVE.org
Instances deployed via the Proxmox extension allow unauthorized access to instances belonging to other tenants.
This issue affects Apache CloudStack: from 4.21.0.0 through 4.22.0.0.
The Proxmox extension for CloudStack improperly uses a user-editable instance setting, proxmox_vmid, to associate CloudStack instances with Proxmox virtual machines. Because this value is not restricted or validated against tenant ownership and Proxmox VM IDs are predictable, a non-privileged attacker can modify the setting to reference a VM belonging to another account. This allows unauthorized cross-tenant access and enables full control over the targeted VM, including starting, stopping, and destroying the virtual machine.
Users are recommended to upgrade to version 4.22.0.1, which fixes this issue.
As a workaround for the existing installations, editing of the proxmox_vmid instance detail by users can be prevented by adding this detail name to the global configuration parameter - user.vm.denied.details.
Executive ViewAI
Apache CloudStack versions 4.21.0-4.22.0 contain a critical cross-tenant isolation bypass in the Proxmox extension that permits unauthenticated attackers to assume control of virtual machines belonging to other organizations. This vulnerability directly compromises multi-tenant isolation-a foundational security boundary for cloud infrastructure-exposing all customer workloads to unauthorized manipulation, data exfiltration, and service disruption.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Disable Proxmox extension entirely if operationally feasible; (2) Implement strict network segmentation restricting CloudStack API to administrative networks only; (3) Enable API authentication and IP whitelisting at load balancer/firewall; (4) Monitor CloudStack audit logs for anomalous VM operations across tenant boundaries; (5) Establish read-only backup regime for tenant VM configurations to enable rapid recovery if unauthorized modifications occur.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Apache Cloudstack
View allCross-tenant manipulation in Apache CloudStack's Kubernetes Service (CKS) plugin allows a tenant to add and remove nodes
Two-factor authentication bypass in Apache CloudStack allows an authenticated low-privileged user to exploit an improper
Cross-tenant root command execution in Apache CloudStack (4.14.0.0-4.20.3.0 and 4.21.0.0-4.22.1.0) allows an authenticat
Remote code execution in Apache CloudStack allows authenticated account users to execute arbitrary code on KVM hyperviso
SAML authentication bypass in Apache CloudStack 4.20.3.0 and 4.22.1.0 permits a network-positioned attacker to forge SAM
Apache CloudStack deployments that use MinIO-backed object storage fail to revoke the MinIO policy associated with a buc
Authenticated CloudStack users can hijack volumes from other tenants' backups via the Backup plugin in versions 4.21.0.0
Sensitive OAuth configuration data is exposed to unauthenticated remote actors in Apache CloudStack's OAuth authenticati
Sensitive information exposure in Apache CloudStack's OAuth2 authentication plugin and Google OAuth integration allows u
Missing authorization controls across multiple Userdata-related APIs in Apache CloudStack expose cross-tenant data to an
Broken object-level authorization in Apache CloudStack exposes project role management APIs to Domain Admins operating o
Server-Side Request Forgery in Apache CloudStack's webhook module lets attackers coerce the management server into issui
EUVD-2026-28550
GHSA-whfq-93mc-cv6g
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB