# CVE-2026-22716: VMware Workstation out-of-bounds write vulnerability

> A guest user can trigger an out-of-bounds write to terminate Workstation processes, causing denial of service.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Feb 2026
- **Updated:** 27 Feb 2026
- **Also known as:** GHSA-jm5v-cr99-76mr

## What is CVE-2026-22716?

CVE-2026-22716 is a medium-severity memory corruption vulnerability in VMware Workstation, published on 27 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Out-of-bound write vulnerability in VMware Workstation 25H1 and below on any platform allows an actor with non-administrative privileges on a guest VM to terminate certain Workstation processes.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-22716?


## How do I fix CVE-2026-22716?

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

## Is CVE-2026-22716 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-22716 and fix it if it is affected.

What it is: CVE-2026-22716 is a medium-severity memory corruption vulnerability in VMware Workstation, published on 27 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-22716 in the wild and no public exploit code.

Affected product: VMware Workstation. 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-2026-22716/ (Markdown: https://insights.sbomify.com/CVE-2026-22716/index.md)
```

## Sources

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

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