Defending vCenter port 2012 while CVE-2026-123890 patches roll out
Defending vCenter port 2012 while CVE-2026-123890 patches roll out Patch windows take time even when an emergency change is approved. During that interval, the most useful control for CVE-2026-123890 is a narrow, monit
Defending vCenter port 2012 while CVE-2026-123890 patches roll out
Patch windows take time even when an emergency change is approved. During that interval, the most useful control for CVE-2026-123890 is a narrow, monitored path to the vulnerable vCenter directory service. The goal is to stop unauthorized DCE/RPC traffic without breaking legitimate vCenter administration or hiding the evidence responders need.
Vulnerability overview
Broadcom published VMSA-2026-0009 for CVE-2026-123890 on November 19, 2026. The VMware Directory Service authentication bypass has a CVSS v3.1 score of 9.8 and a CWE-288 classification. Network access to vCenter is the vendor's stated precondition. Mandiant reports that ARMORY CASTLE exploited the issue in early September using BONESAW, before the public patch.
Mechanism and exploitation conditions
Mandiant describes an unauthenticated Secure Remote Password session-key disclosure over vmdir DCE/RPC. The relevant service is rpc_srp_verifier on TCP 2012, and predictable UUIDv1 timestamp generation exposes the shared session key. The attacker creates an administrator session as [email protected]. Exploitation does not require a password, user interaction, or a phishing step.
Network controls should therefore be precise. Permit TCP 2012 only from the systems that must manage vCenter. Remove broad rules that allow every server VLAN, VPN pool, or user subnet to reach the management plane. Inspect proxies and load balancers for a path that bypasses the intended boundary. Log denied traffic and alert on scans that include VMware management ports 443, 2012, 5480, and 9080.
Impact
The defender who blocks the wrong path can still lose the environment through an unmonitored route. A successful bypass gives administrative access to vCenter and the ability to retrieve vmdir data. BONESAW can extract the SAML Security Token Service key, create an SSO administrator, and assign Global Administrator permissions. These changes can survive the patch unless the affected identity material is rotated and validated.
The response should preserve evidence before the maintenance window ends. Record current SSO administrators, machine accounts, SAML signer certificates, root-folder permissions, and allowed management sources. After the patch, compare those records with the post-change state. If the environment was reached through a proxy or jump host, inspect that system for the source of the DCE/RPC traffic and for staging files or command history.
Affected products and scope
Broadcom lists VMware Cloud Foundation and vSphere Foundation vCenter 9.1.x fixed in 9.1.1.0200, 9.0.x fixed in 9.0.2.0200, vCenter 8.0 fixed in 8.0 U3m, and VMware Cloud Foundation 5.x fixed in 5.2.5. vCenter 7.0 extended-support customers need Broadcom support guidance. VMware Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x, and 5.2 plus Telco Cloud Infrastructure 3.0 follow KB463116. ESX is not affected by this advisory.
Exposure context
ZoomEye reported 27,325 results for app="VMware vCenter" and 0 for vul.cve="CVE-2026-123890" in this review. The product count indicates the scale of visible vCenter fingerprints, not the number of vulnerable deployments or open port 2012 services. A zero CVE-index result does not establish that patching is complete. Internal network telemetry and build checks remain the decision points.
Remediation and mitigations
Install the vendor fix as the primary action. Until then, restrict TCP 2012 to documented management hosts, alert on new sources, and review all network paths into the vCenter management segment. After patching, validate the running version and remove temporary rules only when the intended access model is restored. If exploitation is suspected, rotate the STS signing certificate and SSO credentials and confirm that old forged assertions fail. Also verify that backups, recovery appliances, and alternate management sites use the fixed build and do not retain the same exposed trust material.
References
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.