Auditing Internet-Exposed vCenter for CVE-2026-123890: Patch Priority and Log Evidence
CVE-2026-123890 is reported as an authentication-bypass flaw in VMware vCenter, exploited for roughly two months before Broadcom shipped fixes around 19–20 November 2026. Reported post-exploitation activity includes hijacking administrator accounts and pulling VM data out. This short walks the defensive order from the write-up: don't start with patch timing, start with whether an admin session was minted on your control plane. What's covered: - Why a vCenter admin session is a bearer credential over the whole virtualization inventory, not an app login - Enumerating and terminating sessions with SessionManager so a patch doesn't leave a live intruder behind - Response order: isolate, patch, rotate credentials and sessions, then hunt assuming admin access - Log evidence to look for in vpxd and SSO logs — new identity sources, plugin extensions, fresh administrators - Persistence created through legitimate features (identity sources, Global Permissions, custom roles, extension plugins, solution user certificates) that survives patching - Why recovery here means rebuilding trust in the estate rather than restoring an app Scope and honesty: the post separates what public reporting confirms from what is inferred from the authentication-bypass bug class. Affected build ranges, the CVSS vector and the exact vulnerable component were not confirmed at the time of writing — read the vendor advisory for those. Everything here is defensive and lab-scoped; placeholders are used for hosts, accounts and log lines. Full write-up with the audit checklist, scoring model and log queries: https://hackyjs.com/posts/auditing-internet-exposed-vcenter-for-cve-2026-123890-patch-priority-and-log-evidence