Daily · Article 01 · 4 min read
- Security
VMware vCenter flaw exploited. Is your management server patched?
November 19–20 Broadcom advisory and November 21 JST CISA catalog update
Summary
CISA listed VMware vCenter’s authentication bypass as exploited on November 20. Match your product line to Broadcom’s fix and verify the build running on each management server.
Key facts
The U.S. cybersecurity agency CISA added VMware vCenter authentication bypass CVE-2026-123890 to its Known Exploited Vulnerabilities catalog on November 20. The catalog was updated on November 21 at 02:48 JST. vCenter manages fleets of virtual servers. Someone who can reach an affected vCenter over the network could gain access without the usual identity check.
Vendor Broadcom issued an advisory with fixed versions on November 19 and revised it on November 20. Operators can compare the running build of each management server with the fix for its product line. Broadcom rates its severity at 9.8 out of 10 on the Common Vulnerability Scoring System (CVSS). Broadcom advisory, section 3a · CISA catalog data

1. The public service and the server that manages it
Imagine a company running bookings, staff tools and internal reports on several virtual servers. Customers open the booking website. The operations team uses vCenter to manage where the different virtual servers run. Those destinations and the actions available in each can differ even when the systems share the same physical hardware.
The directory service in vCenter handles identities and account information. Authentication is the check that establishes who someone is before granting access. This advisory concerns that check within vCenter. Broadcom says someone with network access to vCenter may be able to bypass the check and gain unauthorized access to the system. The fictional company shows which destination matters.
| Who is trying to do what? | Destination | What to check for this advisory |
|---|---|---|
| A customer views a reservation | Public booking website | The website response cannot identify the management server’s build |
| An operator manages virtual servers | vCenter management server | Its running build and the networks that can reach it |
- Who is trying to do what?
A customer views a reservation
- Destination
- Public booking website
- What to check for this advisory
- The website response cannot identify the management server’s build
- Who is trying to do what?
An operator manages virtual servers
- Destination
- vCenter management server
- What to check for this advisory
- Its running build and the networks that can reach it
The cat asks Q&A
- The researcher
If the booking site is open to the internet, can people reach vCenter from outside too?
Pocket NotebookEach system has its own access rules. The operations team’s inventory and network access policy can show which management servers are reachable and from where.
2. The update path depends on the product line
Standalone vCenter and vCenter bundled with other VMware products can follow different update paths. Find the product and installed release line first, then read the Fixed Version column in Broadcom’s matrix. Broadcom lists no official workaround for this issue. A management network with restricted access still has a running build that operators can check. Vendor FAQ
| Product and installed release line | Fix in the advisory | Evidence |
|---|---|---|
| Standalone vCenter 8.0 | 8.0 U3m | Advisory, section 3a |
| vCenter 9.0.x.x in Cloud Foundation or vSphere Foundation | 9.0.2.0200 | Advisory, section 3a |
| vCenter 9.1.x.x in Cloud Foundation or vSphere Foundation | 9.1.1.0200 | Advisory, section 3a |
| Cloud Foundation 5.x | Check the matrix’s 5.2.5 entry and component-specific guidance. The FAQ identifies 8.0 U3m for vCenter | Advisory, section 3a · Vendor FAQ |
| Standalone vCenter 7.0 | Contact Broadcom Support if you have extended support | Advisory, section 3a |
| Telco Cloud Platform or Infrastructure | vCenter 8.0 U3m for listed releases. Match the installed line to the documentation | Telco product guidance |
- Product and installed release line
Standalone vCenter 8.0
- Fix in the advisory
- 8.0 U3m
- Evidence
- Advisory, section 3a
- Product and installed release line
vCenter 9.0.x.x in Cloud Foundation or vSphere Foundation
- Fix in the advisory
- 9.0.2.0200
- Evidence
- Advisory, section 3a
- Product and installed release line
vCenter 9.1.x.x in Cloud Foundation or vSphere Foundation
- Fix in the advisory
- 9.1.1.0200
- Evidence
- Advisory, section 3a
- Product and installed release line
Cloud Foundation 5.x
- Fix in the advisory
- Check the matrix’s 5.2.5 entry and component-specific guidance. The FAQ identifies 8.0 U3m for vCenter
- Evidence
- Advisory, section 3a · Vendor FAQ
- Product and installed release line
Standalone vCenter 7.0
- Fix in the advisory
- Contact Broadcom Support if you have extended support
- Evidence
- Advisory, section 3a
- Product and installed release line
Telco Cloud Platform or Infrastructure
- Fix in the advisory
- vCenter 8.0 U3m for listed releases. Match the installed line to the documentation
- Evidence
- Telco product guidance
The cat asks Q&A
- The researcher
If the company bought Cloud Foundation 5.x, should the vCenter screen say
5.2.5?Pocket NotebookThe suite and its individual components have their own version numbers. Broadcom’s FAQ directs Cloud Foundation 5.x operators to apply 8.0 U3m to vCenter through an individual component update. Ask the team that manages the installation for the vCenter build itself.
3. From advisory to the running server
The due date in CISA’s entry is November 23, a date under its U.S. federal agency remediation program. CISA marks ransomware use as unknown. The catalog entry establishes known exploitation. An individual company’s records are needed to determine whether its own management server was compromised or has been patched.
| Stage | Who is responsible? | Status and evidence |
|---|---|---|
| Fix prepared | Broadcom product team | Confirmed. The advisory names fixed versions by product |
| Updates supplied | Broadcom distribution channels | Confirmed. Updates and instructions are available for listed releases |
| Fix in use on a specific server | In-house operations team or managed service provider | Unverified per server. Check the running build, installation time and change record |
- Stage
Fix prepared
- Who is responsible?
- Broadcom product team
- Status and evidence
- Confirmed. The advisory names fixed versions by product
- Stage
Updates supplied
- Who is responsible?
- Broadcom distribution channels
- Status and evidence
- Confirmed. Updates and instructions are available for listed releases
- Stage
Fix in use on a specific server
- Who is responsible?
- In-house operations team or managed service provider
- Status and evidence
- Unverified per server. Check the running build, installation time and change record
The cat asks Q&A
- The researcher
Does a published update mean our management server already has it?
Pocket NotebookIf your team operates vCenter, check its running build in the vSphere Client’s
Summarytab after updating. Ask a managed provider for the fixed build and installation time for each server. Have the security team review evidence of any earlier unauthorized access separately from the patch check. Where to find the build
To close
A record for the next shift
Suppose a team runs vCenter in two offices and has a completed change record for the first server. The second still needs its own evidence. A running build and completion time for each server let the next operator see where work is still due.
Sources
- Advisory, section 3asupport.broadcom.com
- CISA catalog dataraw.githubusercontent.com
- Where to find the buildgithub.com
- Telco product guidanceknowledge.broadcom.com