Skip to content
AIBRAINWORX / OpenSourceCoder.comLOCAL-FIRST. BUILT IN THE OPEN.
A.I. Cyber Security / Infrastructure & Data

Broadcom Patches Actively Exploited CVE-2026-123890 Authentication Bypass in VMware vCenter

Broadcom issued emergency fixes under VMSA-2026-0009 for CVE-2026-123890, a CVSS 9.8 VMware vCenter Directory Service authentication bypass exploited by ARMORY CASTLE since September 2026.

Listen to this articleBrowser Voice
Ready
Official company logo or product image for broadcom-patches-cve-2026-123890-vmware-vcenter-authentication-bypass
Official image or organization logo from www.rapid7.com; identification only, no endorsement.
Event / context: 2026-11-19. Source check: October 28, 2026.

Broadcom published VMware Security Advisory VMSA-2026-0009 on November 19, 2026, addressing five vulnerabilities across its virtualization portfolio and flagging an actively exploited authentication bypass in VMware vCenter. According to an Emergent Threat Response analysis from Rapid7, the most severe flaw, tracked as CVE-2026-123890, carries a critical CVSSv3 score of 9.8 and enables unauthenticated attackers with network access to gain Administrator privileges. Because threat intelligence teams observed exploitation in the wild roughly two months before the advisory's release, Broadcom has classified the remediation as an emergency change requiring immediate deployment outside standard maintenance schedules.

Emergency Disclosure and Active Exploitation Scope

VMSA-2026-0009 covers five distinct security issues across VMware products, with CVE-2026-123890 representing the primary operational risk for enterprise and telecommunications virtualization clusters. Mandiant privately reported the vulnerability to Broadcom, and joint findings from Mandiant and Google Threat Intelligence confirmed that CVE-2026-123890 had already been exploited in active operations prior to public disclosure.

Specifically, Mandiant and Google Threat Intelligence attributed in-the-wild exploitation of CVE-2026-123890 to ARMORY CASTLE, a Chinese state-linked threat actor, with confirmed activity dating back as early as September 2026. That timeline gives defenders an urgent mandate to audit vCenter management planes for signs of unauthorized administrative access alongside deploying the newly issued updates. In its guidance, Broadcom frames the vCenter patch as an emergency update rather than a routine cycle item, signaling that deferred patching exposes core virtualization control planes to immediate compromise.

Directory Service Architecture and Vulnerability Mechanics

At the technical layer, CVE-2026-123890 is classified under CWE-288 as an authentication bypass using an alternate path or channel within the VMware Directory Service component of vCenter. Because the Directory Service governs identity and authentication orchestration for vCenter deployments, an alternate-path flaw at that boundary allows a remote actor with network reachability to an affected vCenter instance to circumvent credential verification entirely.

Successful exploitation requires no existing credentials and grants the attacker unauthorized access directly as the Administrator user, explaining the 9.8 CVSSv3 rating. Broadcom also clarified in its vendor FAQ that CVE-2026-123890 is completely distinct from CVE-2026-59309, an earlier 2026 vCenter authentication bypass vulnerability. Consequently, organizations that previously patched against CVE-2026-59309 remain vulnerable to CVE-2026-123890; every vCenter environment running a build older than the versions specified in VMSA-2026-0009 must apply the new cumulative release.

Affected Product Lines and Cumulative Patch Matrix

The vulnerability spans multiple generations of VMware Cloud Foundation, vSphere Foundation, standalone vCenter Server, and Telco Cloud platforms. Broadcom notes that the remediation packages are cumulative and map across supported software branches as follows:

  • VMware Cloud Foundation / vSphere Foundation 9.1.x.x: Upgrade to fixed version 9.1.1.0200.
  • VMware Cloud Foundation / vSphere Foundation 9.0.x.x: Upgrade to fixed version 9.0.2.0200.
  • VMware vCenter Server 8.0: Upgrade to fixed version 8.0 U3m.
  • VMware Cloud Foundation 5.x: Upgrade to fixed version 5.2.5.
  • VMware Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x, and 5.2: Apply 8.0 U3m as documented in KB463116.
  • VMware Telco Cloud Infrastructure 3.0: Apply 8.0 U3m as documented in KB463116.
  • VMware vCenter Server 7.0: Contact Broadcom Support for extended-support remediation options.

Mapping those build targets accurately is essential for mixed-version estates, particularly where Telco Cloud Platform or Infrastructure deployments tie back to underlying vCenter 8.0 U3m packages tracked under knowledge base article KB463116.

Operational Impact on Infrastructure and Security Workflows

From a systems engineering and platform operations standpoint, gaining unauthenticated Administrator access to vCenter effectively hands an adversary control over the hypervisor management layer, virtual machine lifecycle operations, and connected infrastructure automation workflows. DevOps teams, platform engineers, and Linux or Windows systems administrators who rely on vCenter APIs for provisioning and orchestration face significant blast-radius risk if management interfaces are reachable from untrusted or compromised internal network segments.

Deployment logistics also introduce immediate workflow friction for infrastructure teams. Rapid7 emphasizes that the patches for CVE-2026-123890 cannot be installed using vCenter Quick Patch. Instead, administrators must execute the standard update mechanism tailored to their specific vCenter, Cloud Foundation, or Telco Cloud deployment topology. For organizations accustomed to lightweight Quick Patch cycles, shifting to full standard upgrade procedures under an emergency change window requires coordinating maintenance dependencies, verifying backup snapshots, and scheduling orchestration checks across integrated tooling.

Remediation Constraints, Workarounds, and Support Caveats

Equally notable for risk management teams is the absence of any vendor-supplied mitigation shortcut. Broadcom lists no workaround for CVE-2026-123890, leaving full patching to the fixed releases as the sole supported path to eliminating the CWE-288 bypass in VMware Directory Service. Organizations with strict change-control governance or compliance obligations cannot rely on configuration toggles to defer the upgrade.

Support lifecycle status creates an additional caveat for legacy environments. While vCenter Server 8.0, Cloud Foundation 5.x, and the 9.x Foundation releases have direct fixed builds, VMware vCenter Server 7.0 requires administrators to contact Broadcom Support directly, with access tied to extended-support customers. Teams still operating vCenter 7.0 without an active extended-support agreement face a licensing and lifecycle barrier to obtaining remediation, underscoring the urgency of auditing version inventories and accelerating migrations onto supported branches.

Automated Vertex AI (gemini-4-hydrogen) primary-source report; reviewed 2026-11-19.

Follow your curiosity.

Pass the signal.