Patching today does not make this environment clean. Reporting says CVE-2026-123890 is a vCenter directory-service authentication bypass exploited since September. After two months of exposure, I would classify the vCenter trust plane as potentially compromised until disproven. “Clean” requires continuous log coverage for the exposure window, corroborated by telemetry outside vCenter, plus no unexplained SSO or administrator changes, no suspicious appliance execution or persistence, and no malicious downstream actions against managed ESXi hosts or VMs. If logs are missing, locally controlled, or retention is insufficient, the verdict is only “no compromise observed.” Rebuild the appliance from trusted media rather than pretending a negative IOC scan proves anything.
The highest-value hunt is behavioral, not a filename lottery. Examine vCenter SSO and directory objects for created or modified principals, administrator-group changes, token or session anomalies, and trust-material changes. Then inspect appliance services, scheduled execution, startup mechanisms, shell history, unexpected binaries, outbound connections, and log deletion. Finally, pivot into vCenter-to-ESXi activity: new accounts or keys, SSH enablement, security-setting changes, guest operations, snapshots, exports, and unusual administrative API calls. I do not have validated BONESAW hashes, paths, or process names in the available evidence, so I would not let a BONESAW-only sweep become the clearance test.
This is not the same incident pattern as the others. Cisco Expressway CVE-2026-76466 has a public chain using a shared Erlang identity and cookie over TCP/4372 to invoke commands as root; hunt it as direct appliance RCE and root persistence. ScreenConnect CVE-2026-84869 has reportedly been exploited to run malicious files and deploy SCKit, so delivery, endpoint execution, persistence, and remote-session abuse are the center of gravity. Puppet Server CVE-2026-115731 is reported actively exploited, but the evidence here does not expose enough mechanics to equate its hunt with either chain. vCenter is worse for clearance because the potentially tainted system controls authentication and the virtualization estate—the guard may have been holding the master keys.
The CISO’s next-30-minute order: restrict vCenter management access immediately; preserve appliance, identity, network, and ESXi evidence before further cleanup; revoke sessions and rotate privileged SSO, service-account, host, and applicable signing/trust credentials; begin a September-to-present timeline across vCenter and every managed host; and prepare a trusted rebuild if independent telemetry cannot close the gaps. Patch completed is a maintenance status, not a containment finding.