Affected product(s):
| Product | Affected versions | Fix |
| VMware vCenter (VCF / vSphere Foundation) | 9.1.x.x | 9.1.1.0200 |
| VMware vCenter (VCF / vSphere Foundation) | 9.0.x.x | 9.0.2.0200 |
| VMware vCenter Server | 8.0 | 8.0 U3m |
| VMware vCenter Server | 7.0 | No public patch (extended support, through the vendor’s support) |
| VMware Cloud Foundation (vCenter) | 5.x | 5.2.5 (vCenter 8.0 U3m, asynchronous patching, KB88287) |
| VMware Telco Cloud Platform (vCenter) | 3.0, 4.x, 5.0.x, 5.1.x, 5.2 | See KB463116 |
| VMware Telco Cloud Infrastructure (vCenter) | 3.0 | See KB463116 |
ESX is not affected by this advisory. The flaw is present with or without Enhanced Linked Mode. Versions 6.5 and 6.7, which are already out of support, should be presumed affected.
Description
A critical vulnerability has been reported in VMware vCenter, identified as CVE-2026-123890, that allows an attacker with network access to bypass authentication without credentials and gain unauthorized access to the system. The vendor made it public on Nov 19, 2026, in advisory VMSA-2026-0009, and assigns it CVSS 9.8, critical. This bulletin is classified as CRITICAL.
According to the vendor, the flaw is in the VMware Directory Service. An attacker with network access to vCenter could bypass authentication and obtain a session as administrator@vsphere.local, without knowing any passwords. The vendor does not publish a workaround.
Researchers report that an espionage group with a suspected nexus to China, tracked as ARMORY CASTLE, has been exploiting it as a zero-day since early September 2026, more than two months before the patch. In the only publicly described intrusion, the attacker was already inside the network after compromising a BeyondTrust Remote Support appliance (CVE-2026-102764) and used this flaw against an internal vCenter that already had the July 2026 patch for CVE-2026-59309 applied. With that session, according to the researchers, SSO administrator accounts were created, vCenter secrets were stolen and, later, ESXi hosts were accessed with credentials obtained from vCenter, not through this CVE. The vendor’s advisory does not mention exploitation. CVE-2026-123890 is a new and distinct flaw from CVE-2026-59309, covered in Alert 2026-79: having applied the July patch does not protect against this CVE. According to the researchers, the observed tool works against vCenter 7.x and 8.x; exploitation against 9.x was not documented, although the advisory does list the 9.x branches as affected.
As of the date of this bulletin, CVE-2026-123890 is not listed in the Known Exploited Vulnerabilities catalog and no public proof of concept was identified.
The same advisory fixes four other flaws, which are not the main subject of this bulletin: CVE-2026-123891, an SQL injection in SDDC Manager, CVSS 8.1, high; CVE-2026-123892, an authenticated command injection in SDDC Manager, CVSS 7.2, high; CVE-2026-123893, a local privilege escalation to root in SDDC Manager, CVSS 6.7, medium; and CVE-2026-123894, a SAML token signature bypass in VMware Tools for Windows, CVSS 6.7, medium, which remains confined to the virtual machine. None of them allows escaping from a VM to the host.
Mitigation
Inventory VMware vCenter instances, including those that are part of VMware Cloud Foundation, vSphere Foundation, Telco Cloud Platform and Telco Cloud Infrastructure, together with their version. ESX does not require an update for this advisory.
The fix is to update to the versions listed in Solution, starting with vCenter instances reachable from untrusted networks. There is no vendor workaround.
As an exposure-reduction measure, and not as a vendor workaround, restrict network access to vCenter — including port 2012/TCP, as well as 443, 22 and 5480 — to trusted management hosts only. Researchers identify port 2012 as part of the exploitation path; the vendor’s advisory does not mention it. According to the researchers, the management interface (VAMI) firewall alone is not sufficient.
Review vsphere.local for new or unknown SSO administrator accounts, and VAMI logs for SSH being turned on or off on vCenter. Unexpected connections to port 2012/TCP and the indicators published by the researchers should also be reviewed. The patch does not undo a prior compromise. If there are signs of compromise, treat it as an incident and consider rotating the STS signing certificate and SSO credentials, because forged tokens could remain valid after the patch; this rotation is a general incident-response recommendation, not an official vendor step.
Solution
The solution is to update to the versions published by the vendor, or to a later one:
- VMware vCenter on VCF or vSphere Foundation 9.1.x: 9.1.1.0200.
- VMware vCenter on VCF or vSphere Foundation 9.0.x: 9.0.2.0200.
- VMware vCenter Server 8.0: 8.0 U3m.
- VMware Cloud Foundation 5.x: 5.2.5, applying vCenter 8.0 U3m through asynchronous patching (KB88287).
- VMware Telco Cloud Platform and Telco Cloud Infrastructure: according to KB463116.
- VMware vCenter Server 7.0: there is no public patch; customers with extended support must request it from the vendor’s support. The vendor recommends migrating to VCF 9.1.
There is no workaround. The patches are cumulative, include the fixes from VMSA-2026-0008 and are not eligible for vCenter Quick Patch; they can be applied through the VAMI. Installing vCenter 8.0 U3m or 9.0.2.0200 blocks a later upgrade to VCF 9.1.1 (a “Back-in-Time” restriction): wait for VCF 9.1.2, or first upgrade vCenter to 9.1.1 and apply the patch there. For third-party integrated systems, follow that vendor’s guidance. Virtual machines continue to run during the update, with a brief interruption of management.
In the same advisory, SDDC Manager should also be updated to 9.1.1.0200, 9.0.2.0100 or 5.2.5, according to the branch, and VMware Tools for Windows to 13.1.5.0 (13.x branch) or 12.5.5 (12.x and 11.x branches; 12.4.10 for 32-bit Windows). Back up the configuration before updating.
For information on how to update, visit the following link:
Additional information:
- Vendor — VMSA-2026-0009:
https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39495 - Vendor — VMSA-2026-0009 questions and answers:
https://brcm.tech/vmsa-2026-0009-qna - Vendor — asynchronous patching for VMware Cloud Foundation 5.x (KB88287):
https://knowledge.broadcom.com/external/article?legacyId=88287 - Vendor — VMware Telco Cloud (KB463116):
https://knowledge.broadcom.com/external/article/463116 - Researchers — exploitation analysis:
https://cloud.google.com/blog/topics/threat-intelligence/armory-castle-exploits-vsphere - NVD — CVE-2026-123890:
https://nvd.nist.gov/vuln/detail/CVE-2026-123890 - Known Exploited Vulnerabilities catalog:
https://www.cisa.gov/known-exploited-vulnerabilities-catalog - Alert 2026-79 — July 2026 vCenter vulnerabilities (a different flaw):
https://beaconlab.us/en/publication/alert-2026-79-critical-vulnerabilities-in-vmware-vcenter-esxi-workstation-and-fusion/