Check these three things.
-
System owner: confirm each vCenter runs at least the fixed build for its release line: 8.0 U3m, 9.0.2.0200, 9.1.1.0200, or 5.2.5 in VMware Cloud Foundation 5.x.
Affected versions and fixes
- Affected, from Broadcom's advisory and the CVE record:
- vCenter 9.1.x before 9.1.1.0200.
- vCenter 9.0.x before 9.0.2.0200.
- vCenter 8.0 before 8.0 U3m.
- vCenter in VMware Cloud Foundation 5.x before 5.2.5.
- vCenter 7.0 is also affected. Broadcom offers its fix only through an extended support contract. vSphere 7 reached End of General Support on October 2, 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. Broadcom points to its article KB463116 for their fix.
- Broadcom lists no workaround.
- Record for each vCenter:
- Installed version and build.
- Source of that record.
- Date checked.
- Affected, from Broadcom's advisory and the CVE record:
-
Network owner: check which systems can reach vCenter's directory service on TCP port 2012.
When the risk applies
- Broadcom: an attacker with network access to vCenter may bypass authentication and gain unauthorized access. No login is needed.
- Google Threat Intelligence Group says the flaw is reached through the vCenter directory service on port 2012 and gives a session as the built-in administrator, administrator@vsphere.local.
- In the case Google describes, the attackers reached vCenter from other internal systems they had already broken into. vCenter does not need to face the Internet to be at risk.
- The CVSS vector includes AV:N, meaning network-reachable, including internal networks. It is not proof of Internet exposure.
- A vCenter that ran an affected version while port 2012 was reachable was exposed for that time, even if it is fixed now.
-
Security owner: look in logs for new vCenter administrator accounts and for SSH being turned on, even if it is off now.
What the records can show
- Signs Google reported from the campaign it investigated:
- A new local administrator account in vsphere.local.
- SSH turned on through the appliance management interface (VAMI, port 5480), then turned off again.
- Tools placed in /tmp on a separate internal Linux appliance.
- Internal scans for ports 443, 2012 and 389.
- Records to review:
- vCenter single sign-on and audit logs.
- Appliance management (VAMI) logs.
- Firewall logs for connections to port 2012.
- Limits:
- Clean records do not prove no attack happened.
- Missing records leave the question open.
- Patching does not remove an attacker who is already inside.
- Signs Google reported from the campaign it investigated:
If records show a break-in, start incident response now. Update vCenter whether or not port 2012 appears restricted.
Do Now
- System owner: update vCenter to 8.0 U3m, 9.0.2.0200 or 9.1.1.0200 or later in its release line, or VMware Cloud Foundation 5.x to 5.2.5 or later.
Proof the update is done
- Completion evidence for each vCenter:
- Version and build installed after the update.
- Source of that record.
- Date checked.
- For vCenter 7.0, ask Broadcom support for the fix under an extended support contract, or plan the upgrade.
- Completion evidence for each vCenter:
- Network owner: until the update is done, allow port 2012 on vCenter only from systems that need it.
What to know
- Broadcom lists no workaround. Restricting access lowers who can reach the flaw. It is not the fix.
- Google notes the vCenter appliance firewall is managed through VAMI on port 5480, and an attacker who gains VAMI access with a sufficient role can turn it off. Apply the restriction with network controls outside vCenter as well.
Do Next
- System owner: update SDDC Manager and VMware Tools for Windows from the same advisory.
What to update
- Follow Broadcom VMSA-2026-0009.1 for the fixed releases for CVE-2026-123891, CVE-2026-123892 and CVE-2026-123893 in SDDC Manager, and CVE-2026-123894 in VMware Tools for Windows.
- Security owner: recheck CISA and Broadcom for changes to the exploitation status.
What to recheck
- The CISA Known Exploited Vulnerabilities (KEV) catalog. CISA added CVE-2026-123890 on November 20, 2026 (catalog 2026.11.20), due November 23, 2026.
- CISA's assessment in the CVE record, updated November 20, 2026.
- Broadcom advisory VMSA-2026-0009 and its FAQ.
- Date of each recheck.
Check your own records.
- Use your approved AI tool.
- Require evidence. Flag unknowns.
Read the prompt
The reported finding
vCenter directory service authentication bypass (CVE-2026-123890)
Original advisory →- Required conditions
- vCenter 9.1.x before 9.1.1.0200, 9.0.x before 9.0.2.0200, 8.0 before 8.0 U3m, VMware Cloud Foundation 5.x before 5.2.5, or 7.0, with network access to the VMware Directory Service.
- Reported outcome
- Broadcom: authentication bypass giving unauthorized access; CVSS 3.1 9.8 Critical; no workaround. Broadcom says someone with network access to an affected vCenter may bypass authentication. Google Threat Intelligence Group reports that the flaw can grant administrator access.
Fix guidance
- Broadcom VMSA-2026-0009.1, issued November 19 and updated November 20, 2026: fixed in vCenter 9.1.1.0200, 9.0.2.0200 and 8.0 U3m, and in VMware Cloud Foundation 5.2.5. No workaround.
- vCenter 7.0 is affected, with fixes only through extended support (Broadcom FAQ). Telco Cloud Platform and Telco Cloud Infrastructure: Broadcom KB463116.
- Exploitation report: Google Threat Intelligence Group, November 19, 2026, says the suspected PRC-nexus espionage group ARMORY CASTLE (formerly UNC5221) exploited this flaw in early September 2026, according to forensic evidence. It reached vCenter from internal systems it had already compromised. Broadcom credits Mandiant with reporting the flaw. Broadcom's advisory was silent on exploitation when reviewed on the morning of November 20, 2026.
- Exploitation status: CISA (@CISAgov) added CVE-2026-123890 to its KEV catalog on November 20, 2026, with a catalog due date of November 23, 2026. Known ransomware use: Unknown. CISA's entry asks for forensic triage. CISA SSVC in the CVE record, November 20, 2026: Exploitation active, Automatable yes, Technical Impact total.
- Follow Broadcom VMSA-2026-0009.1 for the fixed releases for CVE-2026-123891, CVE-2026-123892 and CVE-2026-123893 in SDDC Manager, and CVE-2026-123894 in VMware Tools for Windows.
What IntegrityLab.ai can check
- This advisory does not mean IntegrityLab.ai detects CVE-2026-123890.
- When enabled for an authorized assessment, IntegrityLab.ai's discovery records reachable web services and the server name they return. This gives your administrator a starting point. It does not currently offer a validated check for this CVE, a port 2012 test, confirmation of the installed build, or proof of compromise.
- If vCenter sits on an internal network, an external assessment that does not see it does not show it is unreachable from inside.