CVE-2026-123890: VMware vCenter Directory Service SRP Authentication Bypass
- Vendor
- VMware
CVE-2026-123890 is a critical authentication-bypass vulnerability in VMware vCenter Server's VMware Directory Service daemon, vmdird. An unauthenticated attacker can obtain an SRP-6a session key through the service's DCE/RPC interface on TCP port 2012, bypass password verification, and establish an authenticated session as the built-in vCenter SSO administrator. The vulnerability affects vCenter 9.1.x before 9.1.1.0200, 9.0.x before 9.0.2.0200, 8.0 before 8.0 U3m, and 7.0, including affected deployments bundled with VMware Cloud Foundation, vSphere Foundation, and Telco Cloud products. It has a CVSS v3.1 score of 9.8. ARMORY CASTLE exploited the vulnerability as a zero-day beginning in early September 2026. It is distinct from CVE-2026-59309; installing the earlier vulnerability's fix does not address this issue.
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 compromises vCenter authentication and can grant administrative control over the managed virtualization environment, threatening confidentiality, integrity, and availability. Observed post-exploitation activity included directory database extraction, credential and STS SAML signing-key theft, creation of persistent SSO administrator accounts, command execution, and access to ESXi hosts and guest virtual-machine data. Stolen signing material can support Golden SAML token forgery, privileged-user impersonation, and potential MFA bypass. ESXi hosts are not directly affected by this vulnerability but can be compromised through attacker control of vCenter. Patching alone does not revoke stolen credentials or signing keys or remove attacker-created accounts.
Mitigation
If you can’t patch tonight, do this now.
No vendor-supported workaround is available. Pending patching, isolate vCenter management interfaces and use network-enforced allowlists to restrict TCP 2012 and other management ports, including 443, 5480, 22, 389, and 636, to trusted administration systems. Restrict unnecessary outbound Internet access from vCenter. Do not rely solely on the appliance management interface firewall, which an attacker with sufficient access can disable. Monitor unexpected TCP 2012 connections, unauthorized SSO or machine accounts, new administrative grants, abnormal SAML sessions, SSH enablement and disablement, and unauthorized ESXi SSH keys. Network restrictions reduce exposure but do not replace patching.
Remediation
Patch, then assume compromise.
Apply the applicable cumulative updates specified in Broadcom advisory VMSA-2026-0009 immediately: vCenter 9.1.x to 9.1.1.0200, vCenter 9.0.x to 9.0.2.0200, and vCenter 8.0 to 8.0 U3m. For VMware Cloud Foundation 5.x, update to 5.2.5 and apply the vCenter correction using the asynchronous patching guidance in KB88287. For affected Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x, and 5.2, and Telco Cloud Infrastructure 3.0, follow KB463116 for the vCenter 8.0 U3m correction. vCenter 7.0 has no generally available public fix; extended-support customers should contact Broadcom Support. These cumulative fixes cannot be installed using vCenter Quick Patch. Review supported upgrade paths before installation, including restrictions affecting migration from 8.0 U3m or 9.0.2.0200 to VMware Cloud Foundation 9.1.1. Investigate potential compromise dating back to early September 2026. If compromise is identified, remove unauthorized access and rotate SSO credentials, STS SAML signing material, the vCenter master key, and database credentials using version-specific Broadcom guidance.
Exploits
No validated public exploits yet. Hidden: 7 rejected by Mallory's analysis as not a working exploit.
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.
References
Frequently asked questions
- Is CVE-2026-123890 exploited in the wild?
- Yes. As of Nov 22, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Nov 20, 2026.
- Is there a public exploit for CVE-2026-123890?
- Yes. As of Nov 22, 2026, Mallory has reports of a public exploit for CVE-2026-123890.
- Is there a patch for CVE-2026-123890?
- Apply the applicable cumulative updates specified in Broadcom advisory VMSA-2026-0009 immediately: vCenter 9.1.x to 9.1.1.0200, vCenter 9.0.x to 9.0.2.0200, and vCenter 8.0 to 8.0 U3m. For VMware Cloud Foundation 5.x, update to 5.2.5 and apply the vCenter correction using the asynchronous patching guidance in KB88287.
- What products are affected by CVE-2026-123890?
- Vmware Vcenter Server, Vmware Telco Cloud Infrastructure, and Vmware Telco Cloud Platform.
- How severe is CVE-2026-123890?
- CVE-2026-123890 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 3.0% (88th percentile) as of Nov 22, 2026.
Recent activity
259 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.