# VMware vCenter Zero-Day CVE-2026-123890 Exploited Since September

- URL: https://usa-24.com/vmware-vcenter-zero-day-patch/
- Publisher: USA 24
- Section: Cybersecurity
- Published: 2026-11-21T05:02:23.090Z
- Updated: 2026-11-21T05:02:23.095Z
- Topics: VMware, Zero-Day Vulnerabilities, Broadcom, Cyber Espionage, Patch Management, Cybersecurity

> Broadcom patched CVE-2026-123890, a CVSS 9.8 VMware vCenter bypass that a suspected China-linked group exploited from early September. vCenter 7.0 has no public fix.

## Key takeaways

- Broadcom patched CVE-2026-123890, a CVSS 9.8 authentication bypass in VMware vCenter, on Thursday, November 19, 2026.
- Mandiant says the suspected China-nexus group Armory Castle began exploiting the flaw in early September, more than two months before the fix.
- Per Mandiant, the group first got in through a separate BeyondTrust Remote Support zero-day, CVE-2026-102764, then abused vCenter.
- Fixed builds are vCenter 9.1.1.0200, 9.0.2.0200 and 8.0 U3m, while vCenter 7.0 has no public fix and reached end of general support in October 2025.
- Broadcom has not confirmed the attacks and has not disclosed how many organizations were compromised.

A VMware vCenter zero-day, tracked as CVE-2026-123890, has been exploited since early September by a suspected China-linked espionage group. Broadcom shipped fixes on Thursday, November 19, and Google's threat intelligence team published its attribution the same day. Administrators now face a known attack and an emergency patch at the same time, and the gap between those two events is the part that matters most for anyone running VMware in production.

## What the VMware vCenter zero-day allows

