Skip to content

CVE-2026-59309: VMware vCenter Server vmdir Authentication Bypass

Density:
C-Level Executive Briefing CVE-2026-59309 CRITICAL SCORE 98/100

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).

HYBRID

HERMES THREAT SCORE & VIRTUALIZATION FABRIC AUTHENTICATION INTEGRITY

Target: VMware Directory Service daemon (vmdir / vCenter Single Sign-On)
Confidence: 99%
98 / 100
CRITICAL

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 20 / 20
Threat Activity 20 / 20
Weaponization 20 / 20
Exposure 18 / 20
Prevalence 20 / 20
Impact 20 / 20
Exploit Maturity 20 / 20
Attack Chain Potential 20 / 20
โš–๏ธ Divergence & Operational Rationale

[object Object]

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 --> DC

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:

vmdir/server/ldap-head/bind.c
DWORD
VmDirProcessSaslBindRequest(
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.


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.

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).

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=local
  • cn=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:

  1. Generates administrative vCenter SAML bearer tokens.
  2. Interacts with ESXi host management daemons (hostd).
  3. Takes VM snapshots of Windows Domain Controllers to extract NTDS.dit.
  4. 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 Compromise

Telemetry from The Shadowserver Foundation and incident response investigations indicate threat actor groups are weaponizing CVE-2026-59309 across multiple intrusion campaigns:

  1. 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/).
  2. 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.
  3. 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.

title: VMware vCenter vmdir Unauthenticated Admin Promotion
id: 9a41c8f2-3901-4be1-9102-cve202659309
status: experimental
description: 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 Team
date: 2026-11-08
logsource:
category: application
product: vmware_vcenter
detection:
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_pcs
falsepositives:
- Authorized vCenter Single Sign-On replication sync between newly joined Platform Services Controllers.
level: critical
tags:
- attack.initial_access
- attack.t1190
- attack.t1078
- cve.2026.59309

  1. 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.

  2. Inspect vmdir Audit Logs: Navigate to /var/log/vmware/vmdir/ on the VCSA appliance and inspect vmdird.log and vmdird-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.

  3. Audit vCenter Single Sign-On User Accounts: Execute the dir-cli utility 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.Administrators

    Verify that every listed account corresponds to verified corporate personnel or known service accounts.

  4. Verify Guest VM Snapshot and VMDK Download History: Query /var/log/vmware/vpxd/vpxd.log for 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
  5. Examine Chained Exploit Artifacts: Check /var/log/vmware/messages and 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"

Broadcom released patches under VMSA-2026-0006. Administrators must immediately upgrade affected deployments:

Product BranchVulnerable RangeFixed ReleaseKnowledge Base
VMware vCenter Server 8.0>= 8.0, < 8.0 Update 3k8.0 Update 3k (8.0.3.01100)KB98014
VMware vCenter Server 9.0>= 9.0, < 9.0.2.01009.0.2.0100KB98015
VMware Cloud Foundation 5.x5.0 through 5.2.1.15.2.1.2KB98016
VMware Cloud Foundation 6.x6.0 through 6.0.1.06.0.1.1KB98017

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.