# CVE-2026-59310: Broadcom VMware vCenter Path Traversal

> A malicious actor with network access can exploit a directory traversal flaw in the vCenter Syslog server to execute arbitrary code.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 18 Aug 2026 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2026
- **Updated:** 12 Sep 2026
- **Also known as:** GHSA-v2gp-49gj-2c9f

## What is CVE-2026-59310?

CVE-2026-59310 is a critical path traversal vulnerability in Vmware Vcenter Server, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

VMware vCenter contains a directory traversal vulnerability in the Syslog server. A malicious actor with network access to vCenter may exploit this issue to execute arbitrary code.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Vmware Vcenter Server.

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

No fix has been published for CVE-2026-59310 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 21 Aug 2026.

## Is CVE-2026-59310 being exploited?

Yes. Attackers have exploited CVE-2026-59310 in the wild since at least 18 Aug 2026, including in ransomware campaigns.

Public exploit code:

- VC-Strike — VMware vCenter CVE-2026-59310 (unauth root RCE) & CVE-2026-59309 (SRP auth bypass) authorized pentest suite. GUI+CLI, multi-session C2, stdlib-only. 授权测试专用 (github_poc): https://github.com/chu0119/vc-strike
- CVE-2026-59310-POC 仅用于自测，请勿用于攻击 (github_poc): https://github.com/zgsfsec/CVE-2026-59310-POC
- CVE-2026-59310 PoC (github_poc): https://github.com/BiuTrap/CVE-2026-59310
- ChinaRan0/CVE-2026-59310-POC 的优化版本。子命令、一次性 cron、带远端 PTY 的交互 shell。仅限授权测试。 (github_poc): https://github.com/vpxuser/CVE-2026-59310
- CVE-2026-59310 (github_poc): https://github.com/HORKimhab/CVE-2026-59310

## Other vulnerabilities in Vmware Vcenter Server

- [CVE-2023-34048](https://insights.sbomify.com/CVE-2023-34048/): VMware vCenter Server Out-of-Bounds Write (critical 9.8, exploited in the wild)
- [CVE-2020-3952](https://insights.sbomify.com/CVE-2020-3952/): VMware vCenter Server Information Disclosure (critical 9.8, exploited in the wild)
- [CVE-2021-22017](https://insights.sbomify.com/CVE-2021-22017/): VMware vCenter Server Improper Access Control (medium 5.3, exploited in the wild)
- [CVE-2015-2342](https://insights.sbomify.com/CVE-2015-2342/): Code injection in n/a (critical 10.0)
- [CVE-2026-59309](https://insights.sbomify.com/CVE-2026-59309/): vCenter authentication-bypass vulnerability (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59310 is a critical path traversal vulnerability in Vmware Vcenter Server, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-59310 in the wild since at least 18 Aug 2026, including in ransomware campaigns.

Affected product: Vmware Vcenter Server. 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-59310/ (Markdown: https://insights.sbomify.com/CVE-2026-59310/index.md)
```

## Sources

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

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