News
vCenter login can be skipped from the network, with no listed workaround.
Broadcom says a flaw in VMware Directory Service lets someone with network access skip vCenter authentication. Fixed builds are out, the company lists no workaround, and it has not reported attacks.

Impact
- What was impacted
- VMware vCenter's VMware Directory Service, tracked as CVE-2026-123890 and rated 9.8. An attacker with network access can bypass authentication and gain unauthorized access. Broadcom does not say what level of access that is. The same advisory fixes four more flaws rated 6.7 to 8.1: SQL injection CVE-2026-123891 and command injection CVE-2026-123892 in SDDC Manager, privilege escalation to root on the SDDC Manager appliance as CVE-2026-123893, and a SAML token signature bypass in VMware Tools for Windows as CVE-2026-123894. Each of those four needs an authenticated or already privileged actor. The Tools flaw is exploitable only where Guest Alias mapping is configured, and it stays inside the guest virtual machine. None of the five flaws lets code run on an ESX host from inside a virtual machine, and ESX itself is not affected.
- Who was impacted
- Operators of vCenter 8.0, 9.0, and 9.1, including the vCenter builds that ship inside VMware Cloud Foundation (including the 5.x line), vSphere Foundation, Telco Cloud Platform, and Telco Cloud Infrastructure. Enhanced Linked Mode does not change whether the bug is present. vSphere 6.5 and 6.7 should be presumed affected, because Broadcom no longer evaluates versions past end of support. vSphere 7.0, which left general support in October 2025, should also be presumed affected. Customers on an extended support contract can request a patch. The Tools flaw matters where Guest Alias mapping is configured on Windows guests. The SDDC Manager flaws matter for those appliances.
- What you need to do
- Install Broadcom's fixed builds for the supported branch. The company lists no workaround. Treat the change as an emergency and decide timing with your security staff. Do not install these updates through vCenter Quick Patch. Virtual machines keep running, management access drops briefly, and some encryption operations against a Standard Key Provider are unavailable until vCenter is back. If an upgrade to VMware Cloud Foundation 9.1.1 is still ahead, do not install vCenter 8.0 U3m or 9.0.2.0200 first. That blocks the later 9.1.1 upgrade. Upgrade vCenter to 9.1.1 and apply the security update there, or wait for VCF 9.1.2. This report does not print a full fixed-version matrix, so take any other build numbers from the Broadcom advisory. Broadcom has not reported attacks or public exploit code for CVE-2026-123890.
Broadcom published an advisory for CVE-2026-123890, an authentication bypass in the VMware Directory Service, rated 9.8. Someone with network access can skip authentication and reach vCenter without authorization. vCenter is the console that manages an organization's ESX hosts and virtual machines. The company does not say what access the attacker has after the bypass. It has not reported attacks or public exploit code. Google-owned Mandiant reported the bug. In an FAQ with the advisory, Broadcom says the issue qualifies under ITIL as an emergency change and tells organizations to consult their security staff immediately on timing.
The bug is in vCenter 8.0, 9.0, and 9.1, and in the vCenter builds that ship inside VMware Cloud Foundation, vSphere Foundation, Telco Cloud Platform, and Telco Cloud Infrastructure, including Cloud Foundation 5.x. Enhanced Linked Mode does not matter. Older lines are not cleared. Broadcom no longer evaluates versions past end of support and says vSphere 6.5 and 6.7 should be presumed affected. The same applies to vSphere 7.0, which left general support in October 2025. Customers on an extended support contract can request a patch. Fixed versions are out for every supported branch. Asked whether a workaround exists, the FAQ answers that none is listed by Broadcom, while noting that an organization may still have mitigations of its own.
The updates are cumulative and cannot be installed through vCenter Quick Patch. Virtual machines keep running while vCenter updates. Management access drops briefly, and some encryption operations against a Standard Key Provider are unavailable until vCenter is back online. One warning covers upgrades already in progress: installing vCenter 8.0 U3m or 9.0.2.0200 blocks a later upgrade to VMware Cloud Foundation 9.1.1, which the FAQ calls a Back-in-Time issue. The options are to upgrade vCenter to 9.1.1 first and apply the security update there, or to wait briefly for VCF 9.1.2. This report does not print a full table of fixed build numbers.
This is the second critical authentication flaw in the VMware Directory Service this year. The earlier vCenter flaws, patched on July 29, included CVE-2026-59309, another bypass in the same component rated 9.8, and a directory-traversal bug, CVE-2026-59310. Attacks on that traversal started five days after disclosure. In August, the German incident response firm QUIRSO linked them, with moderate confidence, to a suspected China-nexus actor. Those attacks compromised an estimated 361 IP addresses in 47 countries and deployed Babuk-derived ransomware on ESXi hosts. Broadcom has reported no attacks on the new bypass.
The same advisory fixes four lower-severity flaws, rated 6.7 to 8.1. CVE-2026-123891 is SQL injection in SDDC Manager. CVE-2026-123892 is command injection in SDDC Manager. CVE-2026-123893 is privilege escalation to root on the SDDC Manager appliance. CVE-2026-123894 is a SAML token signature bypass in VMware Tools for Windows, and it is exploitable only where Guest Alias mapping is configured. Each of those four needs someone who is already authenticated or already privileged, and the Tools flaw stays inside the guest virtual machine. None of the five flaws in the advisory lets code run on an ESX host from inside a virtual machine, and ESX itself is not affected.
For your AI agent
Agent instructions — copy paste to Claude
You are helping me respond to CVE-2026-123890, an authentication bypass in VMware Directory Service on vCenter, rated 9.8. Do not write or run an exploit or a proof of concept. Do not probe vCenter login in a way that tries to skip authentication. Facts from the report: - Broadcom says an attacker with network access can bypass authentication and gain unauthorized access. The report does not say what level of access that is. Do not assume administrator, and do not assume a low-privilege session. - Broadcom has not reported attacks or public exploit code. Mandiant reported the bug. The FAQ says the issue qualifies under ITIL as an emergency change and says to consult security staff immediately on timing. - Affected: vCenter 8.0, 9.0, and 9.1, including vCenter inside VMware Cloud Foundation (including the 5.x line), vSphere Foundation, Telco Cloud Platform, and Telco Cloud Infrastructure. Enhanced Linked Mode does not change this. - vSphere 6.5 and 6.7 should be presumed affected. vSphere 7.0 left general support in October 2025 and should be presumed affected. Customers on an extended support contract can request a patch. Do not invent a 7.0 build number. - Fixed versions are out for all supported branches. This report does not print a full fixed-version matrix. If the Broadcom advisory in front of you names a build, use that number. If it does not, say this report did not name one. - No workaround is listed by Broadcom. Do not invent a firewall rule or a feature flag and present it as Broadcom's workaround. An organization may still have its own network controls. Ask before changing them. - Updates are cumulative and cannot be installed through vCenter Quick Patch. Virtual machines keep running. Management access drops briefly. Some encryption operations against a Standard Key Provider are unavailable until vCenter is back. - Installing vCenter 8.0 U3m or 9.0.2.0200 blocks a later upgrade to VMware Cloud Foundation 9.1.1. If that upgrade is still ahead, upgrade vCenter to 9.1.1 first and apply the security update there, or wait for VCF 9.1.2. Do not treat 8.0 U3m or 9.0.2.0200 as a build to install when 9.1.1 is the planned next step. - The same advisory also fixes CVE-2026-123891 (SQL injection, SDDC Manager), CVE-2026-123892 (command injection, SDDC Manager), CVE-2026-123893 (privilege escalation to root on the SDDC Manager appliance), and CVE-2026-123894 (SAML token signature bypass in VMware Tools for Windows, only where Guest Alias mapping is configured, and it stays inside the guest). Each of those four needs an authenticated or already privileged actor. Scores are from 6.7 to 8.1. The report does not assign each score to a CVE. Do not invent the mapping. - None of the five flaws lets code run on an ESX host from inside a virtual machine. ESX itself is not affected. - An earlier Directory Service bypass, CVE-2026-59309, and a traversal, CVE-2026-59310, were patched on July 29, 2026. Attacks on the traversal are a separate incident. Do not treat those attacks as evidence that CVE-2026-123890 is being exploited. Context: - What was impacted: vCenter authentication through VMware Directory Service, plus four lower-severity flaws in SDDC Manager and VMware Tools for Windows. - Who should care: operators of vCenter 8.0, 9.0, and 9.1 and the named Cloud Foundation, vSphere Foundation, and Telco products, plus anyone still on vSphere 6.5, 6.7, or 7.0. - What to do: apply the vendor fixed build for the supported branch, avoid Quick Patch, and avoid 8.0 U3m or 9.0.2.0200 if a move to VCF 9.1.1 is still planned. Do this in order. Ask before installing updates, changing network access to vCenter, or rebooting management services. Prefer read-only inventory first. Do not write or run an exploit or a proof of concept. 1. Inventory - List vCenter instances and record the version and whether they sit inside VMware Cloud Foundation, vSphere Foundation, Telco Cloud Platform, or Telco Cloud Infrastructure. Note Enhanced Linked Mode only as context. It does not clear the bug. - Flag vSphere 6.5, 6.7, and 7.0 as presumed affected. For 7.0, note whether an extended support contract is in place. Do not invent a patch build. - Record whether an upgrade to VMware Cloud Foundation 9.1.1 is still planned. If it is, 8.0 U3m and 9.0.2.0200 are the builds this report says will block that upgrade. - Record SDDC Manager presence, and whether any Windows guest uses VMware Tools with Guest Alias mapping. - If a Broadcom advisory in front of you names the fixed build for this version, record that number. If it does not, say this report did not name a full matrix. 2. Contain - Broadcom lists no workaround. If vCenter management is reachable from networks that should not reach it, propose limiting that access and ask before changing firewall or access rules. State that this is your own control, not a vendor workaround, and that it does not replace the update. 3. Remediate - Plan the cumulative vendor update for the supported branch. Do not use vCenter Quick Patch. Ask before installing. - Warn that virtual machines keep running, management access drops briefly, and some Standard Key Provider encryption operations pause until vCenter is back. - If VCF 9.1.1 is still ahead, plan to upgrade vCenter to 9.1.1 and apply the security update there, or to wait for VCF 9.1.2. Ask before choosing. - Include the four lower-severity fixes in the same update plan. Do not treat them as a reason to delay the authentication bypass. 4. Verify - Confirm the running vCenter build matches the fixed build you intended, and that management access returned. - Note any Standard Key Provider operations that were paused, and whether they recovered. 5. Report back - Versions found, whether management was exposed beyond the networks you expect, which update path you used, and any end-of-support systems that still have no build named in this report. Do not invent CVEs, build numbers, or exploit conditions. If a check needs access I have not given you, say what you need and stop.