# CVE-2025-41239: vSockets information-disclosure vulnerability

> Local administrators on virtual machines can leak memory from vSockets processes due to uninitialized memory usage in VMware products.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **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:** 15 Jul 2025
- **Updated:** 15 Jul 2025
- **Also known as:** GHSA-8p72-rxh7-qv97

## What is CVE-2025-41239?

CVE-2025-41239 is a high-severity vulnerability in VMware Cloud Foundation, published on 15 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

VMware ESXi, Workstation, Fusion, and VMware Tools contains an information disclosure vulnerability due to the usage of an uninitialised memory in vSockets. A malicious actor with local administrative privileges on a virtual machine may be able to exploit this issue to leak memory from processes communicating with vSockets.

Weakness: CWE-908 (Use of Uninitialized Resource)

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


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

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

## Is CVE-2025-41239 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41239 is a high-severity vulnerability in VMware Cloud Foundation, published on 15 Jul 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-41239 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-41239/ (Markdown: https://insights.sbomify.com/CVE-2025-41239/index.md)
```

## Sources

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

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