Tuskira AdvisoryReported, not on KEVLast updatedNovember 19, 2026

CVE-2026-123890

VMware vCenter authentication bypass was used in a zero-day attack, per Google; fixed builds are out, with no public fix for vCenter 7.0

Latest change
First published. Broadcom fixed it November 19, and Google reported zero-day exploitation in early September.

Reachable if a vCenter server below 9.1.1.0200, 9.0.2.0200 or 8.0 U3m, or any vCenter 7.0 or older, can be reached by an attacker on the network. No login is needed. Google says the exploit goes through TCP port 2012, and the attackers it observed reached vCenter from inside the network

Affected
vCenter 9.1, 9.0 and 8.0 below the fixed builds, all 7.0, and vCenter in VCF and Telco Cloud. ESX is not affected
Exploitation
Google and Mandiant report zero-day exploitation by ARMORY CASTLE in early September. Broadcom does not mention it. Not on CISA KEV.
Fix
vCenter 9.1.1.0200, 9.0.2.0200 or 8.0 U3m. No public fix for 7.0; extended support customers ask Broadcom.
Can't patch today
Block TCP 2012 to vCenter from systems outside an allowlist, per Mandiant. Broadcom lists no workaround

If you run vCenter 7.0, there is no public fix for a flaw that has already been used in an attack. Broadcom fixed CVE-2026-123890 on November 19, 2026 in vCenter 9.1.1.0200, 9.0.2.0200 and 8.0 U3m. For 7.0, which reached End of General Support in October 2025, Broadcom says customers with an extended support contract should ask Broadcom Support for a patch. Google says the exploit tool it recovered works against vCenter 7.x and 8.x.

Google Threat Intelligence and Mandiant say a suspected China-nexus espionage group they track as ARMORY CASTLE exploited the flaw as a zero-day in early September 2026, according to forensic evidence from one intrusion. The attackers reached vCenter from another compromised appliance inside the network, so internet exposure is only part of the risk. Broadcom credits Mandiant with the report and does not mention exploitation in its advisory.

Broadcom rates it 9.8 Critical and says anyone with network access to vCenter can use it to bypass authentication. There is no workaround. It is not on CISA's Known Exploited Vulnerabilities catalog. Broadcom says it is a separate issue from CVE-2026-59309, fixed in July, and Google says the attack ran against a vCenter that already had that fix.

Is it reachable for you?

What it is. vCenter is the management server for VMware ESX hosts and the virtual machines on them. Broadcom says CVE-2026-123890 is an authentication bypass in the VMware Directory Service inside vCenter. Google says the flaw lets an attacker who can reach the directory service's RPC interface on TCP port 2012 sign in as administrator@vsphere.local without a password. Google says the tool it recovered then copied the vCenter directory database, took the signing key vCenter uses for single sign-on, and created a new administrator account.

Who is most exposed. Every vCenter below the fixed builds, and every vCenter 7.0, that an attacker can reach on the network. Google says the attackers came in through a different appliance first and then scanned the internal network for vCenter ports 2012, 5480 and 9080. Broadcom says ESX hosts are not affected, and that it does not matter whether Enhanced Linked Mode is in use.

Checks, in three tiers. The first two decide exposure. The third decides priority. Run these only on systems your organization owns.

  1. Which vCenter servers are below the fixed builds? Broadcom says the build is on the Summary tab in the vSphere Client, or in $global:DefaultVIServer.Build after Connect-VIServer in PowerCLI. Include vCenter inside VMware Cloud Foundation, vSphere Foundation and Telco Cloud. Any 7.0, 6.7 or 6.5 vCenter counts as affected.
  2. What can reach vCenter on TCP 2012? Test from server networks, management networks and other appliances, since Google says the attack came from inside the network. Anything that is not another vCenter or a system you know needs that port is a path to close.
  3. Which vCenter servers have no fix available to you? vCenter 7.0 without an extended support contract, and 6.7 or 6.5, have no public fix. These need the network restrictions below until they are upgraded.
What Tuskira checks for this flaw in your environment
vCenter servers below the fixed builds, including any 7.0, reachable on TCP 2012 from other systems
What those vCenter servers control, including the ESX hosts and virtual machines they manage
Across every system you run.
See how Tuskira finds exposed systems

