VMware vCenter Update Adds Four New CVEs Alongside Exploited Authentication Bypass
Our earlier advisory covered CVE-2026-123890, a critical authentication bypass in VMware vCenter. The Cyber Centre bulletin AV26-1185, dated 19 November 2026, widens that scope. Broadcom's VMSA-2026-0009 now groups four further flaws alongside it, CVE-2026-123891, CVE-2026-123892, CVE-2026-123893 and CVE-2026-123894, with fixes delivered for vCenter, VMware Tools and SDDC Manager. Affected builds span Cloud Foundation and vSphere Foundation vCenter 9.1.x below 9.1.1.0200 and 9.0.x below 9.0.2.0200, standalone vCenter 8.0 below 8.0 U3m and the entire 7.0 line, Cloud Foundation vCenter 5.x below 5.2.5, Telco Cloud Platform vCenter 3.0, 4.x, 5.0.x, 5.1.x and 5.2, and Telco Cloud Infrastructure vCenter 3.0.
Neither the Cyber Centre bulletin nor the vendor advisory describes how the four newly named issues are triggered, so no exploitation chain can be stated here. What is established is scope. All five CVEs are addressed in a single coordinated release covering vCenter, and the 7.0 branch appears on the affected list without a fixed build of its own. Open source reporting cited in the bulletin indicates CVE-2026-123890 is exploited in the wild.
CISA added CVE-2026-123890 to its Known Exploited Vulnerabilities catalogue on 20 November 2026, confirming real world abuse. FIRST EPSS places that flaw at a 3.0% probability of exploitation within 30 days, while the four new CVEs sit at 0.4%, 0.6%, 0.2% and 0.1%. No exploitation has been reported for those four. vCenter brokers authentication and administration for every connected ESXi host, so a compromise there cascades across the virtual estate, and Telco Cloud deployments extend that exposure into carrier infrastructure.
Attack Surface
Infrastructure, System Management Service, Cloud Service
Tactics
Initial Access, Privilege Escalation, Credential Access
Techniques
- T1190 – Exploit Public-Facing Application
- T1078 – Valid Accounts
- T1068 – Exploitation for Privilege Escalation
SuperPRO's Threat Countermeasures Procedures
- Update VMware Cloud Foundation and vSphere Foundation vCenter 9.1.x to build 9.1.1.0200 or later, and 9.0.x to 9.0.2.0200 or later, as listed in Broadcom advisory VMSA-2026-0009 for CVE-2026-123890 through CVE-2026-123894.
- Update standalone VMware vCenter 8.0 to 8.0 U3m or later, and VMware Cloud Foundation vCenter 5.x to 5.2.5 or later; vCenter 7.0 is named as affected with no fixed build in VMSA-2026-0009, so plan a move to 8.0 U3m or the 9.x line.
- Apply the vCenter fixes covering VMware Telco Cloud Platform vCenter 3.0, 4.x, 5.0.x, 5.1.x and 5.2, and Telco Cloud Infrastructure vCenter 3.0, following the async patch guidance in VMSA-2026-0009 rather than the standard vCenter installer.
- Install the VMware Tools and SDDC Manager updates shipped in the same VMSA-2026-0009 bundle, as the four newly named CVEs (CVE-2026-123891, CVE-2026-123892, CVE-2026-123893, CVE-2026-123894) are fixed across those components, not vCenter alone.
- Because CVE-2026-123890 is KEV-listed, restrict inbound TCP/443 and TCP/5480 access to vCenter Server Appliance management interfaces to named administrative jump hosts or VPN ranges, and drop direct internet exposure of the vSphere Client.
- Audit vCenter Single Sign-On for accounts, solution users and permissions added before patching, and review /var/log/vmware/sso/ and /var/log/vmware/vpxd/vpxd.log for successful authentications without a matching SSO token issuance.
- Alert in EDR or syslog on new SSH sessions, shell enablement (shell.set –enabled true) or unexpected service restarts on the vCenter Server Appliance, and rotate vCenter administrator, ESXi root and vpxuser credentials on any appliance that was internet-facing while unpatched.