← All insights

Security alert · 6 min read

VMware vCenter CVE-2026-123890: actively exploited authentication bypass

Broadcom has released updates for CVE-2026-123890, a critical authentication-bypass vulnerability affecting supported VMware vCenter versions. On 20 November 2026, the US Cybersecurity and Infrastructure Security Agency added it to the Known Exploited Vulnerabilities catalogue based on evidence of active exploitation. A vulnerable vCenter should be treated as a priority because an attacker with network access may bypass authentication without needing a valid account.

Check the authoritative advisories

Review Broadcom’s VMSA-2026-0009 security advisory and CISA’s Known Exploited Vulnerabilities catalogue . For broader protection planning, see Avant IT’s cyber security and managed support services.

What is affected?

The vulnerability is in VMware vCenter, the central management system used to administer VMware vSphere and ESXi environments. Broadcom lists affected releases in the vCenter 8.0, 9.0 and 9.1 branches, along with relevant VMware Cloud Foundation and telco products. vCenter 7.0 is also affected but requires an extended-support arrangement for remediation guidance. The exact fixed release depends on the product branch.

What is not the same thing?

Using VMware Workstation or running an individual virtual machine does not necessarily mean you operate vCenter. A business is more likely to be affected if it has a web-based vSphere Client used to manage one or more ESXi hosts, clusters, shared storage or a VMware Cloud Foundation environment. If you are unsure, check infrastructure records or ask the person who manages the servers rather than scanning or changing production systems at random.

Why the vulnerability matters

Broadcom describes an authentication bypass in the VMware Directory Service and assigns it a maximum CVSS score of 9.8. A malicious actor who can reach vCenter over the network may gain unauthorised access without user interaction. Because vCenter controls important virtual infrastructure, unauthorised administrative access could expose server configurations and create a path to wider disruption or data access.

Check exposure before making changes

Identify every vCenter appliance, record its current build and determine which networks can reach its management interface. A vCenter interface should not be directly available from the public internet. Restrict access to trusted administration networks or a properly secured remote-access path, but do not assume network restriction replaces the security update.

Apply the vendor update

Broadcom lists fixed releases including vCenter 8.0 U3m, 9.0.2.0200 and 9.1.1.0200. Confirm the correct target in the current Broadcom advisory because product editions and supported upgrade paths differ. Follow the supported backup, compatibility and update procedure for the environment. Broadcom states that no workaround is available for the vCenter authentication bypass.

Do not patch blindly without preserving useful evidence

Patching closes the known vulnerability but does not remove access an attacker may already have gained. Before making a change that could overwrite short-lived evidence, record the appliance version, exposure, unusual alerts and relevant times. Where active exposure or suspicious activity is possible, preserve available logs and involve an experienced administrator or incident responder while still treating the update as urgent.

What administrators should review

Look for unexpected administrator accounts, identity or permission changes, unfamiliar sessions, unexplained configuration changes and unusual connections to or from vCenter. Also review security monitoring and authentication evidence around the appliance. Absence of an obvious alert is not proof that exploitation did not occur, and indicators may change as vendor and threat information develops.

Protect the update and recovery process

Use vendor documentation obtained through a known Broadcom support path, verify backups and recovery information, and confirm management access after the update. Do not download an alleged emergency patch from an email or an unfamiliar website. Avoid taking an untested snapshot as the only recovery plan for critical infrastructure, and coordinate changes where restarting management components could affect operations.

When to seek help

Seek prompt assistance if vCenter was internet-exposed, the version cannot be confirmed, an update path is unclear, support has expired or logs show unexplained access or changes. A safe response may require both remediation and investigation. Businesses that do not operate vCenter do not need to change unrelated VMware products because of this alert.

Building something useful together

Did this guide help?

If an Avant IT article helped you solve a problem or better understand your technology, you can make an optional $5 contribution towards creating more practical guides. Help keep us awake and typing by shouting the team a coffee! Every guide is created in-house by our passionate team, often in our own time, to share our knowledge and give back to the community.

Your support is completely optional but always appreciated.
$5,000 community goal

Help us build a free guided troubleshooting centre for common email, Wi-Fi, internet, computer and browser problems.

Support the free tools

Ready when you are

Make IT one less thing to worry about.

Start an enquiry 0434 528 511