https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 05:22:58 +0000 https://cve.radiocsirt.org/vuln/cve-2026-25199 <p><strong>Affected:</strong> Apache Software Foundation Apache CloudStack</p> <p>Instances deployed via the Proxmox extension allow unauthorized access to instances belonging to other tenants.</p> <p>This issue affects Apache CloudStack: from 4.21.0.0 through 4.22.0.0.</p> <p>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.</p> <p>Users are recommended to upgrade to version 4.22.0.1, which fixes this issue.</p> <p>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.</p> <p><strong>Affected:</strong> Apache Software Foundation Apache CloudStack</p> <p>Instances deployed via the Proxmox extension allow unauthorized access to instances belonging to other tenants.</p> <p>This issue affects Apache CloudStack: from 4.21.0.0 through 4.22.0.0.</p> <p>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.</p> <p>Users are recommended to upgrade to version 4.22.0.1, which fixes this issue.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/cve-2026-25199