PT-2025-9652 · Vmware · Vmware Esxi
Published
2025-03-04
·
Updated
2026-03-07
·
CVE-2025-22225
CVSS v3.1
8.2
8.2
High
| Base vector | Vector | AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H |
Name of the Vulnerable Software and Affected Versions
VMware ESXi (affected versions not specified)
Description
VMware ESXi contains an arbitrary write vulnerability. A malicious actor with privileges within the
VMX process may trigger an arbitrary kernel write, leading to an escape of the sandbox. This vulnerability is actively being exploited in the wild by ransomware groups. Reports indicate that attackers are leveraging this flaw to gain code execution on the host, potentially impacting multiple virtual machines. The exploit toolkit used by attackers leverages HGFS (Host-Guest File System) for data exfiltration, VMCI (Virtual Machine Communication Interface) for memory corruption, and kernel-level shellcode to escalate privileges. There have been confirmed reports of exploitation, and CISA has added this vulnerability to its KEV catalog. The vulnerability allows attackers to escape the virtual machine's sandbox and gain unrestricted access to host systems.Recommendations
Apply the latest security updates from Broadcom for VMware ESXi.
Verify the current version of ESXi in use and follow VMware’s official guidance to deploy the fix immediately.
Implement network segmentation to isolate ESXi hosts from critical systems.
Restrict access to the
VMX process using role-based access controls.
Regularly audit virtual machine configurations and monitor for anomalous behavior, such as unexpected process creation or unusual outbound traffic.Fix
LPE
Memory Corruption
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
BDU:2025-02379
CVE-2025-22225
Affected Products
Vmware Esxi
References · 155
- https://bdu.fstec.ru/vul/2025-02379 · Security Note
- https://nvd.nist.gov/vuln/detail/CVE-2025-22225 · Security Note
- https://twitter.com/shah_sheikh/status/2019174426970042557 · Twitter Post
- https://twitter.com/syedaquib77/status/1896927354523639941 · Twitter Post
- https://twitter.com/ox0ffff/status/2019205989229023572 · Twitter Post
- https://twitter.com/jbhall56/status/2019404819828731962 · Twitter Post
- https://twitter.com/dCypherIO/status/1897255783894560798 · Twitter Post
- https://twitter.com/MertSARICA/status/1897282951974453409 · Twitter Post
- https://twitter.com/NickBla41002745/status/1899486754140520825 · Twitter Post
- https://twitter.com/ThreatSynop/status/2019178153688854790 · Twitter Post
- https://twitter.com/CVEnew/status/1897133303632720222 · Twitter Post
- https://twitter.com/NickBla41002745/status/1900573924766998580 · Twitter Post
- https://twitter.com/gbhackers_news/status/1897250694216011890 · Twitter Post
- https://twitter.com/f1tym1/status/2019192853964931119 · Twitter Post
- https://twitter.com/grok/status/2008302979951001602 · Twitter Post