CISA Adds VMware vCenter Authentication Bypass to KEV

P1 — VALIDATE AND UPDATECritical · 9.8 (CVSS v3; Broadcom VMSA-2026-0009.1)EXPLOITATION: KNOWN EXPLOITATION

Quick Answer

Prioritize affected vCenter management systems, apply the branch-specific Broadcom fix, and preserve evidence for forensic triage. CISA lists November 23 for this KEV entry.

Confirm Scope And Apply The Supported Remediation

What to do now: Inventory vCenter builds, Cloud Foundation and Telco dependencies, linked management domains, administrative exposure and supported backup/recovery procedures. Use the vCenter row in VMSA-2026-0009.1 rather than borrowing fixes for SDDC Manager or VMware Tools. Confirm the supported route for the enclosing product. Apply the matching vCenter or integrated-product remedy. Broadcom lists no workaround; use vendor support for vCenter 7.0 extended support and the specified Telco guidance. Verify the running build, authentication, inventory access, host connectivity and backup integrations. Preserve management, identity and host logs before incident-response changes.

Open the authoritative advisory

Last verified: 2026-11-21 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeVMware vCenter and products incorporating it
AdvisoryCISA-KEV-CVE-2026-123890
CVECVE-2026-123890
CISA KEV addition date2026-11-20 — CISA KEV addition; catalog released 2026-11-20T17:48:39.1516Z.
Authority revision date2026-11-20 — Broadcom VMSA-2026-0009.1 update; CISA addition is recorded separately.
Affected versionsThe vCenter components listed in Broadcom VMSA-2026-0009.1: 9.1, 9.0, 8.0 and 7.0 branches, VMware Cloud Foundation 5.x, and the listed Telco Cloud products before their corresponding response-matrix remedies.
Fixed versionvCenter 9.1.1.0200, 9.0.2.0200 or 8.0 U3m for the respective branches; VCF 5.x: 5.2.5. vCenter 7.0 extended-support customers must contact Broadcom; listed Telco products follow KB463116.
CVSS base score9.8 (CVSS v3; Broadcom VMSA-2026-0009.1)
CVSS severityCritical
Exploitation statusCISA confirms exploitation in the wild by adding this vulnerability to KEV. Known ransomware campaign use is listed as Unknown.; no exploitation claim is inferred.

What Changed

CISA now confirms exploitation of the VMware Directory Service authentication bypass and requires forensic triage. An unauthenticated actor with network access can bypass authentication and gain unauthorized access. This notice addresses that CVE; Broadcom’s wider bulletin also covers separate SDDC Manager and VMware Tools issues.

What To Validate Now

  1. Inventory. Inventory vCenter builds, Cloud Foundation and Telco dependencies, linked management domains, administrative exposure and supported backup/recovery procedures.
  2. Establish applicability. Use the vCenter row in VMSA-2026-0009.1 rather than borrowing fixes for SDDC Manager or VMware Tools. Confirm the supported route for the enclosing product.
  3. Remediate. Apply the matching vCenter or integrated-product remedy. Broadcom lists no workaround; use vendor support for vCenter 7.0 extended support and the specified Telco guidance.
  4. Validate. Verify the running build, authentication, inventory access, host connectivity and backup integrations. Preserve management, identity and host logs before incident-response changes.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Avoid mixing standalone vCenter and integrated-product update paths. The KEV addition is evidence of exploitation in the wild, not proof that a particular installation was compromised; follow applicable CISA requirements.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.