Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2026-59310: Unauthenticated Remote Code Execution via Path Traversal in VMware vCenter Syslog Server

Published Jul 30, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days11 mentions · peak 3 in a dayToday
CVSS9.8Critical · v3.1
EPSS61.7%99th percentile
CISA KEVYesAdded Aug 18, 2026
In the wildActivePer CISA KEV
Vendor
VMware
IdentifiersCVE-2026-59310CWE-22 · Improper Limitation of a Pathname…

CVE-2026-59310 is a directory traversal vulnerability in the Syslog server component of VMware vCenter Server. An unauthenticated attacker with network access to the affected service can exploit path traversal to access locations outside the intended directory and achieve arbitrary code execution on the vCenter appliance. Exploitation requires no user interaction and has low attack complexity. The vulnerability has a CVSS v3.1 score of 9.8 and has been actively exploited, including in ransomware campaigns.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can compromise the confidentiality, integrity, and availability of the vCenter appliance and expose the virtualization management plane. Follow-on activity can include infrastructure credential theft, persistent remote access, lateral movement, and compromise of managed ESXi hosts and virtual machines. Observed intrusions established reverse-SSH access and scheduled-task persistence; ransomware-related activity deployed Babuk-derived payloads to encrypt ESXi virtual machines and datastores. These downstream outcomes depend on the access available from the compromised vCenter instance.

Mitigation

If you can’t patch tonight, do this now.

Broadcom provides no workaround. Reduce exposure by removing direct internet access to vCenter and restricting access to an isolated management network, trusted administrator jump hosts, or controlled VPN access. Network restrictions do not prevent exploitation by attackers who already have access to the permitted network. Examine previously vulnerable systems for unexpected accounts, processes, scheduled tasks, outbound connections, and changes to managed ESXi hosts. If compromise is suspected, isolate affected systems, preserve forensic evidence, and rotate privileged credentials after containment.

Remediation

Patch, then assume compromise.

Apply the VMware vCenter updates specified in Broadcom advisory VMSA-2026-0006: upgrade the applicable release branch to 9.1.0.0300, 9.0.2.0100, or 8.0 U3k, or a later vendor-supported release containing the fix. For bundled VMware Cloud Foundation, vSphere Foundation, or Telco deployments, follow the corresponding vendor response matrix and product-specific patching guidance. Prioritize deployment because exploitation is active. Investigate previously exposed systems for compromise in addition to patching; an update does not remove established attacker persistence.

Public exploits

Exploits

