CVE-2026-59309: VMware vCenter Server vmdir Authentication Bypass
A critical unauthenticated authentication bypass vulnerability in the VMware Directory Service (vmdir) of VMware vCenter Server and VMware Cloud Foundation (VMSA-2026-0006) is undergoing active internet-wide scanning and exploitation in the wild, as confirmed by The Shadowserver Foundation. The flaw enables remote attackers with network line-of-sight to LDAP/RPC ports (TCP 389/636/2012) to bypass cryptographic challenge-response verification during SASL/GSS-API bind handshakes. An erroneous state transition marks the LDAP session as administrative (cn=Administrator,cn=Users,dc=vsphere,dc=local). Threat actors gain instantaneous administrative command of the vSphere Single Sign-On (SSO) domain, enabling hypervisor-wide VMDK disk exfiltration, ESXi host backdooring, and snapshot manipulation. Hermes rates CVE-2026-59309 at HTS 98 (CRITICAL).
HERMES THREAT SCORE & VIRTUALIZATION FABRIC AUTHENTICATION INTEGRITY
Target:VMware Directory Service daemon (vmdir / vCenter Single Sign-On) [object Object]
1. Executive Summary & Threat Telemetry
Section titled โ1. Executive Summary & Threat TelemetryโIn security advisory VMSA-2026-0006, Broadcom disclosed a critical authentication bypass vulnerability (CVE-2026-59309) residing in the VMware Directory Service (vmdir) component of VMware vCenter Server and VMware Cloud Foundation. The flaw carries a maximum CVSS v3.1 base score of 9.8 (CRITICAL).
The Shadowserver Foundation monitors daily honeypot telemetry and internet-wide scanning campaigns, confirming that thousands of vCenter Server instances exposed to internal corporate routing or public interfaces are receiving automated exploit probes targeting port TCP 389 (LDAP) and TCP 636 (LDAPS). Attackers exploit an ASN.1 parsing and SASL state transition defect to force the directory daemon into binding unauthenticated network connections with the highest privilege level: Administrator@vsphere.local.
flowchart TD subgraph External["Adversary / Threat Actor"] Attacker["Remote Unauthenticated Attacker"] Probes["Crafted SASL Bind / ASN.1 Payload"] end
subgraph Fabric["Virtualization Control Plane (vCenter Server)"] Port389["TCP 389/636 (LDAP / LDAPS)"] VMDir["VMware Directory Service (vmdir)"] StateCheck{"SASL Handshake\nState Transition"} Bypass["Early Protocol Return (VMDIR_SUCCESS)\nSession Bound as Administrator"] SSO["vCenter Single Sign-On (SSO)"] end
subgraph Impact["Infrastructure Compromise"] ESXi["ESXi Hypervisor Fleet"] Storage["vSAN / VMDK Virtual Disks"] DC["Guest Domain Controllers / Secrets"] end
Attacker --> Probes Probes --> Port389 Port389 --> VMDir VMDir --> StateCheck StateCheck -->|Malformed Challenge Sequence| Bypass Bypass --> SSO SSO --> ESXi SSO --> Storage SSO --> DC2. Architectural Root Cause & Vulnerability Decomposition
Section titled โ2. Architectural Root Cause & Vulnerability DecompositionโThe vulnerability is rooted in the protocol dispatching and authentication state machine of vmdir (vmdir/server/ldap-head/bind.c and vmdir/server/middle-layer/sasl.c).
The vmdir service handles identity synchronization and single sign-on across Platform Services Controllers (PSCs). During an LDAP Bind operation, clients submit authentication requests via SASL mechanisms (such as SRP or GSS-API). The connection context structure VDIR_LDAP_CONNECTION tracks the authentication progress:
typedef struct _VDIR_LDAP_CONNECTION { PVMDIR_STRING pszBindDN; VDIR_LDAP_CONNECTION_STATE connState; BOOLEAN bIsAuthenticated; PVMDIR_BERVALUE pSaslContext; PVMDIR_ENTRY pBindingEntry;} VDIR_LDAP_CONNECTION, *PVDIR_LDAP_CONNECTION;In vulnerable versions of vmdir, the function VmDirProcessSaslBindRequest() processes incoming BER-encoded packets in a multi-step exchange. If a client transmits a sequence with an unrecognized SASL sub-protocol identifier combined with a malformed token length buffer, the parser encounters an unexpected termination branch. Instead of aborting the connection with LDAP_INVALID_CREDENTIALS (error code 49), the error handling logic returns VMDIR_SUCCESS from the outer envelope:
DWORDVmDirProcessSaslBindRequest( PVDIR_LDAP_CONNECTION pConn, PVDIR_OPERATION pOperation){ DWORD dwError = 0;
// Step 1: Decode incoming SASL parameters dwError = VmDirDecodeSaslBindParams(pOperation); if (dwError != 0) { // VULNERABILITY: Fallthrough branch fails to reset connection security context // and treats partial negotiation as complete when replication flag is parsed if (pOperation->reqBind.bReplicationContext) { pConn->bIsAuthenticated = TRUE; // Insecure promotion! pConn->pBindingEntry = gVmdirServerGlobals.pAdminEntry; return VMDIR_SUCCESS; } return dwError; }
// Step 2: Validate challenge response... return dwError;}Because pConn->bIsAuthenticated is set to TRUE without verifying that cryptographic challenge tokens have been validated, the connection descriptor transitions into an authenticated state tied to the built-in SSO administrator directory entry.
3. Attack Vectors & Exploit Chain Mechanics
Section titled โ3. Attack Vectors & Exploit Chain MechanicsโStage 1: Protocol Handshake & Bind Spoofing
Section titled โStage 1: Protocol Handshake & Bind SpoofingโThe attacker initiates a standard TCP connection to vCenter Server on port 389 or 636. An initial BindRequest packet is transmitted claiming SASL negotiation with replication context flags enabled.
Stage 2: Privilege Promotion
Section titled โStage 2: Privilege Promotionโvmdir processes the malformed packet, trips the flawed state transition logic, and binds the connection descriptor to cn=Administrator,cn=Users,dc=vsphere,dc=local. The server responds with LDAP_SUCCESS (error code 0).
Stage 3: Directory Modification & Admin Injection
Section titled โStage 3: Directory Modification & Admin InjectionโThe attacker uses the established session to issue an AddRequest or ModifyRequest adding a rogue user account or assigning an attacker-controlled account to the high-privilege directory groups:
cn=Administrators,cn=Builtin,dc=vsphere,dc=localcn=SystemConfiguration.Administrators,cn=Builtin,dc=vsphere,dc=local
Stage 4: Cloud Infrastructure Control & Workload Exfiltration
Section titled โStage 4: Cloud Infrastructure Control & Workload ExfiltrationโWith full administrative access to the vCenter API, the attacker:
- Generates administrative vCenter SAML bearer tokens.
- Interacts with ESXi host management daemons (
hostd). - Takes VM snapshots of Windows Domain Controllers to extract
NTDS.dit. - Clones or downloads VMDK virtual disks directly over HTTPS port 443.
sequenceDiagram autonumber actor Attacker as Threat Actor participant VMDIR as vCenter vmdir (:389) participant SSO as vSphere SSO Engine participant ESXi as ESXi Hypervisors
Attacker->>VMDIR: TCP SYN & LDAP Connect VMDIR-->>Attacker: TCP ACK (Connection Established) Attacker->>VMDIR: Crafted SASL BindRequest (Malformed ASN.1 Sequence) Note over VMDIR: State machine evaluates incomplete token.<br/>Triggers insecure promotion to admin entry! VMDIR-->>Attacker: LDAP BindResponse (ResultCode: Success 0) Attacker->>VMDIR: ModifyRequest (Add User to SystemConfiguration.Administrators) VMDIR-->>Attacker: ModifyResponse (Success 0) Attacker->>SSO: Authenticate via newly injected Admin Account SSO-->>Attacker: Issue Valid Admin SAML Token Attacker->>ESXi: Snapshot VM / Download VMDK Disks Note over ESXi: Total Virtualization Fabric Compromise4. Real-World Weaponization & Threat Actor Profiling
Section titled โ4. Real-World Weaponization & Threat Actor ProfilingโTelemetry from The Shadowserver Foundation and incident response investigations indicate threat actor groups are weaponizing CVE-2026-59309 across multiple intrusion campaigns:
- Ransomware Pre-Positioning: Ransomware operators prioritize vCenter access because compromising the hypervisor layer bypasses all guest-level EDR agents. Once vCenter is breached, actors deploy Linux-based encryptors directly targeting ESXi datastores (
/vmfs/volumes/). - Persistence via Ghost Administrators: Attackers create hidden directory accounts within non-default organizational units in the SSO tree that remain invisible in the standard vSphere Client UI.
- Exploit Chaining with CVE-2026-59310: By combining directory access with the syslog path traversal flaw, attackers upload arbitrary binaries into
/usr/lib/vmware-syslog/to gain root access on the vCenter Server Appliance (VCSA) underlying Photon OS.
5. Detection Engineering & Triage
Section titled โ5. Detection Engineering & Triageโtitle: VMware vCenter vmdir Unauthenticated Admin Promotionid: 9a41c8f2-3901-4be1-9102-cve202659309status: experimentaldescription: Detects LDAP Bind success followed by anomalous directory modifications originating from untrusted network ranges targeting vCenter vmdir.references: - https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/VMSA-2026-0006 - https://dashboard.shadowserver.org/author: Hermes Codex Cyber Defense Teamdate: 2026-11-08logsource: category: application product: vmware_vcenterdetection: selection_log: file_name: 'vmdird.log' message|contains: - 'BindRequest: SASL bind succeeded with unverified context' - 'BindResponse: result=0' selection_mod: message|contains: - 'ModifyRequest: member added to cn=Administrators' - 'ModifyRequest: member added to cn=SystemConfiguration.Administrators' filter_known_pcs: source_ip|cidr: - '10.0.0.0/8' - '172.16.0.0/12' - '192.168.0.0/16' condition: (selection_log or selection_mod) and not filter_known_pcsfalsepositives: - Authorized vCenter Single Sign-On replication sync between newly joined Platform Services Controllers.level: criticaltags: - attack.initial_access - attack.t1190 - attack.t1078 - cve.2026.59309// Detect anomalous vCenter Directory Service Bind & Group ModificationsVMware_vCenter_CL| where TimeGenerated >= ago(24h)| where ProcessName =~ "vmdird" or LogSource has "vmdir"| where Message has_any ("SASL bind succeeded with unverified", "cn=Administrators", "cn=SystemConfiguration.Administrators")| extend ClientIP = extract(@"from IP:? ([0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3})", 1, Message)| extend Action = iff(Message has "ModifyRequest", "Group Modification", "Suspicious Bind")| project TimeGenerated, HostName, Action, ClientIP, Message| summarize EventCount = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by HostName, ClientIP, Action| order by EventCount descalert tcp $EXTERNAL_NET any -> $HOME_NET [389,636,2012] ( msg:"HERMES - VMware vCenter vmdir Authentication Bypass Exploit Attempt (CVE-2026-59309)"; flow:established,to_server; content:"|30|"; depth:1; content:"|02 01|"; distance:0; content:"|60|"; distance:2; within:3; # BindRequest content:"|a3|"; distance:0; # SASL credentials choice content:"GSS-API"; nocase; content:"|ff ff ff ff|"; # Malformed token buffer length indicator classtype:attempted-admin; sid:202659309; rev:1; metadata:cve CVE-2026-59309, severity critical;)index=vmware sourcetype="vmware:vcenter:vmdird"(Message="*SASL bind succeeded with unverified context*" OR Message="*ModifyRequest*cn=Administrators*")| rex field=Message "from (?<src_ip>\d+\.\d+\.\d+\.\d+)"| stats count earliest(_time) as first_seen latest(_time) as last_seen by host, src_ip, Message| eval first_seen=strftime(first_seen, "%Y-%m-%d %H:%M:%S"), last_seen=strftime(last_seen, "%Y-%m-%d %H:%M:%S")| sort - count6. Forensic Analysis & Incident Response Playbook
Section titled โ6. Forensic Analysis & Incident Response Playbookโ-
Isolate LDAP and Management Interfaces: Immediately restrict access to TCP ports 389, 636, and 2012 on all vCenter Server Appliances. Block incoming traffic from untrusted networks and non-management subnets at network firewalls.
-
Inspect vmdir Audit Logs: Navigate to
/var/log/vmware/vmdir/on the VCSA appliance and inspectvmdird.logandvmdird-syslog.log:Terminal window grep -Ei "BindRequest|ModifyRequest|cn=Administrators" /var/log/vmware/vmdir/vmdird.log*Look for bind events occurring from non-PSC IPs followed immediately by account modification requests.
-
Audit vCenter Single Sign-On User Accounts: Execute the
dir-cliutility on the VCSA console to inspect membership of administrative groups:Terminal window /usr/lib/vmware-vmafd/bin/dir-cli group list --name Administrators/usr/lib/vmware-vmafd/bin/dir-cli group list --name SystemConfiguration.AdministratorsVerify that every listed account corresponds to verified corporate personnel or known service accounts.
-
Verify Guest VM Snapshot and VMDK Download History: Query
/var/log/vmware/vpxd/vpxd.logfor anomalous snapshot creations or virtual disk export tasks initiated by administrative sessions:Terminal window grep -E "CreateSnapshot_Task|ExportVm_Task|VirtualMachine.disk.export" /var/log/vmware/vpxd/vpxd.log -
Examine Chained Exploit Artifacts: Check
/var/log/vmware/messagesand syslog directories for evidence of chained exploitation via CVE-2026-59310:Terminal window ls -la /usr/lib/vmware-syslog/find /tmp /var/tmp -name "*.py" -o -name "*.sh" -o -name "*.elf"
7. Remediation & Mitigation Strategy
Section titled โ7. Remediation & Mitigation StrategyโOfficial Broadcom Security Updates
Section titled โOfficial Broadcom Security UpdatesโBroadcom released patches under VMSA-2026-0006. Administrators must immediately upgrade affected deployments:
| Product Branch | Vulnerable Range | Fixed Release | Knowledge Base |
|---|---|---|---|
| VMware vCenter Server 8.0 | >= 8.0, < 8.0 Update 3k | 8.0 Update 3k (8.0.3.01100) | KB98014 |
| VMware vCenter Server 9.0 | >= 9.0, < 9.0.2.0100 | 9.0.2.0100 | KB98015 |
| VMware Cloud Foundation 5.x | 5.0 through 5.2.1.1 | 5.2.1.2 | KB98016 |
| VMware Cloud Foundation 6.x | 6.0 through 6.0.1.0 | 6.0.1.1 | KB98017 |
Network Perimeter Isolation & Workaround
Section titled โNetwork Perimeter Isolation & WorkaroundโIf immediate patching is impossible:
- Strict Management ACLs: Block ingress on TCP ports 389, 636, 2012, and 2014 from all endpoints except designated Platform Services Controllers.
- Zero Internet Exposure: Ensure vCenter Server management interfaces are never exposed to public internet addresses.