Hackers are already using the vCenter login bug: CISA adds CVE-2026-123890 to its exploited list, patch by Nov 23

5 min read

How to fix CVE-2026-123890: upgrade vCenter to 8.0 U3m, 9.0.2.0200 or 9.1.1.0200. CISA added the exploited vCenter login bypass to its KEV list on Nov 20 with a Nov 23 deadline and forensic triage. Save evidence, patch, then check for intruders.

Hackers are already using the vCenter login bug: CISA adds CVE-2026-123890 to its exploited list, patch by Nov 23
On this page

Attackers have been using a VMware vCenter bug to get into the console that runs a company's virtual machines without a password, and as of November 20, 2026 the US government lists it as exploited. CISA added CVE-2026-123890 to its Known Exploited Vulnerabilities (KEV) catalog with a deadline of Monday, November 23. That is three calendar days, two of them a weekend. CISA also flagged it "Forensic Triage: Yes", which means federal agencies have to look for a break-in, not just install the update.

We covered the bug itself when Broadcom fixed it on November 19: how the vCenter login bypass works, which build fixes your version, and what Mandiant saw attackers do with it. That post owns the fix details. This one is about what the KEV listing changes for the next 72 hours.

What changed since November 19

  • November 19: Broadcom published VMSA-2026-0009 with fixes and no workaround. The advisory does not mention attacks. The same day, Google's Mandiant reported that a China-linked group had used the bug as a zero-day since early September.
  • November 19, NVD: CISA's own enrichment on the NVD record still scored exploitation as "none". That field lags. Do not use it to decide priority.
  • November 20: Broadcom moved the advisory to VMSA-2026-0009.1. The only change in its log is a clarification of the affected VMware Tools versions. The vCenter fixed builds did not change, and the advisory still says nothing about exploitation.
  • November 20: CISA added CVE-2026-123890 to KEV as "VMware vCenter Authentication Bypass Using an Alternate Path or Channel" (CWE-288), due November 23, ransomware use "Unknown", forensic triage "Yes". Cisco Expressway, Apache Roller and SAP NetWeaver went on the list the same day with the same deadline.

How to fix

Install the fixed vCenter build for your line. Broadcom's patches are cumulative, so anything newer also counts:

  • vCenter 9.1.x: 9.1.1.0200
  • vCenter 9.0.x: 9.0.2.0200
  • vCenter 8.0: 8.0 U3m
  • VMware Cloud Foundation 5.x: 5.2.5, applying vCenter 8.0 U3m through the async patching process in KB 88287
  • vCenter 7.0: Broadcom lists no public fix. Its response matrix says to contact Broadcom Support if you have an extended support contract.

To confirm what you run, open the vSphere Client and read the version and build on the vCenter Summary tab, or in PowerCLI run Connect-VIServer vcenter.example.com and then $global:DefaultVIServer | Select-Object Version, Build. If you already installed one of the builds above on November 19 or 20, the KEV listing does not ask you to do anything new about the code. It asks you to check whether someone got in first.

Save evidence before you patch, if you can

This is the part a "patch by Monday" headline hides. CISA's forensic triage guidance for BOD 26-04 puts evidence collection (2 to 24 hours after the KEV add) before patching, and says plainly: "Do not alter or remediate systems prior to evidence/artifact collection when possible." An update restarts vCenter services, which throws away whatever is in memory. If an intruder is already in, that is the evidence you need.

For a vCenter appliance, the practical order is:

  1. Export a vCenter log bundle from the vSphere Client (Export System Logs on the vCenter object) and keep it off the appliance.
  2. Take a snapshot of the vCenter appliance VM with the option to include the VM's memory, then copy or protect it. That memory image is what CISA means by volatile data.
  3. Write down when you did each step and who did it. CISA asks agencies to keep exactly that log.
  4. Then patch. If collecting evidence would push you past the deadline, patch anyway. An exploited management console is worse than a thin investigation.

How to check if you were already hit

Broadcom has not published indicators. The useful ones come from Mandiant's report, which we summarized in the original post. In short:

  • List the single sign-on administrators in vsphere.local and question every account nobody on your team created.
  • Look for SSH on the vCenter appliance being switched on and back off by nobody you know.
  • Look for connections to vCenter on TCP port 2012 (the directory service) from machines that have no reason to talk to it.
  • If you run BeyondTrust Remote Support, confirm the fix for CVE-2026-102764 is in. Mandiant says that was the way in before vCenter.

If you find any of these, treat the vCenter signing key as stolen. A patched vCenter with a stolen signing key still lets the attacker sign in as anyone.

Who is not in scope

  • ESX hosts. Broadcom's FAQ says ESX needs no update for this advisory. Neither do NSX, VCF Operations, VCF Automation, Workstation or Fusion.
  • The November 23 deadline itself. It binds US federal civilian agencies under BOD 26-04. Everyone else gets it as a strong hint, not an order.
  • Teams already on 8.0 U3m, 9.0.2.0200, 9.1.1.0200 or VCF 5.2.5. You are patched. Your remaining work is the compromise check above.

What this is not

This is not a new bug and not a new fix. KEV adds a deadline and confirms attacks; the fixed builds are the same ones Broadcom shipped on November 19. It is also not a bug in the ESX hypervisor, and not something an attacker can reach without network access to vCenter. Neither Broadcom nor CISA has published exploit details.

HOL Guard keeps the source record for this issue in the CVE-2026-123890 evidence pack, and tracks it end to end on the vCenter security campaign page. This post is the operator write-up.

What do people ask about the vCenter KEV listing?

Is CVE-2026-123890 being exploited?

Yes. CISA added it to the Known Exploited Vulnerabilities catalog on November 20, 2026. Mandiant reported zero-day use by a China-linked group starting in early September 2026. Broadcom's advisory does not mention exploitation.

What is the CISA deadline for CVE-2026-123890?

November 23, 2026, with forensic triage required. Under BOD 26-04 that means federal agencies must patch or mitigate within three days and check the system for compromise.

Which vCenter version fixes it?

9.1.1.0200, 9.0.2.0200, 8.0 U3m, or VCF 5.2.5. There is no public fix for vCenter 7.0.

Should I patch first or collect evidence first?

CISA's guidance is evidence first when you can do it quickly: a log bundle and a memory-inclusive snapshot of the vCenter VM take minutes. Do not let it push the update past the deadline.

Does updating vCenter stop my virtual machines?

No. Running VMs keep running. You lose the vSphere Client while vCenter restarts.

If AI agents or automation in your team hold vCenter credentials, check if your agents touch this package with HOL Guard.

References

All articles

Keep exploring

The engineering desk continues across the ecosystem: security research on shipping agents safely, and plugins that put the standards to work.