Back to all news
Industry NewsUsama Asif5 min read

VMware vCenter Zero-Day (CVE-2026-123890) Exploited: What Businesses Should Do Now

Broadcom fixed CVE-2026-123890, a vCenter zero-day a suspected China-nexus group exploited from September. CISA listed it on 20 November. What to do now.

Illustrative example

On 19 November 2026, Broadcom fixed CVE-2026-123890, a critical authentication bypass in VMware vCenter, and Google reported that a suspected China-nexus espionage group had exploited it since early September. On 20 November, CISA added it to its exploited list along with three other flaws, including an SAP NetWeaver bug fixed a year earlier.

What happened

  • 19 November 2026, the fix. Broadcom published security advisory VMSA-2026-0009 for vCenter. The flaw sits in the VMware Directory Service (vmdir), the directory behind vCenter single sign-on. According to Google, an unauthenticated attacker who can reach its RPC interface on port 2012 can obtain a session as the built-in administrator@vsphere.local account. The Hacker News reports a CVSS score of 9.8.
  • Fixed versions. The Hacker News and ThreatDefence list vCenter 9.1.1.0200, 9.0.2.0200 and 8.0 Update 3m as fixed, with matching builds for VMware Cloud Foundation. For vCenter 7.0 no public fix is listed: customers on an extended support contract are told to contact Broadcom. ThreatDefence reports that there is no workaround.
  • 19 November 2026, the attack report. Google Threat Intelligence Group and Mandiant attribute the exploitation to ARMORY CASTLE, which they formerly tracked as UNC5221 and describe as a suspected PRC-nexus espionage actor. Their report says the group first got in through a BeyondTrust Remote Support zero-day (CVE-2026-102764), then used a tool called BONESAW against vCenter. The tool copied the directory database, extracted the signing key vCenter uses for SAML logins, created an administrator account and forged logins. The group later enabled SSH on the appliance, logged in to ESXi hosts and copied Windows credential database files out of virtual machine disks.
  • 20 November 2026, the CISA listing. CISA added four flaws to its Known Exploited Vulnerabilities catalog: this vCenter bug, SAP NetWeaver CVE-2025-42884, Cisco Expressway CVE-2026-76466 and Apache Roller CVE-2026-129448. Security Affairs reports that US federal civilian agencies were told to fix all four by 23 November.
  • The SAP item is not new. NVD describes CVE-2025-42884 as a flaw that lets an unauthenticated attacker inject JNDI settings into SAP NetWeaver Enterprise Portal. SAP fixed it with Security Note 3660969 on its November 2025 Patch Day and rated it CVSS 6.5. Its listing now means CISA has evidence of exploitation a year after the fix.

What it means for businesses

Our reading, not Broadcom's, Google's or CISA's:

vCenter is the key to every server it manages. Many companies run their ERP, CRM, file servers and domain controllers as virtual machines under vCenter. An attacker with vCenter administrator rights does not need a password for each of those systems; Google's report shows the group reading data straight from virtual machine disks.

Patching closes the door, not the house. The flaw was in use for about two and a half months before the fix. Google states that relying only on reactive patching is not enough. A server patched today can still hold an account or backdoor added in October, so the patch and a compromise check belong together.

Management interfaces should answer only trusted admin hosts. In Google's case the attackers reached vCenter from inside the network, after taking over a remote access appliance. Google's hardening advice limits the vCenter ports (443, 2012, 22 and 5480) to trusted administration addresses and filters outbound traffic, which would have blocked that path to port 2012.

Old fixes still matter. The SAP listing shows attackers using a flaw with a year-old patch. A slow patch cycle for enterprise systems is a standing risk, not a backlog item.

What to do next

  1. List every vCenter you depend on, including test environments, VMware Cloud Foundation stacks and any platform a hosting or managed service provider runs for you, with its version.
  2. Upgrade to a fixed build (9.1.1.0200, 9.0.2.0200 or 8.0 Update 3m or later). If you are on 7.0, which is past end of general support, contact Broadcom if you have extended support, restrict access now and plan the upgrade.
  3. Restrict the management ports to an administration network or jump host, and add outbound filtering on the appliance, as Google recommends.
  4. Check for signs of earlier compromise back to at least early September (Google's earliest evidence): unexpected single sign-on administrators or role changes, SSH being switched on, vpxuser or root logins to ESXi you cannot explain, and the indicators in Google's report.
  5. Bring in incident response if anything looks wrong, and ask your responder whether the vCenter signing key and domain credentials need replacing, since an attacker held both in Google's case.
  6. Patch the rest of the list. If you run SAP NetWeaver Enterprise Portal, confirm SAP Note 3660969 is applied. Check BeyondTrust Remote Support and other remote access tools against their own advisories.
  7. Ask your providers in writing whether they run vCenter for your systems and when they patched it.

For the background on routine patching, see our guide on what software maintenance covers and our security and data protection page.

Timeline Digital, a custom software development company founded in 2013 in Islamabad, builds and runs custom business software as managed projects. Under software maintenance and support agreements and DevOps and cloud infrastructure work, we keep the systems we deliver, and the servers they run on, patched and monitored. Every project starts with a free pilot: Before you commit to the full project, we build 2 to 3 of your key modules as working software, free of charge, ready in about 2 days. Your team tests the pilot, and the full build starts only after you approve it.

Sources

Tags

  • VMware vCenter
  • Cybersecurity
  • CISA KEV
  • SAP NetWeaver
  • Patch Management
  • Virtualization

Start a conversation

Tell us how your business works.

Describe what is slowing your team down. We will help you work out what to build, and how a free pilot lets you judge our work before the full project.

Prefer WhatsApp? Start a chat

What happens next

  1. You send a short brief

    The problem, the people involved and any target date. A senior engineer replies within 4 business hours.

  2. We understand your workflow

    A first call about how your business works today. An NDA can be signed before you share details.

  3. You test a free pilot

    You choose 2 to 3 key modules and we build them first, so you judge real software before the full project.