Skip to content
Security & Trust

VMware vCenter login flaw rated 9.8 has no workaround from Broadcom

CVE-2026-123890 lets someone with network access skip authentication on the console that manages virtual machines

W
WebPulse Newsroom
AI-assisted · 4 min read
Share on X LinkedIn
VMware vCenter login flaw rated 9.8 has no workaround from Broadcom
In brief
  • Broadcom's advisory VMSA-2026-0009 fixes CVE-2026-123890, a 9.8-rated login bypass in VMware vCenter that needs only network access to the console.
  • Broadcom lists no workaround, reports no attacks, and says the fix cannot use vCenter Quick Patch.
  • Teams should check vCenter builds, including those inside Cloud Foundation, and review who can reach the console on the network.

One console holds the keys

Most organisations that run VMware manage their virtual machines from one place. That place is vCenter. A flaw in its login check matters more than a typical bug. So much trust sits behind that one screen.

On November 19, 2026, Broadcom published advisory VMSA-2026-0009. Its most serious item is a login bypass in vCenter.

What Broadcom disclosed

The flaw is tracked as CVE-2026-123890. It sits in the VMware Directory Service, the part of vCenter that deals with identity. An attacker who can reach vCenter over the network can get in without a valid login. The advisory scores it 9.8 on version 3.1 of the CVSS scale.

According to The Hacker News, the bug sits in three vCenter release lines: 8.0, 9.0 and 9.1. It also sits in the vCenter builds bundled with VMware Cloud Foundation, including the older 5.x line. The same goes for vSphere Foundation and the two Telco Cloud products.

Some teams hope that skipping Enhanced Linked Mode, which joins several vCenters together, keeps them clear. Broadcom's answer is no. The problem lies in vCenter itself, so turning that feature off does not remove it.

Broadcom lists no workaround. Asked if one exists, its FAQ answers "Not as listed by Broadcom." It adds that a firewall or other defenses in your own setup may help. Each organisation must decide whether to rely on them. Broadcom says the issue "qualifies under ITIL methodologies as an emergency change."

What is not yet known

The Hacker News reports that Broadcom has described no attacks on this flaw and no public exploit code. The advisory also leaves open how much access an intruder gets once past the login. The report credits Google-owned Mandiant with finding the bug.

Those gaps matter. A leader cannot judge the damage from the advisory alone. The sensible reading is to treat the console as exposed until it is patched.

The same component, twice this year

The Hacker News points out that this is the second critical login flaw in the Directory Service this year. A fix issued on July 29 covered CVE-2026-59309, which also scored 9.8. Broadcom's FAQ calls the new flaw "a new and distinct issue."

The July round also fixed a directory-traversal bug, CVE-2026-59310. In August, the German incident response firm QUIRSO assessed that attacks on that bug started five days after disclosure. Its assessment linked them, at moderate confidence, to a suspected actor based in China. QUIRSO estimated 361 compromised IP addresses in 47 countries. It said Babuk-derived ransomware was deployed on ESXi hosts.

Those attacks hit the traversal bug, not a login bypass. Broadcom has reported none on the new flaw. Two flaws in one component are two data points, not a pattern. Still, the August timeline shows how short the gap can be between disclosure and attack.

Why the patch is not a quick click

Broadcom says the updates are cumulative, so one update covers earlier fixes. The fix for vCenter 8.0 is 8.0 U3m. These updates cannot use vCenter Quick Patch, a faster update route introduced in VMware Cloud Foundation 9.1.

Virtual machines keep running during the update. Management access drops briefly. Some encryption tasks against a Standard Key Provider, such as new encryption and key rotation, stop until vCenter returns.

Teams partway through an upgrade face a trap. Broadcom calls it a "Back-in-Time" issue. Applying vCenter 8.0 U3m or 9.0.2.0200 closes the door on a later move to VCF 9.1.1. There are two ways out. One is to move vCenter to 9.1.1 before anything else and put the security update on that version. The other is to wait briefly for VCF 9.1.2.

Older systems are not cleared. Broadcom does not assess products past end of general support. It says unlisted older versions should be presumed affected. vSphere 7 left general support on October 2, 2025. Its customers can ask for a patch under an extended support contract.

The advisory also fixes four lower-rated flaws in SDDC Manager and VMware Tools for Windows. Each needs an attacker who is already authenticated or privileged. Broadcom's FAQ also states that no flaw among the five lets an attacker run code on an ESX host from within a virtual machine.

Questions to put to your team

Ask which vCenter builds you run, including those inside Cloud Foundation. Ask whether each is below a fixed version. Ask who can reach vCenter over the network, and whether that list is as short as it should be. Ask whether any upgrade under way is hit by the Back-in-Time limit.

Ask which systems run vSphere 7 or older, and whether they have extended support. Finally, ask who can declare this an emergency change, and how fast they can act.

With no workaround listed, the network path to the login screen is the main control a team can adjust before patching. A console that manages everything is only as protected as the list of people who can reach it.

Produced by the WebPulse Newsroom with AI assistance from the original reporting credited below, and checked against that source by our editorial review. How we use AI.
Original reporting: Broadcom (VMware).