CVE-2026-123890: VMware vCenter authentication bypass exploited since September — CISA patch deadline is November 23

A critical unauthenticated vCenter Directory Service flaw was used in real intrusions weeks before disclosure. CISA gives federal agencies until November 23 — everyone else should not wait longer.
CoeLab Real-World Impact: 94/100 — Urgent. Editorial score v1.0. Evidence checked 2026-11-22T10:10:43.171342+00:00. CVSS and EPSS are separate measures, not this editorial score.
Rating breakdown: exploitation: 30, reachability: 25, consequences: 24, operational relevance: 15.
Who is affected
Anyone running VMware vCenter Server on an unpatched release branch. Broadcom's advisory VMSA-2026-0009.1, first issued November 19 and updated November 20, 2026, lists CVE-2026-123890 as critical (maximum CVSSv3 base score 9.8) and provides fixed versions for every current branch: VMware Cloud Foundation and vSphere Foundation vCenter 9.1.x is fixed in 9.1.1.0200, 9.0.x.x in 9.0.2.0200, standalone vCenter Server 8.0 in 8.0 U3m, and Cloud Foundation 5.x in 5.2.5. Telco Cloud Platform versions 3.0, 4.x, 5.0.x, 5.1.x and 5.2, plus Telco Cloud Infrastructure 3.0, are remediated through Broadcom KB463116.
vCenter Server 7.0 is in a worse position: the advisory lists no fixed version, directing customers to contact Broadcom Support under an extended support contract. Since the flaw exists on 7.x appliances and every other branch, unpatchable 7.x deployments are effectively stuck carrying a live attack path — network isolation becomes the only realistic control there until a targeted fix becomes available.
The same advisory bundles four other issues (SDDC Manager SQL injection at 8.1, authenticated command injection at 7.2, SDDC Manager local privilege escalation and a VMware Tools SAML token signature bypass, each at 6.7), so organizations applying the vCenter patch should check their SDDC Manager and Windows guest Tools versions in the same maintenance window.
Real-world impact and exploitation evidence
This is not a theoretical critical rating. CISA added CVE-2026-123890 to the Known Exploited Vulnerabilities catalog on November 20, 2026, with a federal patching deadline of November 23 — three days after catalog inclusion. The catalog entry describes an unauthenticated attacker with network access to vCenter bypassing authentication and gaining unauthorized access, and flags forensic triage as required, reflecting real intrusion cleanup rather than a precautionary listing.
Google Threat Intelligence and Mandiant's ARMORY CASTLE report, published November 19 alongside the advisory, provides the clearest exploitation picture. Forensic evidence shows the group exploited this exact vulnerability in early September 2026 — roughly two and a half months before public disclosure — using a Golang utility named BONESAW. In one observed intrusion, the actor moved laterally from a compromised remote-support appliance to an internal Linux appliance, escalated to root, and used BONESAW against an internal vCenter server to create an unauthorized Single Sign-On administrator account and exfiltrate the vmdir LMDB database for offline parsing.
The chain the report describes is a full-compromise sequence, not a denial of service: disclosure of the SRP session key yields an authenticated session as the built-in [email protected] account, after which an attacker can run commands through the Directory Service RPC interface, download the directory database, extract the Security Token Service SAML signing key, forge administrative SAML assertions, and create persistent rogue SSO accounts. A companion utility, SAWSNAKE, enables subsequent Golden SAML-style authentication bypass. Recovery from that level of persistence means assuming credential and signing material is stolen, not merely that one patch replaces one file.
Two timeline details deserve weight. First, a recovered BONESAW binary carries a Go build timestamp of July 13, 2026 — before the July 29 disclosure of the related vCenter flaw CVE-2026-59309 — and Mandiant's logs show the actor running it in September against a vCenter already patched for that older bug. Patching for CVE-2026-59309 therefore bought no protection here. Second, BONESAW is explicitly described as achieving full compromise on 7.x and 8.x appliances, which aligns with the advisory's branch-wide response matrix.
Attack prerequisites
The technical core is an unauthenticated Secure Remote Password (SRP-6a) session key disclosure vulnerability in the vCenter Directory Service's DCE/RPC interface. The published CVSSv3 vector is AV:N/AC:L/PR:N/UI:N — network reachable, low complexity, no privileges, no user interaction. An attacker needs network reachability to vCenter's management interfaces; the intrusion report singles out TCP port 2012 (the Single Sign-On control RPC interface) as the path BONESAW used, alongside routine scanning of management ports 443, 5480 and 9080. Once the shared session key is obtained, no password and no victim interaction is required.
Practically, there are only two real gating conditions: the attacker must reach the vCenter management plane over the network, and the deployed version must predate the fixed releases. Neither condition is unusual. vCenter is reachable from internal networks in nearly every VMware estate, and internet-facing vCenter instances are widely observed. The published SSVC assessment from CISA coordination marks exploitation as active, the flaw automatable, and the technical impact total — consistent with a vulnerability where a working exploit can be pointed at one target after another.
No workaround exists. Broadcom's advisory states this plainly for CVE-2026-123890, so reducing exposure with firewall rules or removing management interfaces from reach can lower risk but does not remediate the flaw. The only complete fix is the version-appropriate patch.
Actions and fixes
Apply the fixed vCenter release matched to your branch: 9.1.1.0200 for 9.1.x, 9.0.2.0200 for 9.0.x.x, 8.0 U3m for vCenter Server 8.0, and 5.2.5 for Cloud Foundation 5.x (note Broadcom's Async Patching Guide KB88287 for 5.x environments). Telco Cloud Platform and Telco Cloud Infrastructure customers should follow KB463116. CISA's KEV due date of November 23, 2026 applies to federal agencies, but a three-day window after KEV addition signals how seriously the vulnerability is being treated; treat it as an emergency-change item, not a routine patching cycle.
Because exploitation predates disclosure by months, patching alone is not a complete response. Any vCenter instance that was reachable before the fix should be treated as possibly compromised. The exploitation chain leaves meaningful traces worth checking: unexpected SSO administrator accounts (the report shows one named sps-*@vsphere.local created on a compromised appliance), recently issued administrative SAML assertions, unexpected access to or copies of the vmdir data.mdb database, and new SSH access enabled through the appliance management interface. CISA's KEV entry makes forensic triage explicitly required for federal systems for this reason.
For 7.x deployments with no available fixed version, isolate the management interface from general networks immediately, restrict TCP port 2012 and the other management ports to necessary administrative sources, and engage Broadcom under the extended support contract. In the observed intrusions the actor reached vCenter from an internal Linux appliance, so network segmentation and internal east-west monitoring for management-port scanning (the attackers ran repeated nmap sweeps for ports 9080, 5480 and 2012) are both detection and mitigation levers for every estate, not just 7.x.
Finally, fold the other four CVEs in VMSA-2026-0009.1 into the same change request: SDDC Manager before 9.1.1.0200 or 9.0.2.0100 (the patches are cumulative, so the latest patch level covers the earlier fixes), and VMware Tools 13.1.5.0 or 12.5.5 on Windows guests with Guest Alias mapping enabled.
Uncertainty and what could change
The public record does not say how many organizations were affected. Mandiant describes one observed intrusion chain in detail; the existence of a purpose-built, apparently reusable exploitation utility plus a KEV listing implies broader use, but the full scope of ARMORY CASTLE's campaign and any other actors' adoption is unknown. CISA lists ransomware campaign use as unknown. Treat the absence of ransomware attribution as an open question, not an assurance.
Some forensic details carry their own caveats. Mandiant notes the July 13 Go build timestamp in BONESAW could in principle have been modified before compilation, so the exact moment the actor first possessed the exploit is inferred from logs rather than proven by the binary alone. The disclosure-to-KEV gap was short (one day), and vendor advisories for complex identity-plane flaws occasionally gain revised guidance or additional affected products; the Broadcom advisory was updated once (November 20) and its status remains open, so recheck it as your maintenance proceeds.
The CoeLab Real-World Impact score for this candidate is 94 (Urgent, v1.0), and it is worth being transparent about what that number does and does not mean. It is not CVSS and not EPSS. Its components: full exploitation points because the CVE is in CISA's KEV (30 of 30); full reachability points because the published CVSS vector is AV:N with PR:N and AC:L (25 of 25); consequence points derived from the published 9.8 base score (24 of 25); and 15 of 20 for operational relevance, a heuristic category match treating vCenter as infrastructure-class software. The heuristic category component in particular is a documented product-category judgment, not a measured installed-base estimate, and the score says nothing about any specific environment's exposure. Its limitation cuts both ways: EPSS for this CVE was still only 0.03 on November 21 despite confirmed exploitation, a reminder that probability-style scores lag real intrusions and should never be the sole justification for deferring a patch.
Sources and evidence date
Primary evidence for this analysis: Broadcom security advisory VMSA-2026-0009.1 (initial publication November 19, 2026, updated November 20, 2026), which supplies affected products, fixed versions, the CVSSv3 9.8 vector, and the no-workaround determination; the Google Cloud Threat Intelligence report 'ARMORY CASTLE Exploits vSphere' by Mandiant (published November 19, 2026), which provides the September 2026 exploitation evidence and the BONESAW/SAWSNAKE analysis; and the official CVE record for CVE-2026-123890 (assigned by VMware, reserved November 6, published November 19, updated November 21, 2026), including CISA ADP enrichments recording the KEV addition of November 20, 2026, the exploitation-only-due-November-23 required-action window, and the SSVC assessment of active exploitation with total technical impact. This article was prepared November 22, 2026, before the KEV deadline.
A note on dates to prevent confusion: the vulnerability was reported privately by Mandiant to Broadcom and was exploited in the wild as a zero-day from at least early September 2026; the CVE was published November 19; the advisory was updated November 20; and KEV listing followed the same day with a deadline of November 23. This is an actively exploited vulnerability, and has been for months — not a newly discovered bug, and not a mere reannouncement: the related but distinct CVE-2026-59309, disclosed July 29, 2026, did not cover this flaw and patching it did not prevent the September intrusions.
Primary-source links
https://cloud.google.com/blog/topics/threat-intelligence/armory-castle-exploits-vsphere
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-123890
https://www.cve.org/CVERecord?id=CVE-2026-123890
AI-assisted research and drafting, with a separate model editorial review. CoeLab ratings are editorial judgments, not a substitute for checking your own versions and vendor advisories. Methodology: https://thecoelab.com/blog/security/methodology
Related Posts
Your USB-C Dock Is Part of Your Network. Test It That Way.
A trending Ethernet investigation shows why docks belong in your network diagram. Here is how to isolate bottlenecks before replacing routers or adapters.
CVE-2026-129448: Apache Roller XML-RPC deserialization gets CISA KEV deadline — unauthenticated remote code execution in versions before 6.1.5
Apache Roller before 6.1.5 runs unauthenticated XML-RPC deserialization before authentication; it is now on CISA's exploited list with a patch deadline of November 23, 2026.
Valkey’s Sorted Set Upgrade Is a Capacity Planning Opportunity
Valkey’s sorted set redesign promises lower index overhead. Here is how to test the real memory benefit, protect latency, and turn savings into usable capacity.