# CVE-2026-41703: Out-of-bounds read vulnerability

> A malicious actor with VM deployment privileges can trigger an out-of-bounds read, causing information disclosure or denial of service.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-m337-3vqr-5pf8

## What is CVE-2026-41703?

CVE-2026-41703 is a high-severity vulnerability in VMware Cloud Foundation, published on 30 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

VMware ESX, Workstation, and Fusion contain an out-of-bounds read vulnerability. A malicious actor with VM deployment privileges could trigger an out-of-bounds read, potentially leading to information disclosure or more likely a Denial-of-Service (DoS) condition of the host process. On Workstation and Fusion, the impact of this vulnerability is restricted to information disclosure.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-41703 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41703 is a high-severity vulnerability in VMware Cloud Foundation, published on 30 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-41703 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-2026-41703/ (Markdown: https://insights.sbomify.com/CVE-2026-41703/index.md)
```

## Sources

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

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