On November 20, 2026, CISA added CVE-2026-123890 for Broadcom VMware vCenter—an authentication bypass in VMware Directory Service that Broadcom documents as Critical (CVSS 9.8) in VMSA-2026-0009.1. A malicious actor with network access to vCenter can bypass authentication and gain unauthorized access according to Broadcom. CISA sets due date November 23, 2026 and forensic triage required under BOD 26-04.
If coding agents maintain lab vSphere, run Terraform against vCenter, or paste "apply latest patch" playbooks, this KEV entry is identity infrastructure—not a sidecar container you can defer.
TL;DR
| Question | Answer |
|---|---|
| Am I affected? | Any network-reachable vCenter on 9.1.x, 9.0.x, 8.0, 7.0, or VCF/Telco lines in the VMSA matrix before listed fixed builds |
| Is it exploited? | Yes — KEV 2026-11-20 |
| Federal due date? | 2026-11-23 |
| BOD forensics? | Yes |
| Fix | 9.1.1.0200, 9.0.2.0200, 8.0 U3m, VCF 5.2.5, etc.—see VMSA table |
| Workaround? | None per vendor |
| Does data leave my machine (Beam)? | Beam is local; this flaw is vCenter server-side |
What happened
Broadcom published VMSA-2026-0009 on November 19, 2026 and VMSA-2026-0009.1 on November 20 clarifying impacted VMware Tools versions. Mandiant reported CVE-2026-123890 to Broadcom per the advisory. The same bulletin covers SDDC Manager SQL and command injection CVEs and a VMware Tools SAML signature issue—patch trains are cumulative on the 9.1 line (Broadcom note on 9.1.1.0200).
CISA's catalog entry classifies the flaw as authentication bypass using an alternate path or channel (CWE-288) and ties federal action to BOD 26-04 and forensics triage guidance.
Mechanism step by step (from Broadcom)
From VMSA-2026-0009.1 section 3a:
- VMware Directory Service handles identity and directory operations inside vCenter.
- A logic error allows a network-positioned attacker to use an alternate path that skips normal authentication.
- Successful exploitation yields unauthorized access to the vCenter system—management plane control, not just a guest VM escape.
Broadcom assigns no workarounds. That matters for teams who usually "segment until patch Tuesday": exposure to the vCenter management network is enough for the documented attack vector.
Who is affected and fixed versions
| Product line | Fixed version (CVE-2026-123890) |
|---|---|
| vCenter 9.1.x | 9.1.1.0200 |
| vCenter 9.0.x | 9.0.2.0200 |
| vCenter 8.0 | 8.0 U3m |
| vCenter 7.0 | Contact Broadcom support (extended support) |
| VMware Cloud Foundation 5.x | 5.2.5 (async patching guide KB88287) |
| Telco Cloud Platform / Infrastructure | KB463116 per matrix |
Verify builds in Broadcom's FAQ if you run nested VCF or stretched clusters agents document in runbooks.
How to check and patch
Version check (examples):
- vSphere Client → vCenter Summary → Version / Build
- vCenter Server Appliance shell: review /etc/appliance-release and vpxd build output documented in your internal runbook
Patch path:
- Download the fixed image or patch from Broadcom support links in VMSA section 4 (e.g. vCenter 8.0 U3m patch id 16137).
- Stage in maintenance mode with database and SSO backups agents should not skip.
- After upgrade, confirm VMware Directory Service health in VAMI and review vCenter SSO logs for anomalous logins.
For the wider November KEV cluster, see Apache Axis CVE-2026-90436 (Java SOAP stacks) and CVE volume context.
What this means if you run AI coding agents
vCenter is where agents increasingly create VMs, attach networks, and rotate credentials for test clusters:
- Terraform / Pulumi jobs an agent edits can expose management NICs when security groups are wrong.
- Ansible playbooks that "open vCenter to the dev VPN" enlarge the network access precondition Broadcom describes.
- Bug-hunter skills that catalog vCenter in exploit chains make this CVE show up in agent-generated priority lists—verify builds, do not trust model severity alone.
Concrete steps:
- Pin infrastructure PRs that touch vCenter endpoint URLs or firewall rules until builds match VMSA.
- Run
govc aboutor API version probes in CI after agent changes. - Search logs (vCenter events, SSO) for sessions from unusual IPs since mid-November if management was internet-adjacent.
- Treat BOD forensics as a checklist even on private lab: export vCenter audit and identity provider logs before agents rotate configs again.
Beam watches risky commands on developer laptops (credential reads, destructive shell). It does not sit on vCenter, patch ESXi, or block vSphere API calls. Use it to catch an agent curling vCenter admin cookies or rewriting .terraform secrets locally—not as a substitute for VMSA patching.
Historical context
November 20, 2026 added four KEV entries alongside Roller, SAP, and Cisco Expressway. That density matches record CVE discovery pressure teams feel when models surface backlog faster than change windows absorb.
vCenter auth bypass bugs are particularly painful because compromise is management-plane: attackers need not escape a guest VM first. Past incidents in adjacent space (e.g. ARTEX-style agent targeting of admin tools) show why identity SSO around virtualization matters for agent-operated estates.
Broadcom's disclosure timeline matters for change control: VMSA-2026-0009 landed November 19, and VMSA-2026-0009.1 arrived November 20 with VMware Tools scope clarifications. CISA's same-day KEV listing compresses federal due date November 23 against weekend maintenance windows—exactly when unattended agents might propose "patch everything now" scripts without staging.
Companion CVEs in VMSA-2026-0009.1 (same bulletin)
This post centers the KEV auth bypass, but agents often apply one ZIP that must cover the bundle:
| CVE | Component | Severity (vendor) | Attacker model (summary) |
|---|---|---|---|
| 123890 | vCenter VMware Directory Service | Critical 9.8 | Unauthenticated auth bypass with network access |
| 123891 | SDDC Manager | Important 8.1 | Authenticated SQL injection — read/write DB |
| 123892 | SDDC Manager | Important 7.2 | Authenticated command injection on appliance |
| 123893 | SDDC Manager / VCF Installer | Moderate 6.7 | Local priv esc from admin to root |
| 123894 | VMware Tools (Windows) | Moderate 6.7 | SAML token signature bypass in guest |
If an agent-generated runbook mentions only 123890, expand it: SDDC Manager and Tools builds in the matrix may still be vulnerable on the same estate. Broadcom's cumulative note on 9.1.1.0200 is explicit that earlier partial fixes are superseded.
BOD 26-04 and forensic triage (federal readers)
CISA marks forensic triage: Yes for CVE-2026-123890. Even private-sector teams can borrow the checklist:
- Identify vCenter and SSO appliances with management interfaces reachable from beyond the admin VLAN since November 1, 2026.
- Export authentication logs (vCenter events, VMware Identity / SSO, AD FS if integrated) for impossible travel or new API clients.
- Snapshot inventory: clusters, datastores, and permission changes after the suspected window—attackers with vCenter often create hidden admin roles or OAuth clients.
- Preserve hypervisor images before agents "clean up" snapshots during patch automation.
- Document patch build numbers applied—BOD 26-04 expects demonstrable compliance by November 23 for federal systems.
Beam does not collect vCenter logs. It can preserve on-device records of agent shell activity if your patch playbook ran from a laptop—useful to prove who kicked off an emergency govc session.
vCenter hardening beyond the binary patch
Vendor guidance is patch-first, but operators running agents should also:
- Remove vCenter from the public internet. If an agent opened
443to0.0.0.0in a cloud template, revert it before upgrading. - Enforce jump hosts for PowerCLI/Terraform—the documented attack needs network access, not necessarily your domain password.
- Rotate vCenter SSO and local accounts after patch if exposure was broad.
- Reconcile TLS and certificate pinning in CI secrets agents store—compromised vCenter can mint trusted-looking endpoints for downstream theft.
How to update VMware vCenter (operator checklist)
Searchers often look for how to patch VMware vCenter when KEV drops. A defensible sequence aligned with Broadcom's advisory:
- Read VMSA-2026-0009.1 and the FAQ for your exact product row (standalone 8.0 vs VCF bundle).
- Download the target build (e.g. 8.0 U3m patch 16137 or 9.1.1.0200 kit) from Broadcom support—agents should not substitute third-party mirrors.
- Back up vCenter database and snapshot the appliance VM.
- Announce maintenance to teams running CI that provisions VMs—agents may fail mid-job during SSO restarts.
- Apply per Broadcom procedure (VAMI or ISO, depending on deployment).
- Verify build strings and run a smoke test: login, cluster view, VM power ops.
- Re-scan with the same agent inventory script and diff outputs—if versions drift, fail the pipeline.
Automation anti-patterns coding agents introduce
| Anti-pattern | Why it hurts here |
|---|---|
"Set VCENTER_INSECURE=true to unblock Terraform" | Extends MITM window while auth bypass is exploitable |
| One playbook patches prod vCenter before lab | Skips validation of SSO integrations agents did not model |
| Disabling MFA enforcement temporarily during patch | Overlaps with attacker auth-bypass window |
Storing service account keys in repo for govc | Stolen vCenter plus leaked keys equals cluster takeover |
Prefer human-approved change requests with single-CVE scope—the same discipline urged in November outage patch-rush commentary, even though this CVE is unrelated to that news cluster.
What is VMware vCenter (search clarity)
Operators googling what is VMware vCenter during an emergency should read it as the control plane for vSphere, not merely a monitoring dashboard: inventory, VM lifecycle, storage policies, clustering, and the identity layer tying admins and automation accounts together. ESXi hosts run workloads; vCenter holds the keys to reconfigure or destroy them at scale. An auth bypass here is therefore closer to domain admin than to a single VM compromise—relevant when coding agents hold PowerCLI service accounts with Administrator role. Document which automation accounts your agents use before patching so you can rotate them if forensic review finds abuse.
Frequently asked questions
What is CVE-2026-123890?
An authentication bypass in VMware Directory Service inside vCenter, rated Critical (9.8) by Broadcom, exploited in the wild per CISA KEV.
How to patch VMware vCenter for this CVE?
Apply the fixed build for your major version in VMSA-2026-0009.1—for many sites 8.0 U3m or 9.1.1.0200.
Is there a workaround?
No, per Broadcom and CISA—patch or remove exposure.
What is VMware vCenter in one line?
The management plane for vSphere—inventory, VM lifecycle, clustering, and SSO—what developers mean when they automate "the VMware API."
Related reading
- Apache Axis KEV SOAP fault RCE
- Java4Shell and agent-driven Java patching
- CVE volume and agent prioritization
- South Korea bank hack: agents and admin paths
- What AI agent monitoring tracks
Primary sources: VMSA-2026-0009.1, CISA KEV catalog, CVE-2026-123890 at MITRE
Version numbers and advisory text reflect Broadcom and CISA publications as of November 20, 2026. Re-check VMSA before executing agent-generated upgrade scripts.

