Skip to content
CTI Academy Sponsor CTI Academy
HIGH · CVSS 8.2 CISA Known Exploited Vulnerability

CVE-2025-22225

VMware ESXi Arbitrary Write Vulnerability

VMware ESXi

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.

CVSS
8.2
HIGH
EPSS
1%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
4 Mar 2025
CWE-787, CWE-123

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 4 March 2025. US federal agencies were required to remediate it by 25 March 2025. CISA records this vulnerability as known to be used in ransomware campaigns.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 1%, which is higher than 63.5% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Frequently asked questions

Is CVE-2025-22225 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2025-22225.

What does CVE-2025-22225 affect?

CVE-2025-22225 affects VMware ESXi. 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.

How severe is CVE-2025-22225?

CVE-2025-22225 is rated HIGH with a CVSS base score of 8.2. EPSS puts the probability of exploitation in the next 30 days at 1%, higher than 63.5% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 25 March 2025.

How should organisations respond to CVE-2025-22225?

Apply the vendor patch for VMware ESXi as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.