VMware vCenter Flaw (CVE-2026-59310) Exploited by APTs

APT actors actively exploiting critical VMware vCenter flaw (CVE-2026-59310)

CRITICAL
August 14, 2026
August 18, 2026
5m read
VulnerabilityCyberattackThreat Actor

Related Entities(initial)

Threat Actors

Advanced Persistent Threat (APT)

Organizations

Broadcom QUIRSO

Products & Tech

Other

reverse_ssh

CVE Identifiers

CVE-2026-59310
CRITICAL
CVSS:9.8

Full Report(when first published)

Executive Summary

A critical directory traversal vulnerability in Broadcom's VMware vCenter Server, tracked as CVE-2026-59310 with a CVSS score of 9.8, is under active exploitation by a suspected Advanced Persistent Threat (APT) actor. The flaw allows unauthenticated attackers with network access to achieve remote code execution. The campaign began within days of patch release, indicating rapid weaponization. Attackers are establishing persistent access on compromised servers using reverse SSH tunnels. German security firm QUIRSO has identified over 360 compromised systems across 47 countries. Due to the critical nature of this vulnerability and evidence of widespread, active attacks, immediate patching and threat hunting are imperative for all organizations using vCenter Server.


Vulnerability Details

The vulnerability, CVE-2026-59310, is a directory traversal flaw residing in the vCenter Syslog server component. An unauthenticated attacker with network access to a vulnerable vCenter instance can send a specially crafted request to the Syslog service. This request allows the attacker to traverse the file system and write arbitrary files to sensitive locations on the server, ultimately leading to remote code execution (RCE). The high CVSS score of 9.8 reflects the low attack complexity, lack of required privileges, and the severe impact of a successful exploit.

Exploitation Status

Active exploitation began around August 3, 2026, a mere five days after Broadcom released security updates on July 29, 2026. This rapid operationalization suggests that the threat actors likely performed patch diffing to quickly develop a working exploit. The campaign is global and ongoing, with new victims being identified daily. The attackers' primary post-exploitation objective is to establish and maintain long-term persistence on the compromised vCenter servers.

Technical Analysis

The attack chain observed by QUIRSO follows these steps:

  1. Initial Access: The threat actor exploits CVE-2026-59310 against a public-facing, unpatched vCenter Server. This aligns with T1190 - Exploit Public-Facing Application.
  2. Execution & Persistence: The attacker uses the directory traversal flaw to write a malicious script to the server. This script is then used to create a cron job, a common persistence technique on Linux-based systems (T1053.003 - Scheduled Task/Job: Cron).
  3. Command and Control: The cron job executes reverse_ssh, an open-source tool, to establish a persistent reverse SSH tunnel to an attacker-controlled command-and-control (C2) server. This provides the actor with ongoing, interactive access to the compromised system, bypassing perimeter firewalls (T1021.002 - Remote Services: SSH).

While attribution remains unconfirmed, the speed, sophistication, and targeting of critical infrastructure management tools are hallmarks of a state-sponsored APT group.

Impact Assessment

Compromise of a vCenter Server can have catastrophic consequences for an organization. vCenter is the central management platform for VMware vSphere environments, providing control over virtual machines, storage, and networking. An attacker with administrative access to vCenter can:

  • Deploy ransomware across the entire virtualized environment.
  • Exfiltrate sensitive data from any virtual machine.
  • Move laterally to other parts of the network.
  • Disrupt business operations by powering off or deleting critical servers.

Given that over 361 victims have been identified in 47 countries, the potential for widespread disruption and data breaches is significant. The highest concentrations of victims are in Germany, the United States, Turkey, Iran, and France.

IOCs — Directly from Articles

No specific file hashes, C2 domains, or IP addresses were disclosed in the source articles.

Cyber Observables — Hunting Hints

Security teams may want to hunt for the following patterns to detect potential compromise:

Type
Process Name
Value
reverse_ssh
Description
The open-source tool used by attackers for C2 communications. Monitor for its execution.
Type
Log Source
Value
vcenter_syslog_logs
Description
Review logs for anomalous requests, especially those containing directory traversal patterns like ../.
Type
Network Traffic
Value
Outbound SSH
Description
Monitor for new or unusual outbound SSH connections (typically on port 22) from vCenter servers to external IP addresses.
Type
File Path
Value
/var/spool/cron/crontabs/
Description
Monitor for newly created or modified cron jobs, particularly for the root user or vCenter service accounts.
Type
Command Line Pattern
Value
ssh -R
Description
The reverse_ssh tool is a wrapper for ssh. Look for command-line executions containing the -R flag for remote port forwarding.

Detection & Response

  • Log Analysis: Ingest vCenter Server logs into a SIEM. Create detection rules for suspicious activity on the Syslog service port, looking for traversal patterns in URLs. Correlate web access logs with process execution events on the vCenter appliance. D3FEND's Network Traffic Analysis (D3-NTA) is critical here.
  • Endpoint Detection (EDR): Ensure EDR is deployed on vCenter servers (if running on Windows) or that the vCenter Server Appliance (VCSA) logs are being monitored for anomalous process creation. Look for the execution of shell scripts from unexpected directories or the launch of reverse_ssh or ssh with reverse tunneling parameters.
  • Network Monitoring: Monitor all outbound traffic from vCenter servers. Since the C2 channel uses SSH, look for outbound connections on port 22 to untrusted IP space. Consider baselining normal administrative traffic and alerting on deviations.

Mitigation

  • Patch Immediately: The most critical action is to apply the patches released by Broadcom for CVE-2026-59310. This is the only way to fully remediate the vulnerability. This aligns with D3FEND's Software Update (D3-SU).
  • Restrict Access: Do not expose the vCenter Server management interface to the public internet. Access should be restricted to a dedicated management network, accessible only via VPN or a secure jump host. This is a form of D3FEND's Network Isolation (D3-NI).
  • Egress Filtering: Implement strict egress firewall rules for vCenter servers. Deny all outbound traffic by default and only allow connections to specific, trusted destinations required for normal operation (e.g., NTP servers, update repositories). This would block the reverse_ssh C2 channel.

Timeline of Events

1
July 29, 2026
Broadcom (VMware) releases patches for CVE-2026-59310.
2
August 3, 2026
First signs of active exploitation of CVE-2026-59310 are observed in the wild.
3
August 14, 2026
This article was published

Article Updates

August 18, 2026

New intelligence attributes vCenter exploitation to China-linked APT, revealing use of a second CVE-2026-59309 for persistence and Babuk ransomware deployment.

MITRE ATT&CK Mitigations

Apply the security patches provided by VMware to remediate the vulnerability.

Mapped D3FEND Techniques:

Restrict network access to the vCenter management interface. It should not be exposed to the internet.

Mapped D3FEND Techniques:

Implement strict egress filtering rules for the vCenter server to block unauthorized outbound connections like reverse SSH tunnels.

Mapped D3FEND Techniques:

Audit

M1047enterprise

Regularly audit vCenter logs for signs of compromise, such as anomalous login patterns or process executions.

Mapped D3FEND Techniques:

Timeline of Events

1
July 29, 2026

Broadcom (VMware) releases patches for CVE-2026-59310.

2
August 3, 2026

First signs of active exploitation of CVE-2026-59310 are observed in the wild.

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Editorial Standards & Analyst Review

CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.

Tags

CVE-2026-59310VMwarevCenterAPTRCEDirectory TraversalCyberattack

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.

Sigma Generator

Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.