The flaw is an authentication bypass in the VMware Directory Service. A remote attacker with network access can obtain an administrator session on vCenter without a password. Broadcom rates it CVSS 9.8, which places it in the critical band, according to [SecurityWeek](https://www.securityweek.com/newly-patched-vmware-vcenter-flaw-exploited-as-zero-day-by-chinese-apt/) and [The Hacker News](https://thehackernews.com/2026/11/critical-vmware-vcenter-flaw-cvss-98.html).

The fix ships under advisory VMSA-2026-0009, which also covers four other flaws in VMware SDDC Manager and VMware Tools for Windows. Those issues are separate from the vCenter bug, so a patch that only touches vCenter does not close every item in the advisory. Teams that manage SDDC Manager and VMware Tools should read the full advisory rather than stopping at the headline flaw.

The reason this bug matters so much is the role vCenter plays. vCenter is the central console administrators use to run VMware hosts and virtual machines. According to [The Hacker News](https://thehackernews.com/2026/11/critical-vmware-vcenter-flaw-cvss-98.html), vCenter manages ESXi hosts and virtual machines, so an attacker who controls it can reach the systems it oversees. That reach is what makes the flaw a serious problem for any enterprise, hospital, university, bank or federal agency that runs VMware.

Broadcom lists no workaround. Its FAQ gives no workaround and notes that an organization's own defenses may still reduce exposure. That leaves patching as the main remedy, with the exception of vCenter 7.0, which has no public fix at all.

## How Armory Castle got in and what it took

Google Threat Intelligence Group and Mandiant attribute the exploitation to a suspected China-nexus espionage group they track as Armory Castle, formerly UNC5221. [Help Net Security](https://www.helpnetsecurity.com/2026/11/20/vmware-vcenter-zero-day-cve-2026-123890-exploited/) reports that Mandiant says the group exploited the flaw in early September 2026 using a custom Go tool called BONESAW, more than two months before the patch.

The group did not start with vCenter. Per Mandiant, it first got in through a separate zero-day in BeyondTrust Remote Support, tracked as CVE-2026-102764. From there, it stole LMDB data, pulled SAML signing material and created a single sign-on administrator account, as [SOC Prime](https://socprime.com/blog/cve-2026-123890-critical-vmware-zero-day-exploited-by-china-linked-hackers/) describes the intrusion.

That sequence shows an identity-focused campaign, not a single server compromise. Signing material of the kind the group pulled can let an attacker forge single sign-on logins. A new administrator account in single sign-on can also outlast a password change on the account that was originally abused. Teams should audit identity systems and remote-access tools alongside the vCenter patch.

Armory Castle is not new to VMware. Google counts this as the group's second VMware zero-day of 2026, according to the [HBS weekly cybersecurity summary](https://hbs.net/cybersecurity-weekly/this-week-in-cybersecurity-november-20-2026). Mandiant also found that the group had a tool ready before the July disclosure of the earlier vCenter bug, CVE-2026-59309, which was disclosed on July 29. Broadcom says the new flaw is a separate issue from that one.

Two vCenter authentication bypasses in one year is a clear signal. A July patch does not mean vCenter is safe from this class of bug, and administrators should not assume an older fix covers the new flaw.

## Which VMware vCenter builds are fixed

The fixed builds are listed in the advisory as reported by [Malware News](https://malware.news/t/cve-2026-123890-vcenter-zero-day-exploited-by-armory-castle/127514). For VMware Cloud Foundation, [SecurityOnline](https://securityonline.info/vcenter-zero-day-cve-2026-123890-exploited/) reports that 5.x is fixed in 5.2.5.

| Product line | Fixed version or status |
|---|---|
| vCenter 9.1 | 9.1.1.0200 |
| vCenter 9.0 | 9.0.2.0200 |
| vCenter 8.0 | 8.0 U3m |
| VMware Cloud Foundation 5.x | 5.2.5 |
| vCenter 7.0 | No public fix |

Confirm your build number in vCenter before you do anything else. Many environments run mixed versions across sites, so check each vCenter instance rather than assuming a single build.

vCenter 7.0 is the hard case. It reached end of general support in October 2025, and customers with an extended support contract must ask Broadcom for a fix, as [SecurityWeek](https://www.securityweek.com/newly-patched-vmware-vcenter-flaw-exploited-as-zero-day-by-chinese-apt/) notes. The sources reviewed do not say how many vCenter 7.0 systems remain unpatched or what Broadcom will do for them.

Organizations that cannot move off vCenter 7.0 soon should contact Broadcom about extended support now. They should also reduce network exposure to the directory service, which the advisory addresses through firewall controls.

## Why Broadcom's wording on attacks matters

Broadcom's advisory does not mention in-the-wild exploitation, and the company has not confirmed the attacks. It has not said whether it knew about the exploitation before it released the patch. It has also not disclosed how many organizations were compromised.

Broadcom's FAQ says the fix "qualifies under ITIL methodologies as an emergency change" and urges customers to consult their security staff on timing. That label tells operations teams to treat the update as urgent rather than waiting for a routine maintenance window.

The gap between the attribution and the vendor's language is the key tension here. Mandiant describes a campaign running since September, while Broadcom's public language is narrower. Readers should treat the attribution as the most detailed account available, while remembering it comes from a security firm rather than the vendor.

The sources reviewed also did not confirm whether CISA has added CVE-2026-123890 to its Known Exploited Vulnerabilities catalog. Check that catalog directly before relying on any federal deadline or compliance timeline tied to this flaw.

## What IT and security teams should do now

The advisory and the threat reports point to a clear order of operations. Start with the management plane, then check for signs that the attacker got in.

- Confirm vCenter, VMware Cloud Foundation and SDDC Manager build numbers against the fixed versions in VMSA-2026-0009.
- Patch management servers first, then the rest of the environment.
- Look for unexpected single sign-on administrator accounts and any changes to the VMware Directory Service.
- Check whether SSH is enabled on hosts, and look for unexpected SSH keys on ESXi hosts.
- Review logs for suspicious access to virtual disk files.
- Audit BeyondTrust Remote Support deployments for CVE-2026-102764 and confirm with the vendor whether a fix is available. The sources reviewed did not address this.
- Restrict network access to the directory service and vCenter management interfaces.

If you find evidence of compromise, treat single sign-on credentials and signing material as exposed, not only the vCenter console. Rotating the console password alone would leave the attacker's other footholds in place.

## What comes next

Three developments will tell administrators how serious this campaign is. The first is whether Broadcom confirms in-the-wild exploitation, which it has not done so far. The second is whether CISA adds the flaw to its catalog. The third is what Broadcom will do for vCenter 7.0 customers who cannot upgrade.

The BeyondTrust zero-day is the other open thread. Its patch status and whether it was used against other customers are not addressed in the sources reviewed, and that answer matters because it is the group's way in.

USA 24 has covered how CISA flags exploited bugs in a [LiteLLM flaw used in AI attacks](https://usa-24.com/litellm-cve-2026-40217-exploited/), and a [Brotli flaw under active attack](https://usa-24.com/cve-2026-111497-brotli-flaw-exploited/) carries its own federal deadline. Both are reminders that exploited-flaw lists change quickly, so vCenter administrators should check them often this week.

## Frequently asked questions

### What is CVE-2026-123890?

CVE-2026-123890 is a critical authentication bypass in the VMware Directory Service that affects VMware vCenter. A remote attacker with network access can obtain an administrator session without a password. Broadcom rated it CVSS 9.8 and fixed it on November 19, 2026, under advisory VMSA-2026-0009.

### Which vCenter versions are fixed for the VMware vCenter zero-day?

The fixed builds are vCenter 9.1.1.0200, 9.0.2.0200 and 8.0 U3m, and VMware Cloud Foundation 5.x is fixed in 5.2.5. vCenter 7.0 has no public fix because it reached end of general support in October 2025. Customers with an extended support contract need to ask Broadcom for a fix.

### Who is exploiting the VMware vCenter zero-day?

Google Threat Intelligence Group and Mandiant attribute the activity to a suspected China-nexus espionage group they track as Armory Castle, formerly UNC5221. Mandiant says the group used a custom Go tool called BONESAW starting in early September 2026. Broadcom has not confirmed the attacks.

### Is there a workaround for CVE-2026-123890?

Broadcom lists no workaround for the flaw, and its FAQ provides none. The FAQ notes that an organization's own defenses may still reduce exposure. Applying the patch for your vCenter version is the main remedy.

## Sources

1. [VMware vCenter CVE-2026-123890 Zero-Day Exploited — SecurityWeek](https://www.securityweek.com/newly-patched-vmware-vcenter-flaw-exploited-as-zero-day-by-chinese-apt/)
2. [VMware vCenter zero-day exploited for months before patch (CVE-2026-123890) — Help Net Security](https://www.helpnetsecurity.com/2026/11/20/vmware-vcenter-zero-day-cve-2026-123890-exploited/)
3. [VMware patches vCenter zero-day exploited in attacks since September — BleepingComputer](https://www.bleepingcomputer.com/news/security/vmware-patches-vcenter-zero-day-exploited-in-attacks-since-september/)
4. [Critical VMware vCenter Zero-Day Flaw Lets Network Attackers Bypass Authentication — The Hacker News](https://thehackernews.com/2026/11/critical-vmware-vcenter-flaw-cvss-98.html)
5. [CVE-2026-123890: Critical VMware vCenter Zero-Day Exploited by China-Linked Hackers — SOC Prime](https://socprime.com/blog/cve-2026-123890-critical-vmware-vcenter-zero-day-exploited-by-china-linked-hackers/)
6. [VMware VCenter Zero-day CVE-2026-123890 Patched — SecurityElites](https://securityelites.com/news/vmware-vcenter-zero-day-cve-2026-123890-patched/)
7. [This Week in Cybersecurity (November 20, 2026) — HBS](https://hbs.net/cybersecurity-weekly/this-week-in-cybersecurity-november-20-2026)
8. [CVE-2026-123890: vCenter Zero-Day Exploited by Armory Castle — Malware News](https://malware.news/t/cve-2026-123890-vcenter-zero-day-exploited-by-armory-castle/127514)
9. [VMware vCenter Zero-Day CVE-2026-123890 Exploited in the Wild — SecurityOnline](https://securityonline.info/vcenter-zero-day-cve-2026-123890-exploited/)
