Skip to main content

Praxis AI™Vijilan's most advanced SOC platform is open to early adopters.

Sign up here
Threat Intelligence · November 21, 2026

VMware vCenter CVE-2026-123890: Exploited Authentication Bypass

CISA confirms attackers are exploiting CVE-2026-123890, a 9.8-rated authentication bypass in VMware vCenter. Fixes are out for supported releases, with a 23 November deadline.

Vijilan Incident Desk· 5 min read
VMware vCenter CVE-2026-123890: Exploited Authentication Bypass
Short answer

On 20 November 2026, CISA added CVE-2026-123890, an authentication bypass in VMware vCenter Server, to its Known Exploited Vulnerabilities catalog, with a due date of 23 November [1][2]. CISA says the flaw, in the VMware Directory Service, "allows an unauthenticated attacker with network access to vCenter to bypass authentication and gain unauthorized access to the system" [2]. Broadcom rates it 9.8 (Critical), lists no workaround and has shipped fixes for vCenter 9.1, 9.0, 8.0 and VMware Cloud Foundation 5.x [3]. If you run vCenter, patch it now and then check whether anyone got in first.

What has been confirmed

  • CISA: CVE-2026-123890 is in the KEV catalog, added 20 November 2026 with a due date of 23 November, three days later [1][2]. CISA also marks it for forensic triage, so it expects organizations to look for signs of compromise, not just patch [2].
  • Broadcom: Advisory VMSA-2026-0009, published 19 November and updated 20 November, covers CVE-2026-123890 and four lower-severity flaws in SDDC Manager and VMware Tools for Windows [3]. For CVE-2026-123890 it states: "A malicious actor with network access to vCenter may exploit this issue to bypass authentication" [3].
  • Fixed versions [3]:
    • 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
    • VMware Telco Cloud Platform and Telco Cloud Infrastructure: see Broadcom KB463116
    • vCenter 7.0: Broadcom asks customers with an extended support contract to contact Broadcom Support. No fixed release is listed.
  • Workarounds: none, according to Broadcom [3].
  • Who found it: Broadcom credits Mandiant [3]. Neither Broadcom nor CISA has named a threat actor, and Broadcom's advisory does not itself describe exploitation in the wild. CISA's catalog listing is the confirmation [2].

Why this matters

vCenter manages an organization's virtual servers. Whoever controls it can start, stop, copy or delete those servers, which is why ransomware operators have long targeted it. An authentication bypass needs no password and no user to click anything, only network access to vCenter. A three-day CISA deadline is unusually short and tells you how seriously CISA takes it. Patching closes the hole. It does not tell you whether someone was already inside.

What to do now

  1. Find every vCenter you run. Include vCenter instances inside VMware Cloud Foundation, lab and disaster-recovery sites, and appliances nobody has logged into for a while.
  2. Patch to a fixed release. Move to 9.1.1.0200, 9.0.2.0200 or 8.0 U3m, or VCF 5.2.5 [3]. Broadcom lists no workaround, so there is no safe alternative to the update [3].
  3. If you are on vCenter 7.0, contact Broadcom Support about your extended support options, and plan the move to a supported release [3]. Until then, restrict network access to vCenter to the administrators who need it.
  4. Take vCenter off the internet. It should be reachable only from a management network or VPN. If it was exposed, treat it as a priority for the next step.
  5. Look for signs of earlier access. CISA flags this flaw for forensic triage [2]. Review vCenter and directory service logs going back as far as you retain them for sign-ins you cannot explain, new or changed accounts and roles, unexpected snapshots, exports or virtual machine power changes, and new SSH access to the appliance.
  6. Rotate what vCenter holds. If you find anything suspicious, reset the vCenter administrator and service-account credentials, and the credentials of anything vCenter connects to.

If you are an MSP or MSSP

Check vCenter on every client estate you manage, not just your own, and patch the ones exposed to the internet first. Tell clients who run their own vCenter that the CISA deadline is 23 November.

Frequently asked questions

Is CVE-2026-123890 being exploited?

Yes. CISA added it to the Known Exploited Vulnerabilities catalog on 20 November 2026 [1][2]. Broadcom's advisory does not itself describe exploitation, and no threat actor has been named [3].

Is there a fix?

Yes, for supported releases: vCenter 9.1.1.0200, 9.0.2.0200 and 8.0 U3m, and VMware Cloud Foundation 5.2.5 [3]. Broadcom lists no fixed release for vCenter 7.0 and asks customers with extended support to contact it [3].

Is there a workaround?

No. Broadcom lists none [3]. Limiting network access to vCenter reduces exposure but does not fix the flaw.

What should an organization that runs its own VMware do first?

Find every vCenter, patch the ones reachable from the internet or large internal networks first, then review their logs for access you cannot explain [2][3].

Does this affect VMware Cloud Foundation?

Yes. VCF 5.x is fixed in 5.2.5, and Telco Cloud Platform and Telco Cloud Infrastructure fixes are in Broadcom KB463116 [3].

Who is behind the attacks?

No one has been named [2][3].

How Vijilan helps

Vijilan's SOC watches the systems an organization depends on most, including virtualization and identity infrastructure, around the clock, with machine speed where speed wins and a human approving the actions that carry real risk. ThreatRespond™ runs that on the security tools you already have, for organizations directly and for the MSPs that serve them. Talk to us.

Sources

  1. Known Exploited Vulnerabilities Catalog (CISA)
  2. Known Exploited Vulnerabilities Catalog, JSON feed (CISA)
  3. VMSA-2026-0009: VMware vCenter Server, Cloud Foundation and Tools updates (Broadcom)

Found this useful? Send it to someone who needs it.

Threat notes, once a week

What our SOC actually saw this week: new attack patterns, the detections we shipped against them, and what it means if you run an MSP. Written by the analysts, not by marketing.

One email a week. One click to stop, and we do not sell your address to anyone.

ThreatDefend™

Our stack. Our SOC.

Managed XDR on CrowdStrike Falcon, deployed and run 24/7 by the Vijilan SOC.

See ThreatDefend™

Questions this answers

Is CVE-2026-123890 being exploited?

Yes. CISA added it to the Known Exploited Vulnerabilities catalog on 20 November 2026. Broadcom's advisory does not itself describe exploitation, and no threat actor has been named.

Is there a fix?

Yes, for supported releases: vCenter 9.1.1.0200, 9.0.2.0200 and 8.0 U3m, and VMware Cloud Foundation 5.2.5. Broadcom lists no fixed release for vCenter 7.0 and asks customers with extended support to contact it.

Is there a workaround?

No. Broadcom lists none. Limiting network access to vCenter reduces exposure but does not fix the flaw.

What should an organization that runs its own VMware do first?

Find every vCenter, patch the ones reachable from the internet or large internal networks first, then review their logs for access you cannot explain.

Does this affect VMware Cloud Foundation?

Yes. VCF 5.x is fixed in 5.2.5, and Telco Cloud Platform and Telco Cloud Infrastructure fixes are in Broadcom KB463116.

Who is behind the attacks?

No one has been named.