1. Executive summary
Broadcom published VMSA-2026-0009 on 2026-11-19, addressing five vulnerabilities in VMware products. The most severe, CVE-2026-123890, is a critical (CVSS 9.8) authentication bypass in the VMware Directory Service component of vCenter that lets an unauthenticated attacker with network access gain access as the Administrator user. Mandiant/Google Threat Intelligence reports in-the-wild exploitation by a Chinese state-linked actor it names ARMORY CASTLE as early as September 2026; that attribution rests on a single source and is unconfirmed by MITRE ATT&CK. Separately, CVE-2026-99312 in Linux KVM allows a guest VM to cause denial of service or memory corruption on an AMD host running nested virtualization; it is rated 8.8 HIGH in NVD but the source quotes a CVSSv3 score of 5.5, a discrepancy noted below. For EMEA financial services, the vCenter flaw is the priority: vCenter is the control plane for ESXi hosts and virtual machines, and compromise gives an attacker control over the virtualised estate and its workloads.
2. Regulatory framing
| Article | Trigger (the fact in this item) | Practical impact |
|---|---|---|
| DORA Art. 17: ICT-related incident management process | Mandiant/Google Threat Intelligence reports in-the-wild exploitation of CVE-2026-123890 by a named state-linked actor as early as September 2026 | Clients running affected vCenter versions must determine whether the exploitation window applies to their estate and run it through their incident management process |
| DORA Art. 19: reporting of major ICT-related incidents to competent authorities | A critical authentication bypass in the vCenter control plane with confirmed in-the-wild exploitation | If exploitation is confirmed on a client estate, the incident may meet the major-incident threshold and require reporting to the competent authority |
| NIS2 Art. 23: incident reporting obligations | Same trigger: confirmed exploitation of a critical vCenter flaw | In-scope entities must assess whether the incident is significant and report within the NIS2 timelines |
3. Technical analysis & attack chain
CVE-2026-123890 is an authentication bypass using an alternate path or channel (CWE-288) in the VMware Directory Service component of vCenter. Broadcom assigned it a critical CVSSv3 score of 9.8. A malicious actor with network access to an affected vCenter deployment can exploit it without credentials to bypass authentication and gain unauthorised access to the system as the Administrator user. Mandiant privately reported the issue to Broadcom.
The confirmed exploitation sequence, as reported by Mandiant/Google Threat Intelligence via Rapid7:
- The attacker obtains network access to an affected vCenter deployment. No credentials are required.
- The attacker sends traffic to the VMware Directory Service that exploits the alternate-path authentication bypass.
- Authentication is bypassed and the attacker gains access to vCenter as the Administrator user.
Mandiant/Google Threat Intelligence confirmed in-the-wild exploitation of CVE-2026-123890 by Chinese state-linked threat actor ARMORY CASTLE as early as September 2026. This attribution is single-sourced (Rapid7 reporting Mandiant's finding) and ARMORY CASTLE has no MITRE ATT&CK profile in the reference data supplied; treat the attribution as unconfirmed. No post-exploitation detail (persistence, lateral movement, data access) is stated in public reporting.
CVE-2026-123890 is distinct from CVE-2026-59309, the vCenter authentication bypass Broadcom addressed earlier in 2026 in VMSA-2026-0006. The vendor FAQ states that all vCenter systems below the versions fixed by VMSA-2026-0009 require the new update, including systems that already received the earlier fix. Broadcom characterises the vCenter update as an emergency change.
Affected and fixed versions from VMSA-2026-0009:
| VMware product | Affected version | Fixed version / patch |
|---|---|---|
| VMware Cloud Foundation / vSphere Foundation | 9.1.x.x | 9.1.1.0200 |
| VMware Cloud Foundation / vSphere Foundation | 9.0.x.x | 9.0.2.0200 |
| VMware vCenter Server | 8.0 | 8.0 U3m |
| VMware vCenter Server | 7.0 | Contact Broadcom Support (extended-support customers) |
| VMware Cloud Foundation | 5.x | 5.2.5 |
| VMware Telco Cloud Platform | 3.0, 4.x, 5.0.x, 5.1.x, 5.2 | 8.0 U3m, KB463116 |
| VMware Telco Cloud Infrastructure | 3.0 | 8.0 U3m, KB463116 |
The fixes are cumulative. The vCenter 8.0 U3m and 9.0.2.0200 updates introduce a "Back-in-Time" restriction that blocks upgrades to VMware Cloud Foundation 9.1.1; Broadcom advises customers in an active upgrade to review the vendor FAQ and interoperability matrix. Updating vCenter temporarily makes its management interfaces unavailable, but Broadcom states that running virtual machine and container workloads continue to operate. Broadcom lists no workaround, and the patches cannot be applied using vCenter Quick Patch.
VMSA-2026-0009 also details four more CVEs, some of them high-severity. The source does not name them or give their scores.
VMSA-2026-0010 warns that Cloud Foundation, Aria Operations and VCF Operations HCX all use Apache, which has a remote code execution vulnerability. The source rates it 9.8; NVD records CVE-2026-119618 as 8.1 HIGH with EPSS 2% and CWE-362 (race condition). The verified NVD values are used here; the source's 9.8 rating is noted as a discrepancy. No further technical detail on this flaw is stated in public reporting.
CVE-2026-99312 in Linux KVM allows an attacker with access to a guest virtual machine to cause denial of service or memory corruption on the host. It affects only users of AMD processors who employ nested virtualisation, the practice of running a hypervisor inside a virtual machine. It is not a guest-to-host escape. NVD records it as 8.8 HIGH with EPSS 0%; the source quotes a CVSSv3 score of 5.5, a discrepancy noted here. Security researcher Oren Tomtov of Accomplish.ai reported that the flaw let him access 127 GB of host RAM on a Digital Ocean Droplet. Yomtov told Digital Ocean and the Linux kernel security team about the flaw in October. Maintainers delivered a fix to the mainline kernel on November 2, with full fixes landing on the 17th. The CVE appeared on November 18. Yomtov and Terra Security posted analysis of the flaw and took the posts down within hours; The Register understands Digital Ocean asked for the posts to come down to allow more time to update its Linux implementations. Terra's analysis asserts the flaw was introduced to KVM in 2022 when developers wrote a fix for CVE-2022-3344, and that 3.2 percent of CVEs in the Linux kernel were introduced by the fix for another CVE. The flaw is defeated without an update by disabling nested virtualisation in KVM.
4. Mitigation & containment
P1 (within 24 hours)
- Upgrade vCenter to the fixed version for your branch: 9.1.1.0200 for Cloud Foundation / vSphere Foundation 9.1.x.x, 9.0.2.0200 for 9.0.x.x, 8.0 U3m for vCenter Server 8.0, 5.2.5 for Cloud Foundation 5.x. Extended-support customers on vCenter 7.0 must contact Broadcom Support. Apply the update outside normal patch cycles; Broadcom characterises it as an emergency change.
- Do not use vCenter Quick Patch; Broadcom states the patches cannot be applied that way. Use the standard update mechanism for your deployment.
- Restrict network access to vCenter management interfaces to dedicated management networks. The flaw requires network access to the affected vCenter deployment, so reducing reachability limits exposure.
- If you are mid-upgrade to Cloud Foundation 9.1.1, review the vendor FAQ and interoperability matrix before applying 8.0 U3m or 9.0.2.0200, which carry a "Back-in-Time" restriction blocking that upgrade path.
- On AMD hosts running nested virtualisation, disable nested virtualisation in KVM. The source states this defeats CVE-2026-99312 without an update.
P2 (within 72 hours)
- Hunt vCenter and VMware Directory Service logs for authentication events consistent with unauthenticated access to the Administrator account, focusing on the period from September 2026 onward given the reported exploitation window.
- Apply the kernel fix for CVE-2026-99312 where nested virtualisation cannot be disabled. The mainline fix landed on November 2 and full fixes on November 17; map those to your distribution's kernel packages.
P3 (within 7 days)
- Review exposure to CVE-2026-119618 in Cloud Foundation, Aria Operations and VCF Operations HCX. No fixed version for the Apache component is named in public reporting.
- Confirm whether any vCenter system remains below the VMSA-2026-0009 fixed versions, including systems that received the earlier VMSA-2026-0006 fix, which the vendor FAQ states still require the new update.
5. Indicators of compromise
No indicators of compromise available in the source material.
The sources describe no file hashes, network indicators, file paths or registry keys for this item. The behaviour below is the only observable described.
Behavioural indicators
| Behaviour | Where to observe | Confidence |
|---|---|---|
| Unauthenticated access to vCenter resulting in Administrator-level session | vCenter and VMware Directory Service authentication logs | Medium; described by Mandiant via Rapid7, single-sourced |
| Guest VM causing host memory pressure or corruption on AMD hosts with nested virtualisation | KVM host kernel logs, hypervisor memory telemetry | Medium; described by The Register citing the researcher |
6. Detection
Insufficient indicators to author detection rules.
The sources give no distinctive strings, command-line flags, file names, registry keys or hard-coded values present in an artefact of the threat. The CVE identifiers and product names are not threat artefacts and would detect reporting about the flaw, not exploitation of it.
CVE assessment
4 referenced CVEs — 1 critical (CVSS ≥ 9.0)
| CVE | CVSS | Exploited | EPSS | Summary |
|---|---|---|---|---|
| CVE-2026-123890 | 9.8 Critical | — | — | VMware vCenter contains an authentication bypass vulnerability in the VMware Directory Service. Affected versions: 9.1.x (fixed… |
| CVE-2026-99312 | 8.8 High | — | 0% | In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Unconditionally reset MMU context when emulating… |
| CVE-2026-119618 | 8.1 High | — | 2% | Concurrent Execution using Shared Resource with Improper Synchronization vulnerability in Apache HTTP Server's mod_http2 in ass… |
| CVE-2022-3344 | 5.5 Medium | — | 0% | A flaw was found in the KVM's AMD nested virtualization (SVM). A malicious L1 guest could purposely fail to intercept the shutd… |
7. Sources
- Rapid7 Blog, "CVE-2026-123890: Critical Authentication Bypass in VMware vCenter", https://www.rapid7.com/blog/post/etr-cve-2026-123890-critical-authentication-bypass-vmware-vcenter, 2026-11-19
- The Register, "Flaws in VMware and KVM need attention, if you have time while fixing Java, PHP, and everything else", https://www.theregister.com/security/2026/11/20/flaws-in-vmware-and-kvm-need-attention-if-you-have-time-while-fixing-java-php-and-everything-else/5311193, 2026-11-20
- The Hacker News, "Critical VMware vCenter Flaw (CVSS 9.8) Lets Network Attackers Bypass Authentication", https://thehackernews.com/2026/11/critical-vmware-vcenter-flaw-cvss-98.html
8. Adverse Trace position
Adverse Trace assesses CVE-2026-123890 as the priority for EMEA financial services clients: critical (CVSS 9.8), unauthenticated, network-reachable, and reported exploited in the wild since September 2026, though that exploitation claim and the ARMORY CASTLE attribution are single-sourced from Mandiant via Rapid7 and unconfirmed by MITRE ATT&CK. CVE-2026-99312 is rated 8.8 HIGH by NVD (the source quotes 5.5) but is constrained to AMD hosts running nested virtualisation and is defeated by disabling that feature. CVE-2026-119618 is 8.1 HIGH with EPSS 2%. None of the four CVEs is in CISA KEV. We will monitor for a Broadcom workaround or further exploitation reporting on CVE-2026-123890 and update this advisory if either appears.
Published via PulseTrace — Adverse Trace threat intelligence.