endoflife.ai
EOL Checker Products EOL Watch Get Support

vCenter 7.0 and CVE-2026-123890: On CISA's Exploited List, Fixed Only by Extended Support Contract

By Scott Bissett  ·  Published: November 21, 2026  ·  Verified against CISA's KEV catalog feed, Broadcom advisory VMSA-2026-0009.1 and its FAQ, and Google Threat Intelligence Group's report — methodology

VMware vCenter 7.0 is affected by CVE-2026-123890, a CVSS 9.8 authentication bypass that CISA added to its Known Exploited Vulnerabilities catalog on November 20, 2026, and it is fixed only for customers with an extended support contract. Broadcom's advisory VMSA-2026-0009 lists public fixed builds for vCenter 9.1, 9.0 and 8.0. For vCenter 7.0, which reached End of General Support on October 2, 2025, the Fixed Version cell of its response matrix reads: “Contact Broadcom Support if you have extended support contract.” The advisory lists no workaround. CISA set a federal due date of November 23, 2026.

The statements that the flaw is being exploited come from CISA and from Google, not from Broadcom. Google Threat Intelligence Group's report of November 19, 2026 says a suspected China-nexus group it tracks as ARMORY CASTLE exploited CVE-2026-123890 in early September 2026, and that the group's tool achieves full compromise of vCenter Server 7.x and 8.x appliances. Broadcom's advisory and its FAQ do not mention exploitation. This page sets out what each source says, who can get the 7.0 fix, and what an owner of 7.0 without a contract can do.

The one-paragraph version: if you run vCenter 8.0 or 9.x, install the fixed version Broadcom's advisory lists for your line (table below) or a later one. If you run vCenter 7.0 with an extended support contract, contact Broadcom Support and request the 7.0 patch. If you run vCenter 7.0 without one, the advisory and its FAQ give you no public build and no workaround: the routes are an extended support contract or an upgrade to a line with a public fix, and until one is done the instance is exposed to a flaw that CISA and Google say is being exploited.
Quick answer: VMware vCenter 7.0 reached end of life (EOL) on October 2, 2025. Every VMware vCenter version's release and end-of-support date is on the VMware vCenter lifecycle page. Running a VMware vCenter version that is past end of life? See the support options on this page ↓

Key Dates at a Glance

Running vCenter past end of life?
Extended support past the official EOL date exists for many products in this position — whether it covers vCenter is exactly what we check. Tell us where to reach you and we’ll reply with matched options and pricing guidance — or an honest “no vendor covers this.” Free, no obligation.

Free · No obligation · Independent — we track the dates, vendors don’t pay for placement · dates verified against vendor sources. See all support options →

What Broadcom's Advisory Says, Row by Row

VMSA-2026-0009 was published on November 19, 2026 and revised on November 20, 2026 (VMSA-2026-0009.1; its change log says the revision clarified the impacted VMware Tools versions). It covers five CVEs in vCenter, SDDC Manager and VMware Tools for Windows. CVE-2026-123890 is the vCenter one: an authentication bypass in the VMware Directory Service that Broadcom rates Critical, with a CVSS base score of 9.8, and describes as usable by an attacker with network access to vCenter. The table below copies the vCenter response matrix as printed in VMSA-2026-0009.1. The version and build numbers are Broadcom's, quoted from that revision; a later revision of the advisory replaces them.

