CVERadar

CVE-2026-123890: Broadcom VMware vCenter flaw exploited in the wild, what we know

CVE REPORT · EXPLOITED IN THE WILDCVE-2026-123890Broadcom VMware vCenterCRITICALCVSS 9.8cveradar.org

CVE-2026-123890 affects Broadcom VMware vCenter; exploited in the wild. What happened, who is affected, how far exploitation has gone and where the patch stands.

CVE-2026-123890 at a glance

CVE-2026-123890 is a critical-severity Auth Bypass vulnerability in Broadcom VMware vCenter, with a CVSS 3.1 base score of 9.8. NVD published it on 2026-11-19 and classifies the weakness as CWE-288. CISA added it to the Known Exploited Vulnerabilities catalog on 2026-11-20; the federal remediation due date is 2026-11-23. Public exploit code: 6 public GitHub proof-of-concept repositories from 6 accounts, with the earliest exploit evidence dated 2026-11-19. FIRST EPSS puts the probability of exploitation activity in the next 30 days at 0.84% (percentile 58.8, scored 2026-11-20). NVD configuration data lists a fixed release for 3 products, for example vmware cloud foundation 5.2.5. CVERadar maps 2 MITRE ATT&CK techniques across Initial Access, Stealth, Persistence and Privilege Escalation, inferred from the CWE and the description. Its CVERadar threat level is 64/100.

Full CVE-2026-123890 record: exploitation evidence, ATT&CK chain and every source.

What it is

VMware vCenter contains an authentication bypass vulnerability in the VMware Directory Service. Affected versions: 9.1.x (fixed in 9.1.1.0200); 9.0.x (fixed in 9.0.2.0200); 8.0 (fixed in 8.0 U3m); 5.x (fixed in 5.2.5). Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x, 5.2 and Telco Cloud Infrastructure 3.0 are also affected (see KB463116).

  • Severity: CRITICAL (CVSS 3.1 9.8, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
  • Weakness: CWE-288.
  • NVD published 2026-11-19, status Analyzed.

Who's affected

Anyone running Broadcom VMware vCenter in the version ranges below. Internet-facing instances are the priority.

  • vmware cloud foundation: from 5.0 up to (not including) 5.2.5.
  • vmware vcenter server: from 9.0 up to (not including) 9.0.2.0200.
  • vmware vcenter server: from 9.1 up to (not including) 9.1.1.0200.
  • vmware telco cloud platform: from 3.0 up to and including 5.2.

Version ranges come from the NVD CPE configuration. Confirm against the vendor advisory before you rely on them.

Exploitation status

  • Exploited in the wild: added to the CISA Known Exploited Vulnerabilities catalog on 2026-11-20; federal remediation due date 2026-11-23.
  • Public proof-of-concept code: 4 GitHub repositories from 4 accounts, the first on 2026-11-19.
Verify before running: public exploit and proof-of-concept code can be fake or carry malware. Only run it in an isolated lab, after reading the code.

What this means for a small business

CISA added CVE-2026-123890 to its Known Exploited Vulnerabilities catalog on 2026-11-20. A KEV listing means CISA has evidence that attackers are using the flaw against real systems, not just that it could be used.

If your business runs Broadcom VMware vCenter, put this at the top of the patch list. CISA gave US federal agencies until 2026-11-23 to deal with it, and that is a sensible deadline for a small business too.

  • Patch. Update to a fixed release: vmware cloud foundation 5.2.5 or later; vmware vcenter server 9.0.2.0200 or later; vmware vcenter server 9.1.1.0200 or later. These versions come from NVD's configuration data, so confirm them against the advisory from Broadcom.
  • If you cannot patch yet. Follow CISA's required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines
  • Check your exposure. Find out whether Broadcom VMware vCenter can be reached from the internet, for example a VPN portal, an admin login page or a file-transfer site. Your firewall's port-forwarding rules and your IT provider's list of public-facing systems are the quickest places to look. Exposed copies come first.
  • When to call IT support. Call your IT support provider now if you run Broadcom VMware vCenter and cannot confirm it is updated, if it was reachable from the internet before you patched it, or if you notice accounts, sign-ins or files you do not recognise. The last two can mean the system was already hit, and checking that properly takes someone who can read the logs.

Risk

  • EPSS (probability of exploitation activity in the next 30 days): 0.84%, higher than 59% of all scored CVEs (as of 2026-11-20).
  • CVERadar threat level: 64/100 (see methodology).
  • Likely ATT&CK techniques: T1190 Exploit Public-Facing Application (inferred); T1078 Valid Accounts (inferred).

Remediation steps

  1. Find every instance. List where Broadcom VMware vCenter runs, including test, DR and forgotten internet-facing systems, and record the installed version.
  2. Upgrade to a fixed release. vmware cloud foundation: 5.2.5 or later; vmware vcenter server: 9.0.2.0200 or later; vmware vcenter server: 9.1.1.0200 or later. Get the build from the vendor advisory.
  3. If you can't patch today, follow CISA's required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines
  4. Verify the fix. Re-run the version check on every instance and confirm it reports the fixed build (5.2.5 or later). Re-scan from outside if the service is exposed.
  5. Hunt for signs of earlier compromise. If the system was exposed before you patched, assume it may have been hit and check the items below.
  6. Rotate credentials stored on or used by the affected system if you cannot rule out compromise, and keep the logs you reviewed.

Detection hints

  • T1190 Exploit Public-Facing Application: Review WAF, reverse-proxy and application logs for unusual requests to VMware vCenter (odd paths, oversized or encoded payloads, bursts of errors), going back to at least 2026-11-19.
  • T1078 Valid Accounts: Check for logins from new sources or accounts you did not create.

Detection commands are generic starting points, not CVE-specific signatures. Use the indicators from the vendor advisory when it publishes them.

Sources

← Back to blog
Keep reading

Related articles

Track every exploited CVE

Full record for CVE-2026-123890, with the ATT&CK chain and every source. Browse what attackers are using right now, and who is affected.

Exploited in the wildHow we score