← All updates

Security / News explained

vCenter’s authentication fix needs the right product branch

CVE-2026-123890 affects the VMware Directory Service. Broadcom’s response matrix separates vCenter branches, Cloud Foundation packages and extended-support paths.

By Zyel · Published · 4 min read

Broadcom’s November 19, 2026 advisory describes CVE-2026-123890, an authentication bypass in vCenter’s VMware Directory Service. An attacker with network access to vCenter may gain unauthorised access. The advisory was updated on November 20; its response matrix remains the place to match an installation to a correction. [1]

CISA added the CVE on November 20. Its entry lists November 23 for remediation and requests forensic triage. [3]

For an operations team, the central issue is access to the management system itself. Our interpretation is that the review should begin with reachable management services and the software they actually run. An application’s ordinary sign-in experience is not a test of whether a separate authentication path is functioning correctly.

Match the component before choosing a version

The VMware CNA record lists affected vCenter 9.1.x releases before 9.1.1.0200, 9.0.x before 9.0.2.0200, and the 8.0 line before 8.0 U3m. These are branch-specific correction points, not interchangeable names for a single update. [2]

For VMware Cloud Foundation 5.x, the FAQ specifies vCenter 8.0 U3m through the asynchronous patching process and a separate SDDC Manager update to 5.2.5. The advisory links additional instructions for the affected Telco Cloud products. [1] [4]

The vendor’s FAQ also says vSphere 7.0 is affected and reached the end of general support on October 2, 2025. Customers with an active extended-support contract are directed to that support process for patches. [4]

This is a place where a tidy spreadsheet can still mislead. In a hypothetical estate, “version 9” might describe a product bundle, while its management components follow different build numbers. Recording the component name alongside the version prevents one completed update from being used as evidence for a different component.

A shared version prefix is a convenient label, not a completed security argument. The useful question is whether the installed component falls on the corrected side of the appropriate vendor row. Where a support path differs, that difference needs an owner and a documented next action.

Plan around the documented operational behaviour

Broadcom’s FAQ says this is not a virtual-machine escape and ESX is not affected by this advisory. It also states that turning off Enhanced Linked Mode does not protect vCenter from this issue. Those distinctions help keep remediation focused on the affected software. [4]

The same FAQ says these vCenter updates are not eligible for Quick Patch. Updating vCenter temporarily removes its management interface while running workloads continue; operators should still review their own dependent management and encryption operations when planning the maintenance window. [4]

In a hypothetical environment, an internal route from an administrator workstation could satisfy a network-access prerequisite even when the management address is absent from the public internet. That example is why reachability deserves an explicit review. It is not a claim that any particular workstation, VPN or management network has been compromised.

The advisory lists no workaround for this authentication bypass. Network restrictions can still be part of a team’s containment decisions, but Broadcom identifies the fixed software versions as the remediation. An access-control change should not be recorded as though the missing software correction had already been installed. [1]

Separate a completed update from an investigation

Our suggested completion record is deliberately ordinary: identify the instance, the relevant matrix row, the installed corrected build and the time the running service was checked. Include management dependencies that were unavailable during the change and the person responsible for confirming their return. These are proposed operating practices, not results of a Zyel assessment.

The exploitation listing gives teams a reason to connect patching with their incident-response process where their evidence warrants it. Installing a correction and examining possible earlier access answer different questions. A successful change does not, on its own, establish that historical authentication activity was legitimate.

Keep any investigation tied to the actual asset and available evidence. A public advisory can describe a capability and a prerequisite; it cannot identify the condition of a private system. Likewise, a working login after maintenance establishes a useful function check, but it does not validate every management route or explain earlier events.

The practical outcome is a precise maintenance decision: use the right product branch, apply the vendor’s correction and verify the running component. For this issue, choosing the row carefully is part of acting quickly. One convenient version number cannot do all the work.

Sources + further reading

Source dates describe the original material. Publication above is the date this Zyel article went live.

  1. Broadcom VMSA-2026-0009.1Broadcom · Checked Nov 21, 2026
  2. VMware CNA: vCenter authentication bypassBroadcom · Checked Nov 21, 2026
  3. CISA Known Exploited Vulnerabilities catalogCISA · Checked Nov 21, 2026
  4. Broadcom advisory questions and answersBroadcom · Checked Nov 21, 2026

Reader discussion

What would you ask next?

Questions, useful corrections and thoughtful disagreement are welcome. Comments are reviewed before they appear.

No reader comments yet.

10–2,000 characters. Plain text. Leave out passwords, private project data and personal contact details. A blank display name appears as Anonymous.

Complete the CAPTCHA before sending. Verification runs on your device.