CVE-2025-22224 — Cloud Foundation
CRITICALCVE-2025-22224 is a critical-severity (CVSS 9.3) CWE-367 vulnerability in vmware cloud foundation. It is in CISA's Known Exploited Vulnerabilities catalog (added 2025-03-04) — treat it as actively exploited and patch now. A fix is available — see the affected versions and patch details below.
VMware ESXi, and Workstation contain a TOCTOU (Time-of-Check Time-of-Use) vulnerability that leads to an out-of-bounds write. A malicious actor with local administrative privileges…
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2025-03-04. Federal agencies were required to remediate by 2025-03-25.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2025-22224.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2025-22224 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 395,249 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Description
VMware ESXi, and Workstation contain a TOCTOU (Time-of-Check Time-of-Use) vulnerability that leads to an out-of-bounds write. A malicious actor with local administrative privileges on a virtual machine may exploit this issue to execute code as the virtual machine's VMX process running on the host.
Affected Products
cloud foundationvmwareesxivmwaretelco cloud infrastructurevmwaretelco cloud platformvmwareworkstationvmwareDetection & mitigation playbook
Vendor / applianceDetect
Inventory every vmware cloud foundation deployment and check each version against the affected-products list above.
Fix
Apply the vmware cloud foundation security patch or hotfix for CVE-2025-22224 on the affected version, following the vendor advisory for your exact build.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.
Frequently Asked Questions
Is CVE-2025-22224 being exploited in your environment?
Detect and block the exploit chain at execution, on systems you cannot patch yet.