Critical VMware vCenter Flaw (CVSS 9.8) Lets Network Attackers Bypass Authentication
An authentication bypass lets an attacker get past a system’s login checks without successfully proving they are an authorized user. In this case, Broadcom says a network-reachable attacker can use a flaw in VMware Directory Service to bypass authentication and access vCenter without authorization. That makes the flaw especially serious because the attacker does not first need a valid account, according to the advisory. The flaw is tracked as CVE-2026-123890 and has a CVSS score of 9.8. However, Broadcom has not specified what level of access an attacker gains after the bypass. The article therefore does not establish that an attacker can take any particular action inside vCenter or control specific systems. Broadcom has released fixes for supported affected versions and lists no workaround. It has not reported attacks exploiting this flaw or public exploit code. Organizations should treat the authentication weakness as urgent, while keeping the limits of what is known clear: the risk is unauthorized access, but the precise post-bypass capabilities are undisclosed.
What does an authentication bypass let a network attacker do in this vCenter flaw?
An authentication bypass lets an attacker get past a system’s login checks without successfully proving they are an authorized user. In this case, Broadcom says a network-reachable attacker can use a flaw in VMware Directory Service to bypass authentication and access vCenter without authorization. That makes the flaw especially serious because the attacker does not first need a valid account, according to the advisory.
The flaw is tracked as CVE-2026-123890 and has a CVSS score of 9.8. However, Broadcom has not specified what level of access an attacker gains after the bypass. The article therefore does not establish that an attacker can take any particular action inside vCenter or control specific systems.
Broadcom has released fixes for supported affected versions and lists no workaround. It has not reported attacks exploiting this flaw or public exploit code. Organizations should treat the authentication weakness as urgent, while keeping the limits of what is known clear: the risk is unauthorized access, but the precise post-bypass capabilities are undisclosed.
What is VMware vCenter, and what does it manage?
VMware vCenter is the central console an organization uses to manage its ESX hosts and virtual machines. In practical terms, it is the management point for those parts of a VMware environment. The article distinguishes vCenter from ESX itself: the new flaw affects vCenter, while Broadcom says ESX is not affected.
For example, an organization with multiple ESX hosts can use vCenter as its central place to manage those hosts and the virtual machines they run. The article does not detail every management task, but it describes vCenter as the console for managing both categories. That central role helps explain why unauthorized access to the system matters.
The authentication bypass is in VMware Directory Service within vCenter. Broadcom says the flaw affects specified vCenter versions and versions included in several VMware products. It has released updates for supported branches. Virtual machines keep running during installation, though management access drops briefly, according to the advisory FAQ.
What does a CVSS score of 9.8 mean on the 10-point severity scale?
CVSS is a standard system for scoring the severity of security vulnerabilities on a scale that runs up to 10. A score of 9.8 is very close to the maximum. Under CVSS’s standard severity bands, scores from 9.0 through 10.0 are classified as critical. That makes 9.8 a signal that the flaw warrants urgent attention.
Broadcom assigned CVE-2026-123890 a 9.8 score. The vulnerability allows an attacker with network access to bypass authentication in VMware Directory Service and gain unauthorized access to vCenter. The score reflects the seriousness of the weakness; it does not, by itself, establish what access the attacker gets after bypassing authentication.
A severity rating is also not evidence that a vulnerability is being exploited. Broadcom says it has not reported attacks on this flaw or public exploit code. It has released fixes for supported versions and calls the issue an emergency change under ITIL methodologies. Organizations should consult security staff promptly about update timing.
Why could unauthorized access to vCenter put an organization's ESX hosts and virtual machines at risk?
vCenter is the central console for managing an organization’s ESX hosts and virtual machines. If an attacker gains unauthorized access to that management system, the organization’s management environment is exposed. That is why an authentication bypass in vCenter matters beyond the console alone, even though the advisory does not describe the attacker’s exact permissions.
The flaw, CVE-2026-123890, is in VMware Directory Service and can be reached by an attacker with network access. Broadcom has not said what level of access follows the bypass. It also states that none of the five flaws in the advisory lets code run on an ESX host from inside a virtual machine, and that ESX itself is not affected.
So the concern is unauthorized access to the central management system, not a confirmed ability to execute code on ESX hosts. Broadcom has not reported attacks exploiting this bypass. Updates are available for supported affected versions, and the company says there is no listed workaround. The FAQ advises organizations to consult security staff immediately about timing.
If an organization cannot install the update immediately, what workaround does Broadcom offer, and what does it say about other mitigations?
Broadcom lists no workaround for the vCenter authentication bypass. In its FAQ, it answers the workaround question with “Not as listed by Broadcom.” It adds that mitigations may still exist within an organization’s own defenses, but does not identify or recommend a specific one. That means the article gives no substitute fix to apply while waiting to update.
Broadcom has released updates for all supported affected branches. The updates are cumulative and cannot be installed through vCenter Quick Patch. During installation, virtual machines continue running, but management access drops briefly. Some encryption operations involving a Standard Key Provider are unavailable until vCenter is back online.
The FAQ calls the flaw an emergency change under ITIL methodologies and urges organizations to consult security staff immediately about timing. For systems that cannot be updated yet, the article’s guidance is limited: there is no Broadcom-listed workaround, though an organization may have mitigations in its own defenses. It does not claim those mitigations remove the vulnerability.
How does this flaw compare with the earlier VMware Directory Service flaws, and what did attackers exploit after those flaws were disclosed?
The current flaw is the second critical authentication flaw in VMware Directory Service this year. The earlier vCenter flaws were patched on July 29: CVE-2026-59309 was another authentication bypass in the same component, also rated 9.8, while CVE-2026-59310 was a directory-traversal bug. The new bypass is tracked as CVE-2026-123890.
The attacks described after the earlier disclosure targeted the directory-traversal flaw, not the new bypass. German incident response firm QUIRSO assessed that attacks began five days after disclosure and 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 not reported attacks exploiting the new authentication bypass, nor public exploit code. The earlier incidents show that a different flaw in the same service was followed by attacks, but they do not establish that the current bypass is being exploited. Broadcom has released fixes for supported branches and urges organizations to consult security staff about update timing.
What is a hypervisor, and how is its job different from vCenter's management role?
A hypervisor is software that runs virtual machines on a physical computer, commonly called a host. Its job is to provide the environment in which those virtual machines operate. This basic definition comes from general computing knowledge; the article does not define “hypervisor,” but it refers to ESX hosts and the virtual machines they run.
vCenter has a different role: it is the central console for managing an organization’s ESX hosts and virtual machines. For example, vCenter provides a management point for an environment made up of hosts and VMs, rather than being the software that runs each VM. The flaw discussed here is in vCenter’s VMware Directory Service.
Broadcom says none of the five flaws in its advisory lets code run on an ESX host from inside a virtual machine, and ESX itself is not affected. That distinction matters when describing the risk: the critical bypass targets vCenter authentication, while the article does not claim the vulnerability directly compromises a hypervisor or a VM.
This brief was written by AI from the original reporting and checked by other models. Names, figures and quotes come from the source; read it for full context.
Read more in the JupiteX app
Pulse is free. New stories every 4 hours, each one broken into the questions that explain it.
Or read more news on the web