All Threat Alerts
criticalCVE Alert
CVE-2026-25199

Critical Vulnerability: CVE-2026-25199 β€” apache β€” cloudstack

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 mod

Thursday, May 14, 2026apacheVulnios Threat Intelligence
Share:

Vulnerability Snapshot

CVE-2026-25199 is rated CRITICAL β€” exploitation is trivial or already observed in the wild and impact is severe. Patch immediately, not on the next maintenance window.

Affected technology: cloudstack.

Executive Summary

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

Why It Matters

CVE-2026-25199 is rated CRITICAL severity, requiring immediate attention from security teams.

CVSS Base Score: 9.1/10

Affected Technologies

Vendors: apache

Products: cloudstack

πŸ›‘οΈWhat Defenders Should Check

  • Check if you are affected β€” Review your asset inventory for products listed in CVE-2026-25199.
  • Apply available patches β€” Visit vendor advisories for the latest security updates.
  • Monitor for exploitation β€” Check your SIEM/IDS logs for related indicators.
  • Use Vulnios to continuously monitor your exposure to CVE-2026-25199 and similar vulnerabilities.

    References & Sources

    How Vulnios Detects This

    Vulnios scans for this vulnerability using Trivy and Grype for CVE matching against your container images and OS package manifests and Nuclei templates that probe live HTTP surfaces for the published exploit pattern. Run a scan against your environment to see whether you are exposed; findings are linked back to the original CVE record so triage starts with the patch path already known.

    AI Security Advisor

    Powered by Gemini

    Get AI-powered security recommendations tailored to this specific threat β€” including risk assessment, detection guidance, MITRE ATT&CK mapping, and actionable remediation steps.

    Affected Products

    cloudstack

    Sources

    Related Threat Alerts

    Frequently Asked Questions

    What is CVE-2026-25199?

    CVE-2026-25199 is a critical-severity vulnerability tracked under the Common Vulnerabilities and Exposures program. 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 Proxmo

    Am I affected?

    Check whether your environment runs cloudstack. If you operate any of those, treat yourself as in scope until you have evidence otherwise. A Vulnios scan will identify the exact assets carrying the affected version.

    How urgent is the response?

    Critical: do not wait for your normal patch cycle. Verify exposure today, apply the vendor patch immediately, and add detection rules for any post-exploit indicators.

    How do I remediate?

    Apply the vendor patch listed in the upstream advisory linked under Sources. If the patch is not yet available, follow the vendor-supplied workaround (often a config flag or feature disable) and add detections for the published exploit pattern in your SIEM. Re-scan after the patch lands to confirm the finding clears.

    Where can I track exploitation activity?

    Watch CISA's Known Exploited Vulnerabilities catalog for CVE-2026-25199. Cross-reference with public exploit databases and your own SIEM/IDS for indicator-of-compromise patterns. Vulnios tracks KEV status automatically and surfaces it on the asset findings view.

    How does Vulnios help with this?

    Vulnios continuously cross-references your asset inventory against the live CVE feed (NVD, vendor advisories, CISA KEV, and curated OSINT). When a new CVE matches your environment, you get a prioritized finding with the severity, KEV status, exploit-prediction (EPSS), and a direct path to the vendor patch. You can start a free scan from the homepage.

    critical

    Protect Your Organization

    Monitor CVEs, scan for vulnerabilities, and get real-time threat alerts β€” all in one platform.

    Get instant alerts on Telegram

    Join our public channel for real-time critical CVE alerts.

    Follow @vulnios