# CVE-2025-41226: Guest Operations Denial-of-Service Vulnerability

> Authenticated attackers with guest operation privileges can cause denial of service on VMs with VMware Tools enabled.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 May 2025
- **Updated:** 24 Jun 2025
- **Also known as:** GHSA-jfjv-vw9w-9w8v

## What is CVE-2025-41226?

CVE-2025-41226 is a medium-severity denial of service vulnerability in VMware Cloud Foundation, published on 20 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

VMware ESXi contains a denial-of-service vulnerability that occurs when performing a guest operation. A malicious actor with guest operation privileges on a VM, who is already authenticated through vCenter Server or ESXi may trigger this issue to create a denial-of-service condition of guest VMs with VMware Tools running and guest operations enabled.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2025-41226?


## How do I fix CVE-2025-41226?

No fix has been published for CVE-2025-41226 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-41226 being exploited?

There is no known exploitation of CVE-2025-41226 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-41226 and fix it if it is affected.

What it is: CVE-2025-41226 is a medium-severity denial of service vulnerability in VMware Cloud Foundation, published on 20 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-41226 in the wild and no public exploit code.

Affected product: VMware Cloud Foundation. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-41226/ (Markdown: https://insights.sbomify.com/CVE-2025-41226/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-41226
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-41226
- OSV: https://osv.dev/vulnerability/CVE-2025-41226

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-41226/
Summaries are generated and may contain mistakes; the official description above is the record.