Threats / VMware / CVE-2025-22225
CVE-2025-22225
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
VMware ESXi vulnerability
VMware ESXi arbitrary write vulnerability allows privileged VMX process attackers to write to kernel memory and escape the sandbox environment.
Verdict
Today item, not a backlog item.
A privilege escalation and sandbox escape vulnerability in VMware ESXi that enables arbitrary kernel writes from within the VMX process context, facilitating host compromise and lateral movement in virtualized environments.
CISA KEV Yes · 2025-03-045Ransomware use Flagged5EPSS 0.00997 (verify live)6CVSS 8.23CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
11 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-03-04), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.00997 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.2 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H) · Affected: VMware, ESXi. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-123 CWE-123.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog the same day the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
WeaknessCWE-123 · CWE-123
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I gain initial access to a guest VM or VMX process with limited privileges.
Business
Guest VM compromise represents initial foothold in customer infrastructure.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the arbitrary write vulnerability to write malicious data to kernel memory.
Business
Kernel memory corruption enables escape from guest isolation boundaries.
3
Lateral reach — past segmentation narrative 3
Attacker
I break out of the VMX sandbox and achieve code execution on the ESXi host.
Business
Host compromise grants attacker control over all guest VMs and stored data.
4
Data at risk — exfiltration narrative 4
Attacker
I establish persistence and move laterally across the virtualized infrastructure.
Business
Multi-VM compromise and data exfiltration across the entire virtual environment.
5
Lights out — disruption & extortion narrative 5
Attacker
I deploy ransomware or destructive payloads across compromised hosts and guests.
Business
Widespread service disruption, data encryption, and operational downtime across customer infrastructure.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by vmwareCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.