VMware vCenter Authentication Bypass CVE-2026-123890 Needs an Emergency Patch, Broadcom Says
Broadcom's VMSA-2026-0009 fixes a 9.8-rated vCenter authentication bypass with no workaround and no reported attacks. Fixed builds, what is left unpatched on vSphere 7, and what to check first.

Broadcom published security advisory VMSA-2026-0009 on Thursday 19 November 2026, fixing a critical flaw in VMware vCenter that lets an attacker with network access to the server bypass authentication. The flaw, CVE-2026-123890, is in the VMware Directory Service and carries a CVSS score of 9.8, according to The Hacker News’s report on the advisory. Broadcom has reported no attacks on it and no public exploit code, lists no workaround, and says the issue “qualifies under ITIL methodologies as an emergency change”. Fixed versions exist for every supported branch.
#What the advisory covers
The advisory has five entries, and only one of them is the headline. CVE-2026-123890 is the vCenter authentication bypass. The other four are lower-rated: an SQL injection (CVE-2026-123891), an authenticated command injection (CVE-2026-123892) and a local privilege escalation (CVE-2026-123893), all in SDDC Manager, plus a SAML token signature bypass in VMware Tools for Windows (CVE-2026-123894). Broadcom rates the advisory as a whole Critical, with individual scores running from 6.7 to 9.8.
Broadcom’s own question-and-answer document for the advisory, which it published alongside it, is plain about scope. Any version of vCenter below the fixed builds is affected, whether it is installed on its own or inside VMware Cloud Foundation, vSphere Foundation, Telco Cloud Platform or Telco Cloud Infrastructure. Enhanced Linked Mode makes no difference: the document says the bug is “in vCenter itself” and is present whether or not that feature is used. ESX, the hypervisor, is not affected, nor are NSX, VCF Operations, VCF Automation, Workstation or Fusion.
Mandiant, which is owned by Google, is credited with reporting the vCenter bug, The Hacker News says. Broadcom has not said what level of access an attacker would hold after the bypass, and that is the most important thing we do not know. We come back to it below.
#Fixed versions and what is not covered
For the 8.0 branch the fixed release is vCenter 8.0 U3m. Customers on VMware Cloud Foundation 5.x apply that same vCenter build through the asynchronous patching process in Broadcom knowledge base article 88287 and update SDDC Manager to 5.2.5. On the 9.0 branch the vCenter fix is 9.0.2.0200. For SDDC Manager the fixed builds are 9.1.1.0200, 9.0.2.0100 and 5.2.5. For the 9.1 vCenter build, read the advisory itself, because it is the source of truth for exact versions.
Software that has left support is the gap. Broadcom says it no longer evaluates versions past end of support, so vSphere 6.5 and 6.7 should be presumed affected. vSphere 7.0 is affected too: it reached end of general support on 2 October 2025, and customers with an extended support contract must ask for a patch through it. Broadcom’s advice for anyone on those versions is to move to VCF 9.1. If you are running vCenter 7.0 on a standard contract today, you have no published fix to install and the advisory gives you no mitigation, which is a decision to make this week rather than next quarter.
The updates are cumulative. You do not need to apply earlier patches first, and the builds in this advisory also contain the fixes from the previous one, VMSA-2026-0008. They are not eligible for vCenter Quick Patch, the faster update route introduced in VCF 9.1, so plan for a conventional update.
#The second directory-service bypass this year
This is not the first critical authentication bypass in the VMware Directory Service in 2026. On 29 July, Broadcom patched CVE-2026-59309, another 9.8-rated bypass in the same component, alongside a directory-traversal flaw, CVE-2026-59310. Broadcom’s Q&A calls the new bug “a new and distinct issue”, so patching in July does not protect you now.
What followed July is worth remembering. The security firm Defused Cyber said on 11 August that it was seeing a rise in scanning against vCenter that fitted attempts on CVE-2026-59309, including version probes and walks of the single sign-on flow, as The Hacker News reported in an update to its July story. German incident response firm QUIRSO later assessed that attacks on the traversal flaw had begun five days after its disclosure, linking them with moderate confidence to a suspected China-nexus actor, according to the same publication’s account. It says those attacks compromised an estimated 361 IP addresses in 47 countries and deployed Babuk-derived ransomware on ESXi hosts. That is one outlet’s summary of one firm’s assessment, and we have not seen QUIRSO’s own report, so treat the numbers as indicative.
The pattern matters more than the figures. Last time, the gap between disclosure and attack was measured in days. Nothing we have read says the same will happen with this flaw, and Broadcom reports no exploitation, but defenders who waited on the July advisory had very little margin.
#Why a management server is such a good target
vCenter is the console that manages ESX hosts and virtual machines. It holds the credentials, certificates and permissions that tie a virtualised estate together, and it can reach every host. That is our reading of why this class of bug draws attention: an attacker who gets past authentication on the management plane does not need to break each workload one by one. It is also why we would not rely on the reassurance in Broadcom’s wording that ESX and the virtual machines are unaffected. If the bypass gives an attacker administrative standing in vCenter, what they can then do through vCenter is not limited by this advisory, and Broadcom has not said what access the flaw grants.
We think the practical risk depends mostly on one thing you control: who can reach vCenter over the network. The flaw needs network access to the server. A vCenter on an isolated management network, reachable only from a small set of administrator workstations or a jump host, presents a very different target from one reachable from the whole corporate LAN, a flat network shared with user devices, or the internet. That is a judgement about exposure, not a substitute for patching, because Broadcom lists no workaround and says other controls are for each organisation to weigh.
#The Windows guest fix is the one people will miss
The VMware Tools issue, CVE-2026-123894, is easy to overlook because it is rated lower and applies only inside Windows virtual machines. Broadcom’s document says it is exploitable where a guest alias mapping is configured, and only by an attacker who already has access to a local privileged process in the guest. It does not let code run on the host. A guest alias is a mapping, held inside the guest operating system, that lets a request authenticated with a vCenter single sign-on token act as a guest account without a password.
Two points in the Q&A save time. Disabling guest operations, the control in Broadcom’s security configuration guide, does not protect against this flaw and does not remove aliases that already exist. Stopping or uninstalling VMware Tools is not a workaround either, and would switch off time sync, heartbeats for high availability and quiescing for backups. The fixed builds are VMware Tools 13.1.5.0 for the 13.x line and 12.5.5 for 12.x and 11.x. To see what is installed, the Summary tab for each machine in the vSphere Client shows the version, and Broadcom’s document gives a PowerCLI query that lists it for every Windows guest.
#Small organisations and managed providers
If your organisation has no in-house infrastructure team and a provider looks after your virtual servers, this is a message to send them rather than a job to do. The question to ask, in these words, is: “Which version of vCenter do we run, is it on the fixed build from VMSA-2026-0009, and who can reach its management address from the network?” If they run vSphere 7 or earlier, ask when it is moving and what protects it in the meantime. Do not assume that a hosted service has patched itself: Broadcom’s document says that for hosted and cloud products, advisory information arrives as a message inside the service’s own admin console, so check there.
#Our view: treat it as an emergency change, and start with exposure
We agree with Broadcom’s own classification. An unauthenticated bypass in the central console of a virtualised estate, from a vendor that tells customers to treat the update as an emergency change, belongs at the front of the queue, ahead of ordinary monthly patching. We also think the July episode justifies not waiting for confirmation of attacks first.
What we expect next, as a labelled prediction: scanning for vCenter will rise within days, as it did after the July advisory, and researchers will start picking apart the patch. What would prove us wrong is a quiet fortnight with no public analysis and no scanning reports, in which case the urgency is lower than we think, though the patch is still worth applying.
#What to do today
- Find every vCenter you run. Include test, lab and forgotten ones, and any inside engineered systems such as HPE SimpliVity or Dell VxRail. For those, Broadcom says to follow the system vendor’s guidance on patch levels rather than apply its own.
- Check the build. The Summary tab in the vSphere Client shows it, or run
Connect-VIServerin PowerCLI and read$global:DefaultVIServer.Buildand.Version. - Cut network reach first. Limit who can reach vCenter’s management address to administrator workstations or a jump host while you schedule the update. This is our suggestion, not a Broadcom workaround.
- Take a backup, then update. Virtual machines keep running during the vCenter update; management access drops briefly, and some key operations against a Standard Key Provider, such as new encryption or key rotation, are unavailable until it returns.
- Mind the upgrade conflict. Installing vCenter 8.0 U3m or 9.0.2.0200 blocks a later upgrade to VCF 9.1.1, which Broadcom calls a “Back-in-Time” issue. If you are planning that upgrade, update vCenter to 9.1.1 first and apply the security update there, or wait briefly for VCF 9.1.2.
- Update VMware Tools in Windows guests and SDDC Manager where you run it.
- Review sign-in and administrator activity on vCenter for the past weeks, looking for logins or new accounts nobody can explain.
#What we do not know yet
- What access an attacker holds after the bypass. Broadcom does not say.
- Whether the flaw is being exploited. Broadcom has reported no attacks and no public exploit code, as of its advisory on 19 November.
- Whether it will be added to the US cyber agency CISA’s Known Exploited Vulnerabilities list. It was not there when we checked the feed on the evening of 19 November.
We will update this story if Broadcom or a researcher adds to that picture.
Evidence trail
Sources and verification
Primary documentation and external technical references used in this article.
- 01Broadcom, VMSA-2026-0009: Questions & Answersgithub.com
- 02The Hacker News, Critical VMware vCenter Flaw (CVSS 9.8) Lets Network Attackers Bypass Authentication, 19 November 2026thehackernews.com
- 03The Hacker News, Three critical VMware flaws, 29 July 2026thehackernews.com
- 04CISA Known Exploited Vulnerabilities cataloguecisa.gov
About this page
Credited to
Dates
Published
Corrections
No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.
More news
All newsWas this useful?
Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.
Get new fixes by email.
New runbooks, configuration traps and fixes from KBY Technologies, about twice a week.




Comments
Add a thoughtful note on VMware vCenter Authentication Bypass CVE-2026-123890 Needs an Emergency Patch, Broadcom Says. Comments are checked for spam and held for moderation before appearing.