Blog
VMware vCenter CVE-2026-123890: critical authentication bypass
What it is and who is affectedBroadcom VMware vCenter contains a critical authentication bypass, tracked as CVE-2026-123890 and officially named "VMwa...
What it is and who is affected
Broadcom VMware vCenter contains a critical authentication bypass, tracked as CVE-2026-123890 and officially named "VMware vCenter Authentication Bypass Using an Alternate Path or Channel Vulnerability". The flaw sits in the VMware Directory Service and, according to CISA, allows an unauthenticated attacker with network access to vCenter to bypass authentication and gain unauthorised access to the system. It is classified as CWE-288 and carries a CVSS 3.1 score of 9.8 (CRITICAL).

The affected versions listed in the advisory are 9.1.x (fixed in 9.1.1.0200), 9.0.x (fixed in 9.0.2.0200), 8.0 (fixed in 8.0 U3m) and 5.x (fixed in 5.2.5). Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x, 5.2 and Telco Cloud Infrastructure 3.0 are also affected, with details in Broadcom KB463116. The NVD entry, published on 19 November 2026, additionally lists VMware Cloud Foundation from 5.0 up to but not including 5.2.5, and a long set of vCenter Server 7.0 and 8.0 configurations, including the 8.0 update1, update1a, update1b and update1c builds.
In practice this concerns any organisation running vCenter to manage its virtual infrastructure: an internal IT team, a hosting provider, or a company with a small systems department in Barcelona, Lleida, Tarragona or Girona that virtualises its servers. If vCenter is reachable from the internet, or from a network segment an attacker can already touch, the exposure is serious.
Why it is urgent
This is not a theoretical bug waiting for a proof of concept. CISA added CVE-2026-123890 to its Known Exploited Vulnerabilities (KEV) catalogue on 20 November 2026, which means it has been observed in real attacks. The agency gave US federal agencies until 23 November 2026 to apply mitigations in line with vendor instructions, under its BOD 26-04 risk-based patching guidance and its forensics triage requirements.
The advisory does not record known use in ransomware campaigns, and we should not claim otherwise. That said, an unauthenticated bypass of this severity on a management plane is exactly the kind of foothold that gets reused later, so the absence of a ransomware link is no reason to relax. The CVSS vector (AV:N/AC:L/PR:N/UI:N) describes an attack that needs no credentials, no user interaction and only network reachability.
What to do today
- Inventory first. Confirm whether you run vCenter, VMware Cloud Foundation or any Telco Cloud Platform or Telco Cloud Infrastructure release, and pin down the exact build. Many teams discover a forgotten vCenter appliance during an audit.
- Patch to the fixed build named in the vendor advisory. The versions above are the ones Broadcom states as corrected. If your deployment is outside those branches, follow whatever the official Broadcom security advisory and KB463116 indicate rather than guessing.
- Look for signs of intrusion. Because the flaw allows unauthenticated access, review vCenter and Directory Service logs for unexpected authentication events, unfamiliar accounts or configuration changes around the dates the vulnerability became public. CISA's forensics triage requirements are a useful checklist even for private organisations.
- Reduce what is exposed. vCenter has no business being reachable from the public internet. Restrict management interfaces to a VPN or a dedicated administration network, segment them from user networks, and apply least privilege to service accounts.
- Assume compromise if you cannot patch immediately. Where a fix cannot be applied at once, apply the mitigations in the vendor notice and consider discontinuing the exposed service until you can. Rotate credentials and certificates that may have been reachable during the window.
How a cybersecurity team like ALMC's can help
Most SMEs and online shops we work with in Catalonia do not have a dedicated security function. They have a web team, an IT generalist, or an external provider keeping WordPress, PrestaShop or Joomla running. Infrastructure vulnerabilities such as this one fall between the cracks precisely because nobody owns the virtualisation layer.
That is where an external team earns its keep: running a security audit and pentesting to map what is actually exposed, hardening servers and management interfaces so vCenter and similar consoles are not reachable from the open internet, and monitoring for the kind of anomalous access this flaw enables. When something does go wrong, incident response and repair of a hacked site matter more than any report. The same discipline applies to routine patch management on CMS platforms, where an unpatched plugin is the everyday equivalent of an unpatched hypervisor.
If your infrastructure runs on VMware and you are unsure which build you are on, that uncertainty is the finding. Establishing it, closing the gap and keeping it closed is the whole job. The technical details in this article come from CISA's Known Exploited Vulnerabilities catalogue and the NIST National Vulnerability Database, together with Broadcom's own advisory.
Related
- Ivanti Connect Secure: CVE-2026-104935 Under Active Attack
- CVE-2026-96951: Windows Shell Command Injection Under Attack
- Click to Chat for WhatsApp: CVE-2026-92097 in WordPress
- Abuse Shield
Is your business exposed to flaws like this?
ALMC checks which versions you are running, applies the patches and hardens your servers and website. Contact our team for a security review.
