VMware vCenter Hit by CVSS 9.8 Zero-Day: Armory Castle Has Been Inside Since September
Broadcom shipped emergency fixes on November 19 for CVE-2026-123890, a CVSS 9.8 pre-auth session-key disclosure in VMware Directory Service that Mandiant says Chinese state actor Armory Castle has exploited since September. vCenter 7.0 has no patch at all.
Broadcom shipped emergency fixes on November 19 for CVE-2026-123890, a CVSS 9.8 pre-auth session-key disclosure in the VMware Directory Service that underpins vCenter. Google Mandiant attributes months of in-the-wild exploitation to the Chinese state actor it tracks as Armory Castle, previously known as UNC5221 and Warp Panda, with activity dating back to September. The mechanics are as bad as the score suggests: the flaw is reachable pre-auth over DCE/RPC, requires no valid credentials for initial access, and hands attackers a session key that leads to admin control of the virtualization layer.
The uncomfortable detail sits at the bottom of the advisory. vCenter 7.0, which has been end-of-support since October 2025, has no patch for this vulnerability and will never get one. Every organization still running vCenter 7.0 is running software with a known 9.8 pre-auth zero-day that a state actor has been working since September, with no vendor remediation path short of migration. That is not a patching backlog problem. That is a permanent exposure problem, and the number of estates in that position is larger than anyone's slide deck admits.
Key Takeaways: What Matters Most?
- CVE-2026-123890 is a CVSS 9.8 pre-auth session-key disclosure in VMware Directory Service, exploited as a zero-day since September 2026.
- Google Mandiant attributes the exploitation to Chinese state actor Armory Castle, formerly tracked as UNC5221 and Warp Panda.
- The attackers used a Go tool called Bonesaw to steal LMDB data and hijacked SAML signing material to provision SSO admin accounts.
- vCenter 7.0, end-of-support since October 2025, has no patch for CVE-2026-123890, leaving EOL estates permanently exposed.
- Emergency fixes shipped November 19, more than two months after exploitation began, via DCE/RPC pre-auth admin access.
Takeaways like these, every weekday morning. Get the briefing
What Armory Castle actually did
Mandiant's attribution carries a specific toolkit and a specific objective. The actors deployed a Go tool called Bonesaw to steal LMDB data from compromised vCenter instances, and they hijacked SAML signing material to provision SSO admin accounts, per The Hacker News coverage. The SAML move deserves attention, because a forged signing relationship is a persistence mechanism that survives vCenter reinstalls and password resets. An attacker holding your SAML signing material does not need the vulnerability anymore; they need only your identity infrastructure to keep trusting the tokens they mint.
The pre-auth nature of the initial bug sets the difficulty floor low. DCE/RPC is a protocol that exists to be reachable by management networks, which means segmentation errors, exposed management interfaces, or overly flat networks convert directly into attack surface. A CVSS 9.8 pre-auth disclosure in the directory service of a hypervisor management plane is close to the maximum practical value of a vulnerability, and Mandiant says it was being used in the wild for months before a fix existed. If you run vCenter and have not checked your SAML configuration and admin account provenance, assume the worst and verify.
The timeline is the second story inside the story. Exploitation since September, fixes on November 19. That is more than two months of unpatched, actively exploited exposure in the management layer that controls the servers running everything else. Organizations that treated the virtualization layer as settled infrastructure, too boring to monitor closely, handed a state actor the quietest possible foothold: the thing that controls where workloads run and what they trust.
The AI datacenter angle, and the trade-off nobody prices
The AI buildout has made this class of infrastructure risk newly expensive. GPU clusters, training runs, and inference farms all ride on virtualization and management software like vCenter, and the industry's risk conversation has focused almost entirely on model weights, prompt injection, and data leakage. A 9.8 pre-auth zero-day in the layer beneath all of that reframes the priority order. An attacker with vCenter admin and forged SAML tokens does not need a data poisoning scheme to steal a training run; they need only the access the hypervisor management plane already grants them.
The vCenter 7.0 situation is where the honest cost lands. Broadcom's fix program covers supported versions; EOL estates get nothing. The organizations most likely to be on 7.0 are those that deferred migration costs, possibly for years, and the deferral now converts into an incident-response line item with a hard deadline, because the vulnerability is known, weaponized, and attributed. Migration under incident pressure is the most expensive possible way to do it, and it is now the only path for anyone on unsupported vCenter with an internet-reachable management plane.
What To Do About It
- Patch supported vCenter immediately: Apply Broadcom's November 19 emergency fixes for CVE-2026-123890 today, not in the next maintenance window; the bug is pre-auth and actively exploited.
- Hunt for September access, not just the CVE: Because Armory Castle used Bonesaw to steal LMDB data and hijacked SAML signing material, review every SSO admin account's provenance and rotate SAML signing material on any vCenter with exposure.
- Isolate the management plane now: Restrict DCE/RPC reachability to a dedicated management network with no lateral paths; pre-auth bugs are harmless to hosts attackers cannot reach.
- Inventory vCenter 7.0 estate: Every instance on EOL 7.0 has no patch and no fix coming, so treat that inventory as a migration project with an immediate start date, not an annual cleanup item.
The Bottom Line
A CVSS 9.8 pre-auth flaw in vCenter was exploited by a Chinese state actor for more than two months before fixes arrived on November 19, and the SAML hijacking documented by Mandiant means some compromises will outlive the patch. For anyone on vCenter 7.0, there is no patch and never will be, so the choice is migrate or remain exposed to a known, weaponized vulnerability. The AI era's security debate focuses on models and agents, but this week's sharpest lesson is older: the management layer beneath everything got popped, and it had no plan for the day it did.
Sources
Frequently Asked Questions
Share this article