vCenter's Directory Service Bypass Demands Patch, Then Session Hunting
vCenter's Directory Service Bypass Demands Patch, Then Session Hunting VMware vCenter is a high-value identity and virtualization control plane. CVE-2026-123890 matters because the failed component is the VMware Direct
vCenter's Directory Service Bypass Demands Patch, Then Session Hunting
VMware vCenter is a high-value identity and virtualization control plane. CVE-2026-123890 matters because the failed component is the VMware Directory Service, where an authentication mistake can affect administrative sessions rather than one isolated application.
What the advisory establishes
Broadcom rates the vulnerability 9.8 and describes it as an authentication bypass. Google Cloud's analysis identifies the affected interface as vmdir DCE/RPC and explains that predictable UUIDv1 timestamp generation exposed Secure Remote Password session keys. An unauthenticated network attacker could recover a session key without knowing a password. That is enough to make the issue more serious than a denial of service, but the public evidence does not establish that every vCenter deployment was targeted.
Fixed targets published by Broadcom include vCenter 9.1.1.0200, 9.0.2.0200, and 8.0 U3m. Additional affected products and 5.x guidance are listed in the advisory. Teams should use the vendor matrix rather than infer coverage from a build number.
Patch and verify
Inventory vCenter appliances, including management products that bundle them. Record the running build before maintenance, apply the vendor fix, and verify the new build after services restart. Check dependent products such as VMware Cloud Foundation and Telco Cloud separately.
Do not treat a successful patch as the end of response. Search centralized logs for unexpected SSO accounts, authentication events that lack a believable user session, and changes to directory or identity configuration. Preserve vmdir and vSphere audit records before retention windows remove them. Compare account creation times with maintenance and administrative schedules.
If evidence suggests key or credential exposure, rotate administrative secrets according to the vendor recovery guidance and invalidate sessions that could have been forged. Restrict vCenter management interfaces to dedicated administrative networks. Network isolation reduces opportunity, but it does not replace the fix.
Detection questions
Ask which accounts can administer SSO, whether new accounts appeared near the disclosure date, and which systems can reach vCenter management services. Review service accounts that were used interactively and certificates issued to vCenter components.
The investigation should distinguish three facts: a vulnerable build existed, an attacker reached the interface, and an administrative session was forged. Each conclusion needs separate evidence. A scan match alone proves only the first.
References
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes โ full credit and traffic to the original publisher.