VMware product (as printed)ComponentVersionFixed version (as printed)Workarounds
VMware Cloud Foundation, VMware vSphere FoundationvCenter9.1.x.x9.1.1.0200None
VMware Cloud Foundation, VMware vSphere FoundationvCenter9.0.x.x9.0.2.0200None
VMware vCenterN/A8.08.0 U3mNone
VMware vCenterN/A7.0“Contact Broadcom Support if you have extended support contract.”None
VMware Cloud FoundationvCenter5.x5.2.5 (the row points to Broadcom's async patching guide, KB88287)None
VMware Telco Cloud PlatformvCenter3.0, 4.x, 5.0.x, 5.1.x, 5.2KB463116None
VMware Telco Cloud InfrastructurevCenter3.0KB463116None

Every row is listed for CVE-2026-123890 at CVSS 9.8, severity Critical, running on any platform; those columns are left out above.

Read the 7.0 row for what it says and for what it does not say. It does not say that 7.0 has no fix. It says the fix is reached through Broadcom Support by customers who hold an extended support contract. Broadcom's FAQ for the advisory answers the question directly: vSphere 7.0 is impacted, vSphere 7 reached End of General Support on October 2, 2025, and an organization with an active extended support contract should use those support processes to request patches. The same FAQ says the patches are cumulative, so versions newer than the ones listed also resolve the issue.

vCenter 6.5 and 6.7. The matrix has no row for them. The FAQ's answer for vSphere 6.5 and 6.7 is to presume they are affected, because Broadcom does not evaluate products past their End of General Support dates as part of security advisories. Both lines reached End of General Support on October 15, 2022. The advisory and the FAQ name no patch route for them and encourage an upgrade.

Who Says It Is Being Exploited

Two sources, and neither of them is Broadcom.

Broadcom's advisory describes the attack vector, credits Mandiant with reporting the issue and lists the fixes. Neither the advisory nor the FAQ says the flaw has been used in attacks.

Who Can Get the 7.0 Fix

  1. vCenter 7.0 with an extended support contract. The advisory sends you to Broadcom Support, and the FAQ says to use those support processes to request the patch. The 7.0 fix is requested from Broadcom; the advisory lists no 7.0 build to download.
  2. vCenter 7.0 without an extended support contract. The advisory lists no fixed version for you and no workaround, and neither the advisory nor the FAQ names another route for 7.0. The choices are to obtain an extended support contract from Broadcom or to upgrade to a line with a public fix. The FAQ encourages customers on older versions to upgrade to VMware Cloud Foundation 9.1.
  3. vCenter 6.5 or 6.7. Not evaluated by Broadcom for this advisory. Its FAQ says to presume these versions are affected and names no patch route for them.

If you are not sure whether your agreement with Broadcom counts as an extended support contract, that is the first question to put to Broadcom. The advisory and the FAQ do not state what such a contract costs or who qualifies, and we do not know.

The Same Line as CVE-2026-59310

The 7.0 wording is not new. Broadcom's advisory VMSA-2026-0006 carries the same line for vCenter 7.0 and CVE-2026-59310, a different vCenter flaw, which CISA listed on August 18, 2026. Our article on that case is vCenter 7.0 and CVE-2026-59310.

The two are separate. Broadcom's FAQ says CVE-2026-123890 is a new and distinct issue from CVE-2026-59309, the Directory Service flaw in that earlier advisory, and that all systems below the fixed versions need this update. Google's report says the server it examined had already been patched against CVE-2026-59309 when it was compromised. A vCenter 7.0 instance that received the earlier fix through a contract needs this one as well.

For an owner of vCenter 7.0 the pattern matters more than either flaw. Since general support ended on October 2, 2025, the route to the fix for a vCenter flaw on CISA's exploited list has twice been a contract, not a download.

Where Each vCenter Line Stands

The dates are the End of General Support dates on our vCenter product page. The fix column summarises the advisory table above.

VersionEnd of General SupportCVE-2026-123890 in VMSA-2026-0009.1EOL Risk Score
vCenter 9.1August 12, 2028Public fixed build listed30
vCenter 9.0November 12, 2027Public fixed build listed30
vCenter 8.0October 11, 2027Public fixed build listed30
vCenter 7.0October 2, 2025Fix through Broadcom Support, for customers with an extended support contract65

The EOL Risk Score (0–100) combines how far past, or how close to, end of life a version is, the attack surface of the software class, whether CISA lists the product in its KEV catalog, and whether extended support exists. The numbers above are recomputed at every build.

What to Do Now

  1. vCenter 8.0 and 9.x: install the fixed version the advisory lists for your line, or a later one. CISA set a federal due date of November 23, 2026 for agencies, which is a reasonable measure of the urgency for everyone else.
  2. vCenter 7.0 with an extended support contract: contact Broadcom Support and request the 7.0 patch.
  3. vCenter 7.0 without one: choose between the two routes, an extended support contract or an upgrade, and until one is done limit which hosts can reach vCenter over the network. Broadcom lists no workaround and says other mitigations are for each organization to judge. Google's report describes dropping connections to TCP port 2012 from hosts that are not on an allowlist as one of its hardening measures. Restricting access reduces exposure; it does not fix the flaw.
  4. vCenter 6.5 and 6.7: presume the instance is affected, as Broadcom's FAQ says, and plan the upgrade.
  5. Everyone: look for signs of earlier compromise as well as patching. Google says the flaw was exploited in early September 2026, before Broadcom's advisory existed, so a server patched now can have been entered earlier. Google's report lists the indicators.
  6. ESXi hosts: Broadcom's FAQ says ESX is not affected by this advisory. Lifecycle dates for the hypervisor are on our ESXi page.

Frequently Asked Questions

Is vCenter 7.0 patched for CVE-2026-123890?

Only for customers with an extended support contract. Broadcom's advisory VMSA-2026-0009 lists public fixed builds for vCenter 9.1, 9.0 and 8.0. For vCenter 7.0, the Fixed Version cell of its response matrix reads: 'Contact Broadcom Support if you have extended support contract.' The advisory lists no workaround. vCenter 7.0 reached End of General Support on October 2, 2025.

Is CVE-2026-123890 being exploited?

CISA and Google say it is; Broadcom's advisory and FAQ do not mention exploitation. CISA added CVE-2026-123890 to its Known Exploited Vulnerabilities catalog on November 20, 2026. Google Threat Intelligence Group's report of November 19, 2026 says a suspected China-nexus group it tracks as ARMORY CASTLE exploited the flaw in early September 2026, with a tool that achieves full compromise of vCenter Server 7.x and 8.x appliances.

What did CISA require by November 23, 2026 for CVE-2026-123890?

CISA's catalog entry set a federal due date of November 23, 2026 for federal civilian agencies. The required action is to apply mitigations according to vendor instructions under CISA's directive BOD 26-04, or to discontinue use of the product if mitigations are unavailable. For vCenter 7.0 the vendor instruction is to contact Broadcom Support under an extended support contract; the advisory lists no public 7.0 build and no workaround.

Which vCenter versions are in general support?

vCenter 9.1 is supported until August 12, 2028. vCenter 9.0 is supported until November 12, 2027. vCenter 8.0 is supported until October 11, 2027. vCenter 7.0 reached End of General Support on October 2, 2025. Broadcom's advisory lists vCenter 9.0 and 9.1 as components of VMware Cloud Foundation and VMware vSphere Foundation. Every line is on our vCenter product page.

Has this happened to vCenter 7.0 before?

Yes. Broadcom's advisory VMSA-2026-0006 carries the same line for vCenter 7.0 and CVE-2026-59310, a different vCenter flaw, which CISA listed on August 18, 2026. Broadcom's FAQ says CVE-2026-123890 is a new and distinct issue and that all systems below the fixed versions need this update.

What should I do if I run vCenter 7.0?

With an extended support contract, contact Broadcom Support and request the 7.0 patch. Without one, the routes are an extended support contract or an upgrade to a line with a public fixed build; Broadcom's FAQ encourages an upgrade to VMware Cloud Foundation 9.1. Until one of those is done, limit network access to vCenter and check for signs of earlier compromise: Google says the flaw was exploited in early September 2026, and its report publishes indicators of compromise. Broadcom lists no workaround.

The Monthly EOL Digest™

Once a month — critical EOL dates, CVE blind spots, and lifecycle changes worth knowing.

© 2026 endoflife.ai · How we verify our dates · API · About · Data from endoflife.date (MIT)