4 exploits validated by Mallory's analysis. Hidden: 2 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2026-59310-POCThe repository contains a Chinese-language README and one standalone Python exploit, with listed sizes totaling 20,040 bytes. No repository URL, revision, or archive size was supplied; repository size 0 represents unavailable archive metadata. The Python file uses standard-library modules and exposes argparse modes for marker-file creation, command execution, reverse shells, and cleanup guidance. The README also mentions two additional PoC scripts, but neither appears in the supplied two-file inventory. The visible implementation builds RFC5424 messages and sends them over UDP or plaintext TCP. Its APP-NAME carries traversal segments intended to escape a privileged rsyslog dynamic output path. Command mode embeds newlines around an every-minute root cron entry and redirects command output into /tmp. There is no native remote file-read primitive: optional readback delegates to an operator-supplied local command. Jobs are recurring, not one-shot, if accepted and left in place. Check mode is a write attempt, despite a source comment calling it read-only, and successful transmission is not proof of exploitation. Important validation limits remain. The supplied Python listing is truncated inside reverse-shell construction and resumes inside argument-parser initialization, preventing review of the complete listener, Python shell payload, version probe, local command helper, and cleanup implementation. The generated cron filename contains a dot in '-syslog.log'; cron implementations that reject dotted filenames in /etc/cron.d would prevent this RCE chain even if file writing succeeds. Embedded newlines may also interact with TCP syslog framing. CVE attribution, advisory references, affected versions, root execution, and claimed test results are repository assertions, not independently established facts. No clear evidence of a deliberately fake exploit or unrelated malicious behavior is visible; the cleanup deletion commands concern documented exploit artifacts.zgsfsec · Disclosed Sep 25, 2026 · python · networkOperationalCVE-2026-59310-POCThe repository consists of a Chinese-language README and one Python 3 exploit script, exploit_cve_2026_59310.py. It is a standalone, standard-library-only network exploit rather than a Metasploit or other framework module. The script constructs RFC5424 syslog messages with a fixed timestamp and priority, placing a traversal sequence in APP-NAME. It sends the payload over UDP by default or TCP on request. The claimed vulnerable rsyslog template uses APP-NAME in both a directory and filename, allowing the payload to escape /var/log/vmware/ and write files with the syslog service's stated root privileges. For RCE, plant_cron() targets /etc/cron.d and injects a newline-delimited cron entry, relying on disabled control-character escaping; cron then invokes an attacker-selected command as root. The script supports a low-impact write check, root command execution with output redirected to a predictable /tmp file, cleanup guidance, and an interactive callback shell using Bash or a Python fallback. The README also documents vulnerable versions, configuration preconditions, detection queries, and mitigations. It references additional PoC files, but those files are not present in the supplied two-file repository.ChinaRan0 · Disclosed Sep 25, 2026 · python · markdown · networkOperationalCVE-2026-59310This three-file repository contains one standalone Python 3 exploit (`cve-2026-59310.py`) and English/Chinese documentation. It is not a Metasploit, Nuclei, or other framework module. The script delivers crafted RFC5424 syslog records to a vCenter syslog service, exploiting traversal in a dynamic rsyslog APP-NAME log-path template. It supports `check`, `exec`, `shell`, and `cleanup` subcommands. Check writes a marker under /tmp; exec writes a one-shot /etc/cron.d job to execute an operator-provided command as root and capture output; shell plants a root reverse shell with PTY support; cleanup removes identified or prefix-matched artifacts. UDP/514 is the default delivery mechanism, TCP/514 is optional, and shell mode listens locally on 0.0.0.0:4444 by default. Documentation identifies vulnerable VMware vCenter branches and explains that successful exploitation depends on RFC5424 acceptance, unsafe APP-NAME path interpolation, disabled control-character escaping, and cron availability.vpxuser · Disclosed Sep 29, 2026 · python · markdown · networkOperationalvc-strikeVC-Strike is a 31-file, standard-library-only Python 3.8+ VMware vCenter penetration-testing suite with CLI and Tkinter GUI entry points (`vc-strike.py`, `vc-strike-gui.py`, and `python -m vcstrike`). It implements two network exploits: CVE-2026-59310, which abuses RFC5424 syslog fields and unsafe rsyslog dynamic path templates to write files as root and inject a root cron job; and CVE-2026-59309, which exploits missing SRP public-value validation in vmdird's Cyrus SASL SRP implementation by submitting A=N and forging authentication evidence. The former supports non-destructive write checks, arbitrary file writes, VAMI readback-based RCE, reverse shells, and a ProcessBuilder JSP webshell. The latter supports rootDSE/SRP discovery, post-bypass LDAP search/add/modify operations, user and administrator-group enumeration, SSO administrator creation, and password resets. Core implementation is in `syslog59310.py`, `srp59309.py`, `berldap.py`, `c2.py`, `recon.py`, and `postex.py`; it includes pure-Python AES-128-OFB and BER/LDAP implementations, offline self-tests, and unit tests. C2 functionality manages multiport listeners and reverse-shell sessions, interactive command execution, and base64-based file transfers. Documentation and `data.py` also provide cleanup instructions, IOCs, version checks, network restrictions, and rsyslog hardening guidance. No hard-coded victim infrastructure is present; target hosts and reverse-shell listener addresses are operator supplied.chu0119 · Disclosed Oct 1, 2026 · python · yaml · network · webOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
VMwareVmware Cloud Foundationapplication
VMwareVmware Telco Cloud Infrastructureapplication
VMwareVmware Telco Cloud Platformapplication
VMwareVmware Vcenter Serverapplication
FAQ

Frequently asked questions

Is CVE-2026-59310 exploited in the wild?
Yes. As of Nov 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Aug 18, 2026.
Is there a public exploit for CVE-2026-59310?
Yes. Mallory tracks 4 public exploits or proofs of concept for CVE-2026-59310, the earliest disclosed Sep 25, 2026.
Is there a patch for CVE-2026-59310?
Apply the VMware vCenter updates specified in Broadcom advisory VMSA-2026-0006: upgrade the applicable release branch to 9.1.0.0300, 9.0.2.0100, or 8.0 U3k, or a later vendor-supported release containing the fix. For bundled VMware Cloud Foundation, vSphere Foundation, or Telco deployments, follow the corresponding vendor response matrix and product-specific patching guidance.
What products are affected by CVE-2026-59310?
Vmware Vcenter Server, Vmware Cloud Foundation, Vmware Telco Cloud Infrastructure, and Vmware Telco Cloud Platform.
How severe is CVE-2026-59310?
CVE-2026-59310 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 61.7% (99th percentile) as of Nov 16, 2026.
Activity feed

Recent activity

283 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+32 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence1Every report linking this CVE to a named adversary.
Associated malware25Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity159Community discussion across Reddit, Mastodon, and other social sources.