# CVE-2026-22715: VMware Workstation/Fusion NAT vulnerability

> A guest VM administrator can intercept or disrupt network traffic of other guest VMs due to a NAT logic flaw in VMware Workstation and Fusion.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Feb 2026
- **Updated:** 27 Feb 2026
- **Also known as:** GHSA-r6f6-7cf6-c3cg

## What is CVE-2026-22715?

CVE-2026-22715 is a medium-severity vulnerability in VMware Fusion, published on 26 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

VMWare Workstation and Fusion contain a logic flaw in the management of network packets. 

Known attack vectors: A malicious actor with administrative privileges on a Guest VM may be able to interrupt or intercept network connections of other Guest VM's. 

Resolution: To remediate CVE-2026-22715 please upgrade to VMware Workstation or Fusion Version 25H2U1

Weakness: CWE-923 (Improper Restriction of Communication Channel to Intended Endpoints)

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


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

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

## Is CVE-2026-22715 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22715 is a medium-severity vulnerability in VMware Fusion, published on 26 Feb 2026. 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-2026-22715 in the wild and no public exploit code.

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

## Sources

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

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