Compensating controls (test them, don't assume them)

Broadcom lists no workaround. It says perimeter and appliance firewalls may help, and that each organization has to decide whether to rely on them. Mandiant gives this hardening guidance.

  • Block TCP 2012 to vCenter from everything that does not need it. Mandiant says an iptables DROP policy on TCP 2012 for addresses outside an allowlist stops the exploit from reaching the directory service. Only if you can list the systems that legitimately connect on that port and test the rule first.
  • Do not rely on the built-in appliance firewall alone. Mandiant says the vCenter appliance firewall managed through the VAMI on TCP 5480 can be turned off by an attacker who gets VAMI access, and does not send remote logs for denied connections. Mandiant recommends its VCSA Hardening and Logging Tool, which sets an iptables inbound DROP policy on management ports and forwards blocked connections and shell activity to remote syslog. Only if you can test it on a non-production vCenter first.

The patch is the only fix. Install vCenter 9.1.1.0200, 9.0.2.0200 or 8.0 U3m, or move vCenter 7.0 and older to a supported release.

What to look for in logs

Broadcom has published no indicators of compromise. Google Threat Intelligence and Mandiant have published indicators and YARA rules for the tools used in this intrusion, linked under Sources, with a fuller set in a GTI Collection for registered users. The signs below come from Google's post.

  • Internal port scans for TCP 2012, 5480 and 9080 from Linux appliances, which Google saw before the attack on vCenter.
  • Webshells named ActiveSer.jsp and u.jsp on Linux appliances, and tools staged in /tmp, per Google.
  • The SUID bit set on /bin/env, which Google says the attackers used to become root on those appliances.
  • An SSH service announcing itself as SSH-2.0-pulsesecure_23345, which Google ties to the group's BEARBONES backdoor.
  • Single sign-on administrator or machine accounts in vCenter that your team did not create, since Google says the exploit tool creates them.

FAQ

Am I exposed to CVE-2026-123890?

You are if a vCenter server is below 9.1.1.0200, 9.0.2.0200 or 8.0 U3m, or runs 7.0 or older, and an attacker can reach it on the network. No login is needed.

Is CVE-2026-123890 being exploited?

Google Threat Intelligence and Mandiant say a suspected China-nexus espionage group exploited it as a zero-day in early September 2026, in one intrusion they describe. Broadcom's advisory does not mention exploitation. It is not on CISA KEV as of the November 18, 2026 catalog release. No public exploit code has been released.

Is there a fix for vCenter 7.0?

Not publicly. Broadcom says vSphere 7 reached End of General Support on October 2, 2025, and that customers with an extended support contract should request patches through those support processes. Google says the exploit tool works against 7.x. Broadcom says to presume 6.5 and 6.7 are affected too.

We patched CVE-2026-59309 in July. Are we covered?

No. Broadcom says CVE-2026-123890 is a new and distinct issue. Google says the attack ran against a vCenter server that already had the CVE-2026-59309 fix.

Do I need to update ESX hosts?

No. Broadcom says ESX is not affected by this advisory.

What else did the same advisory fix?

VMSA-2026-0009 also fixes three SDDC Manager flaws (CVE-2026-123891, SQL injection, 8.1; CVE-2026-123892, command injection, 7.2; CVE-2026-123893, privilege escalation, 6.7), all needing a login, fixed in SDDC Manager 9.1.1.0200, 9.0.2.0100 and 5.2.5. It also fixes CVE-2026-123894 (6.7) in VMware Tools for Windows, fixed in 13.1.5.0 and 12.5.5. None is reported as exploited.

Vendor
Broadcom (VMware)
Product
VMware vCenter, including vCenter inside VMware Cloud Foundation, vSphere Foundation, Telco Cloud Platform and Telco Cloud Infrastructure
Affected versions
vCenter 9.1.x before 9.1.1.0200, 9.0.x before 9.0.2.0200, 8.0 before 8.0 U3m, and 7.0 (Broadcom VMSA-2026-0009). VMware Cloud Foundation 5.x before 5.2.5. Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x and 5.2, and Telco Cloud Infrastructure 3.0 (KB463116). Broadcom says to presume 6.5 and 6.7 are affected. ESX is not affected
Vulnerable component
VMware Directory Service (vmdir) in vCenter, reached over its RPC interface on TCP 2012, per Google
CVSS
9.8 Critical (VMware as CNA, CVSS 3.1). NVD has not added its own score
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (VMware)
CWE
Authentication bypass (Broadcom); no CWE published
Exploitation
Reported, not on KEV
CISA KEV added
Patch
vCenter 9.1.1.0200, 9.0.2.0200 or 8.0 U3m. VMware Cloud Foundation 5.x applies vCenter 8.0 U3m through KB88287 and updates SDDC Manager to 5.2.5. Telco Cloud follows KB463116. vCenter 7.0 has no public fix; Broadcom says customers with an extended support contract should contact Broadcom Support. Broadcom lists no workaround

Updates

Nov 19, 2026. First published. Broadcom fixed CVE-2026-123890 in VMSA-2026-0009. Google Threat Intelligence and Mandiant reported zero-day exploitation by ARMORY CASTLE in early September 2026. Not on CISA KEV (catalog 2026.11.18).

Sources

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

We publish an advisory when a vulnerability is Critical or on CISA KEV, has one identifiable component to check, and has a public proof of concept or reported exploitation. Advisories are updated as exploitation status changes.