Skip to main content
All incident reports
Incident report

Broadcom issues fixes for critical VMware vCenter authentication bypass

Broadcom has published an advisory for CVE-2026-123890, a 9.8-rated authentication bypass in VMware vCenter's Directory Service that lets an attacker with network access into the management console. Fixed builds are available for supported branches, and the company says it has seen no attacks.

· First published

The short version

  • The flaw. CVE-2026-123890 is rated 9.8 and sits in the VMware Directory Service inside vCenter, the console used to manage ESX hosts and virtual machines. An attacker who can reach it over the network can bypass authentication and gain unauthorised access. Broadcom credits Google-owned Mandiant with reporting it.
  • Affected products. vCenter 8.0, 9.0 and 9.1 are affected, as are the vCenter builds shipped inside VMware Cloud Foundation (including 5.x), vSphere Foundation, and the Telco Cloud Platform and Telco Cloud Infrastructure products, whether or not Enhanced Linked Mode is used. Broadcom says vSphere 6.5 and 6.7 should be presumed affected.
  • No workaround. Fixed versions exist for all supported branches and Broadcom lists no workaround. The updates are cumulative and cannot be applied through vCenter Quick Patch; virtual machines keep running but management access drops briefly.
  • Exploitation status. Broadcom reports no attacks exploiting the bypass and no public exploit code. It does not say what level of access an attacker obtains after bypassing authentication.
  • Second bypass this year. A July update fixed another 9.8-rated bypass in the same Directory Service component. Attacks later followed against a directory-traversal flaw patched at the same time, according to an assessment by German incident response firm QUIRSO.

Timeline

DateEvent
29 JulyBroadcom patches earlier vCenter flaws, including CVE-2026-59309, another 9.8-rated Directory Service authentication bypass, and a directory-traversal bug, CVE-2026-59310.
AugustQUIRSO assesses that attacks on the traversal flaw began five days after disclosure and links them with moderate confidence to a suspected China-nexus actor.
19 NovemberBroadcom publishes an advisory for CVE-2026-123890 with fixed builds for supported vCenter branches.

What the vulnerability allows

The flaw is an authentication bypass in the VMware Directory Service, a component of vCenter. Broadcom rates it 9.8 on the CVSS scale. The precondition is network access to the affected system; the advisory calls it an issue for attackers who already have that reach.

Broadcom has not said what an attacker can do once past authentication, so the practical blast radius is unconfirmed. The advisory FAQ does state boundaries: none of the five flaws it covers allows code execution on an ESX host from inside a virtual machine, and ESX itself is not affected.

Broadcom describes the update as an emergency change under ITIL and tells customers to consult security staff on timing immediately. It offers no workaround, saying only that mitigations may exist in an organisation's own defences. The same advisory fixes four lower-severity flaws rated 6.7 to 8.1, including SQL injection and command injection in SDDC Manager and a SAML token signature bypass in VMware Tools for Windows.

Who is exposed and how to sequence the update

Exposure covers the current vCenter lines and the builds bundled into several Broadcom platforms, so teams that never installed vCenter directly may still be running an affected copy inside Cloud Foundation, vSphere Foundation or the Telco Cloud products. Older, unsupported branches are not cleared: Broadcom no longer evaluates versions past end of support and says vSphere 6.5 and 6.7 should be presumed affected. vSphere 7.0 left general support in October 2025, and customers there can request a patch under an extended support contract.

One sequencing trap matters for teams mid-upgrade. Installing vCenter 8.0 U3m or 9.0.2.0200 blocks a later upgrade to VMware Cloud Foundation 9.1.1, a conflict the FAQ calls a Back-in-Time issue. The stated 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. Virtual machines continue running during the update, but management access is briefly lost and some encryption operations against a Standard Key Provider become unavailable until vCenter returns.

Earlier exploitation in the same component

This is the second critical authentication flaw in the VMware Directory Service this year. The July advisory carried another 9.8-rated bypass, CVE-2026-59309, alongside the traversal bug CVE-2026-59310. QUIRSO's August assessment was that attacks on the traversal flaw started five days after disclosure and were linked with moderate confidence to a suspected China-nexus actor. The August attacks compromised an estimated 361 IP addresses across 47 countries and deployed Babuk-derived ransomware on ESXi hosts.

That history shows how quickly vCenter flaws can be taken up in the wild, but Broadcom has reported no attacks on CVE-2026-123890 and no public exploit code, and no source connects the two sets of flaws beyond their shared component.

What is not known yet

  • What level of access an attacker gains once authentication is bypassed.
  • Whether anyone has already exploited the bypass without it being detected or reported.
  • Whether Broadcom will issue patches for vSphere 6.5 and 6.7, which it no longer evaluates.
  • How many vCenter instances are reachable from untrusted networks.
  • How long the Back-in-Time conflict will persist before VCF 9.1.2 arrives.

What to do

If you run vCenter or a platform that bundles it

  1. Apply the fixed build for your branch, taking the version and installation steps from Broadcom's advisory rather than from a summary.
  2. Treat it as an emergency change and agree timing with your security staff, as the advisory urges.
  3. Check whether your vCenter sits inside Cloud Foundation, vSphere Foundation or a Telco Cloud product, and patch that copy too.
  4. If you are on vSphere 6.5, 6.7 or 7.0, assume the system is affected and contact Broadcom about a patch under extended support.

If you are mid-upgrade to Cloud Foundation 9.1.1

  1. Do not install vCenter 8.0 U3m or 9.0.2.0200, which blocks the later Cloud Foundation upgrade.
  2. Either move vCenter to 9.1.1 first and apply the security update there, or wait briefly for VCF 9.1.2.

For everyone else

  1. Because the bypass requires network reach, restrict which networks and users can open the vCenter management interface.
  2. Schedule the update for a window that tolerates brief loss of management access and paused encryption operations against a Standard Key Provider.
  3. Watch for exploitation reporting from Broadcom or your incident response provider, since none has been confirmed yet.

Update log

  • First published.

Sources

New incident reports by email

One email a week with the reports published since the last one.

We email you about this topic only; unsubscribe any time. See our Privacy Policy.

Want us to look at your domain?

Give us one apex domain and we'll send back a written snapshot of what is already visible from outside. No call required.