VMware vCenter: authentication bypass (CVE-2026-123890) reported exploited as zero-day, fixed in 8.0 U3m, 9.0.2.0200, 9.1.1.0200
CVE-2026-123890 CVE-2026-123891 CVE-2026-123892 CVE-2026-123893 CVE-2026-123894
Published 19/11/2026 17:19 · Updated 19/11/2026 17:27 (revision 2)
Timeline
5 events over 1 h
- 19/11/2026 15:31UnconfirmedCommunity post+56 min
- 19/11/2026 16:27CorroboratedCommunity post+51 min
- 19/11/2026 17:19Published on WatchtowerPro CISO+4 min
- 19/11/2026 17:24Confirmedsupport.broadcom.com+3 min
- 19/11/2026 17:27UpdatedBroadcom's advisory VMSA-2026-0009 was read directly. It confirms the vCenter…
In short
Broadcom's advisory VMSA-2026-0009 of 19/11/2026 confirms an authentication bypass in VMware vCenter (CVE-2026-123890, CVSS 9.8) that an attacker with network access can use to gain unauthorized access; the advisory also fixes four lesser flaws in SDDC Manager and VMware Tools for Windows. A researcher's post says the flaw was exploited as a zero-day by a China-linked espionage actor, but this is second-hand. Update vCenter to 8.0 U3m, 9.0.2.0200 or 9.1.1.0200 as an emergency change.
Shodan recognises at least 556 internet-facing VMware vCenter servers worldwide, 72 of them in the EU (19/11/2026); the real number is likely higher, and how many run an affected version is not yet known.
How bad is it
Critical. An attacker who can reach a vulnerable vCenter server over the network can get in without a password, with no user interaction; exploitation by a espionage actor is reported.
Confirmed by the vendor or a CERT - no exploitation reported yet.
Severity score
The worst of 5 CVEs · CVSS 3.1 from NVD, from vmware.com, read 19/11/2026.
What an attacker needs
- Internet access to itEnough
- A loginNot needed
- A user to clickNo
- Special settingsNo
Red helps the attacker, blue holds them back, grey is not published yet.
If it works, an attacker can
- Read the data it holds
- Change or delete that data
- Take it offline
Type: authentication bypass.
A score is the worst case for the flaw, not a verdict on any one system. How we score · ReconX customers see which of their own systems are affected.
Affected versions
- VMware vCenter (CVE-2026-123890, in the VMware Directory Service): 9.1.x before 9.1.1.0200, 9.0.x before 9.0.2.0200 and 8.0 before 8.0 U3m. The CVE record also lists 5.x before 5.2.5 (VCF 5.x). The flaw is present whether or not Enhanced Linked Mode is used.
- SDDC Manager and VCF Installer (CVE-2026-123891, CVE-2026-123892, CVE-2026-123893): 9.1.x.x before 9.1.1.0200, 9.0.x.x before 9.0.2.0100 and 5.x before 5.2.5.
- VMware Tools for Windows (CVE-2026-123894): 13.x.x.x before 13.1.5.0 and 12.3.x before 12.5.5.
- vCenter 7.0 is not listed in the advisory, but the FAQ says to presume it is affected (vSphere 7 reached End of General Support on 02/10/2025).
- Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x and 5.2, and Telco Cloud Infrastructure 3.0, are affected; the CVE record points to KB463116.
- The FAQ states that ESX is not affected.
Fixed in
- VMware vCenter (CVE-2026-123890): 9.1.1.0200 (9.1 branch), 9.0.2.0200 (9.0 branch), 8.0 U3m (8.0 branch). On VCF 5.x apply 8.0 U3m through the asynchronous patching guide KB88287.
- SDDC Manager and VCF Installer: 9.1.1.0200 (9.1 branch), 9.0.2.0100 (9.0 branch), 5.2.5 (5.x branch). Patches are cumulative, and 9.1.1.0200 contains the fixes for CVE-2026-123891, CVE-2026-123892 and CVE-2026-123893.
- VMware Tools for Windows (CVE-2026-123894): 13.1.5.0 (13.x) and 12.5.5 (12.x).
- Telco Cloud Platform and Telco Cloud Infrastructure: see KB463116.
What to do now
- Treat the vCenter update as an emergency change, as the FAQ advises.
- Update vCenter to 8.0 U3m, 9.0.2.0200 or 9.1.1.0200, depending on your release line. Apply it through the VAMI, not Quick Patch.
- On VCF 5.x, apply vCenter 8.0 U3m using the asynchronous patching process in KB88287 and update SDDC Manager to 5.2.5.
- Update SDDC Manager to 9.0.2.0100 or 9.1.1.0200 on the 9.x branches.
- Update VMware Tools for Windows to 13.1.5.0 (13.x) or 12.5.5 (12.x).
- If you run vCenter 7.0, presume it is affected and request patches through the extended support process if you have it.
- Note the known "Back-in-Time" issue with upgrades in progress when the update is applied.
- No workaround for CVE-2026-123890 was clearly stated in the advisory text found in the signals.
ReconX customers see the full notice - and their own systems
Our customers are alerted at every phase. Until a patch exists, the ReconX agent watches their servers from the inside for anomalies, and our outside view - the attacker's view - shows which systems to fix first.
In ReconX: the full analysis, 4 open questions, followed up as sources answer, all 3 sources with their dates and every revision. And technology matching: which of your systems run VMware vCenter, at which version, fixed or not - and what each one needs.
Main sources
CVE Record: CVE-2026-123890 Research · Julian-Ferdinand Vögele Community · cR0w Community