CVE-2026-25199
Last modified
CVE-2026-25199 is a critical-severity vulnerability rated 9.1/10 on the CVSS scale. 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. EPSS estimates a 0.50% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Apache | Cloudstack | >= 4.21.0.0, < 4.22.0.1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2026-25199?
How severe is CVE-2026-25199?
How do I fix CVE-2026-25199?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-25193Insertion of Sensitive Information into Log File (CWE-532) i…8.1
- CVE-2026-25194Out-of-bounds write in the firmware for the Intel(R) Slim Bo…1.8
- CVE-2026-25195An OS command injection vulnerability exists in XWEB Pro…6.6
- CVE-2026-25196An OS command injection vulnerability exists in XWEB Pro ve…8.8
- CVE-2026-25197A specific endpoint allows authenticated users to pivot to o…8.1
- CVE-2026-25198web2py versions 2.27.1-stable+timestamp.2023.11.16.08.03.57 …5.1
- CVE-2026-25200A vulnerability in MagicInfo9 Server allows authorized users…9.8
- CVE-2026-25201An unauthenticated user can upload arbitrary files to execut…8.8
- CVE-2026-25202The database account and password are hardcoded, allowing lo…9.8
- CVE-2026-25203Samsung MagicINFO 9 Server Incorrect Default Permissions Loc…7.8
- CVE-2026-25204Deserialization of untrusted data vulnerability in Samsung O…7.5
- CVE-2026-25205Heap-based buffer overflow vulnerability in Samsung Open Sou…9.8
Are you affected by CVE-2026-25199?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
