CVEHit Business Advisory by IntegrityLab.ai
What should we do?
vCenter flaw lets attackers inside the network take over as administrator — CVE-2026-123890: Business Triage
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.
- 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.
← Back to article questions