Critical

VMSA-2026-0009.1 — Patch vCenter to 9.1.1.0200, 9.0.2.0200 (build 25901331) or 8.0 U3m (VCF 5.x: 5.2.5 via KB 88287; Telco Cloud: KB 463116; 7.0 only with extended support).

Details →

Latest News from the Web

Friday edition · archive

The week ends with the one you'll want to act on today. Broadcom has patched CVE-2026-123890, an authentication bypass in vCenter's directory service rated 9.8, and Google's Mandiant team, which reported it, says a China-linked group has been exploiting it since early September to create SSO administrator accounts and steal SAML signing material. The fixes are vCenter 9.1.1.0200, 9.0.2.0200, 8.0 U3m and VCF 5.2.5, there's no workaround, and it can't go on with vCenter Quick Patch, so plan a short management outage.

Security is busy beyond that: Broadcom has also confirmed the Apache HTTP/2 flaw reaches VCF Operations, Aria Operations and HCX, with a workaround but no patch yet. Broadcom's own advisory doesn't state that the vCenter flaw is exploited.

One upgrade trap comes with the fixes: Broadcom's FAQ says vCenter 8.0 U3m and 9.0.2.0200 block upgrades to VCF 9.1.1, so if you're mid-migration you'll be waiting for 9.1.2. Elsewhere, VCF 5.2.5 is out and finally fixes the Brotli flaw on 5.2.x SDDC Managers. As it's Friday there's a week in review, and the deep dive looks at what to check after patching: your SSO administrators and the STS signing certificate.

This is an earlier briefing. Read today's Latest Tech News →

  • Security Two new VMSAs Patch vCenter for CVE-2026-123890 today
  • Releases & KBs vCenter fixes for every line 9.1.1.0200, 8.0 U3m and VCF 5.2.5
  • Terraform & Packer Nothing new vcf 0.19.0 still covers VCF 9.1.1
  • Next deadline 11 days VMUG NL VCF Techcon, 1 Dec

Key Takeaways

  • Urgent Patch every vCenter for CVE-2026-123890 now: 9.1.1.0200, 9.0.2.0200, 8.0 U3m or VCF 5.2.5. VMSA-2026-0009.1 lists no workaround, and per Broadcom's FAQ it's a new flaw, separate from CVE-2026-59309, so a vCenter already patched for VMSA-2026-0006 still needs this update. It isn't eligible for Quick Patch. Mandiant reports exploitation since early September, per SecurityWeek; Broadcom's advisory doesn't state it.
  • Urgent After patching, check for new SSO administrators and refresh the STS signing certificate if anything looks wrong. The attackers created an SSO admin account and took SAML signing material, per The Hacker News. A patch closes the hole but doesn't undo that; today's deep dive covers the STS refresh and what to look for.
  • Before upgrading If you're on vCenter 8.0 or VCF 9.0 and planning a move to 9.1.1, know that the security fix blocks that path for now. Broadcom's FAQ says 8.0 U3m and 9.0.2.0200 are "Back-in-Time" for VCF 9.1.1 and that you should wait briefly for VCF 9.1.2. Patch for the zero-day first; the upgrade can wait. Separately, KB 456235 still means patching VCF Operations and the License Server before ESX on 9.1.1.
  • This month Apply the Apache HTTP/2 workaround on VCF Operations, Aria Operations 8.18 and VCF Operations HCX. VMSA-2026-0010 rates CVE-2026-119618 at 9.8 and every fix is "Patch pending". KB 463005 turns HTTP/2 off in Apache on each VCF or Aria Operations node (there's a script with --check, --apply and --revert), KB 463022 covers HCX, and you'll need to re-check after every upgrade because upgrades turn HTTP/2 back on.
  • This month Keep the Brotli workaround on 9.x SDDC Managers, but 5.2.x can now take VCF 5.2.5. VMSA-2026-0008.2 adds 5.2.5 as the fix for 5.2.x and still lists "Patch pending" for 9.0.x, 9.1.0 and 9.1.1, so KB 460732 or KB 460734 stays in place there.

Week in Review The week's top five

Security Advisories Two new VMSAs

Two new advisories landed on 19 November and VMSA-2026-0008 was revised, so these are the four most recently released or updated; Broadcom's advisory portal has the rest. Patch vCenter for CVE-2026-123890 first. Broadcom's advisory makes no statement on exploitation, but Mandiant and Google's Threat Intelligence Group report that a group they call Armory Castle (formerly UNC5221) has exploited it since early September, per BleepingComputer and SecurityWeek [Press]. VMSA-2026-0010 is Broadcom's answer on the Apache mod_http2 flaw that Singapore's CSA reported as exploited. VMSA-2026-0006 has dropped out of the latest four but isn't finished: CVE-2026-59310 has been in CISA's KEV catalogue since 18 August, and its fixes still apply. On the wider industry front, Broadcom still hasn't said whether VMware products are affected by Java4Shell (CVE-2026-114938) or the NGINX HTTP/2 flaws, and PHP shipped 8.5.13, 8.4.28, 8.3.37 and 8.2.36 on 19 November, per Aikido [Press]; KB 459989 covers only the earlier PHP2Shell flaws.

VMSA-2026-0009.1 Critical Open Rev .1 · 20 Nov 2026

New this week and the one to patch first. CVE-2026-123890 is an authentication bypass in the VMware Directory Service in vCenter: someone with network access can get an administrator session. The same advisory fixes three SDDC Manager flaws (SQL injection, command injection and a local privilege escalation to root) and a SAML token signature bypass in VMware Tools for Windows. CVSSv3 6.7 to 9.8, no workarounds. Broadcom thanks Mandiant for reporting the vCenter flaw; the advisory makes no statement on exploitation, though Mandiant reports it has been exploited since early September [Press]. Issued 19 Nov 2026; revision .1 on 20 Nov clarified the affected VMware Tools versions.

  • CVE-2026-123890 9.8 vCenter directory service auth bypass · exploitation reported by Mandiant
  • CVE-2026-123891 8.1 SDDC Manager SQL injection
  • CVE-2026-123892 7.2 SDDC Manager command injection
  • CVE-2026-123893 6.7 SDDC Manager / VCF Installer privilege escalation
  • CVE-2026-123894 6.7 Tools for Windows SAML signature bypass

DoPatch vCenter to 9.1.1.0200, 9.0.2.0200 or 8.0 U3m (VCF 5.x: 5.2.5 via KB 88287; Telco Cloud: KB 463116; 7.0 only with extended support). SDDC Manager is fixed in 9.1.1.0200 (already out since 12 Oct), 9.0.2.0100 and 5.2.5, and Windows VMs need Tools 13.1.5.0 or 12.5.5.

VMSA-2026-0008.2 Critical Open Rev .2 · 19 Nov 2026

The Node.js Brotli decoder flaw in SDDC Manager: critical (9.8) on 9.1.1.x and important (7.5) on 9.0.x, 9.1.0 and 5.2.x. Revision .2 on 19 Nov added VCF 5.2.5 as the fixed version for 5.2.x; 9.0.x, 9.1.0 and 9.1.1 are still "Patch pending". The VMSA-2026-0009 FAQ says its fixed versions include the VMSA-2026-0008 fixes, but the 0008 matrix doesn't list any 9.x fix, so go by the matrix. Press reports a CISA KEV addition for the underlying Brotli flaw on 27 Oct; the advisory makes no statement on exploitation. First issued 27 Oct 2026.

  • CVE-2026-111497 9.8 9.8 on SDDC Manager 9.1.1, 7.5 elsewhere · reported KEV 27 Oct

DoOn 5.2.x, move to VCF 5.2.5. On 9.1.1 keep KB 460732 in place, and on 9.0.x or 9.1.0 KB 460734, until Broadcom lists a fix.

VMSA-2026-0010 Critical Open Initial · 19 Nov 2026

New this week: the Apache HTTP Server mod_http2 heap corruption flaw reaches VCF Operations 9.x, Aria Operations 8.18.x (standalone and in VCF 5.x) and VCF Operations HCX 9.1.x, with a CVSSv3 of 9.8 for anyone with network access. Every row says "Patch pending", and there's a workaround for each. The advisory makes no statement on exploitation; Singapore's CSA said on 17 Nov the Apache flaw is reportedly being exploited.

  • CVE-2026-119618 9.8 Apache mod_http2 RCE

DoDisable HTTP/2 with KB 463005 on every VCF Operations or Aria Operations node and KB 463022 on HCX, then re-check after each upgrade.

VMSA-2026-0007 Critical Open Initial · 3 Sep 2026

For desktop hypervisors: Workstation and Fusion 25H2 and 26H1, CVSSv3 8.1 to 9.3. Both CVEs need local admin rights inside a guest and can lead to code execution on the host. No workarounds, and no statement on exploitation.

  • CVE-2026-59346 9.3 VMXNET3 integer overflow
  • CVE-2026-59347 8.1 HGFS stack overflow

DoUpdate Workstation and Fusion to 26H1u1, especially if you run nested labs on a laptop.

All VMware security advisories on Broadcom's support portal →

KB Articles & Known Issues Three new KBs

KB 463022, the HCX workaround for VMSA-2026-0010, is linked from the advisory. On the articles we follow, KB 457944 points to vCenter 9.1.1.0100 for the missing Supervisor Control Plane VMs, KB 456235 on host-scoped licences has no fix version, the eMudhra article KB 460199 names no VCF 9 fixes (VCF 5.2.5 removes the eMudhra roots and vCenter 8.0 U3m confirms they're no longer in use, per their release notes), and KB 450972 still targets a future 9.1.x patch for Back-in-Time upgrades from 8.0 U3j and later.

  • KB 463005: Manual interim workaround for CVE-2026-119618 on VCF Operations Broadcom KB 19 Nov Official The workaround behind VMSA-2026-0010 for VCF Operations 9.x and Aria Operations 8.18.x. On each node, check httpd -v (2.4.71 or later is fixed), comment out the http2_module line and the H2WindowSize setting in vcops-photon-apache.conf, set Protocols http/1.1, run httpd -t and restart httpd; an attached script does the same across a cluster. Future releases will ship a fixed Apache, but every upgrade switches HTTP/2 back on, so re-check afterwards.
  • KB 463116: VMware Telco Cloud response to VMSA-2026-0009 Broadcom KB 19 Nov Official For Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x and 5.2 and Telco Cloud Infrastructure 3.0, the fix for CVE-2026-123890 is vCenter 8.0 U3m; other or extended-support versions should contact support.
  • VMSA-2026-0009 questions and answers vmware on GitHub 19 Nov Official Broadcom's FAQ is worth ten minutes. It confirms ESX, NSX, VCF Operations and Automation, Workstation and Fusion aren't affected; none of the issues allows a VM escape; stopping or removing VMware Tools isn't a workaround for the Tools flaw; and vCenter 8.0 U3m and 9.0.2.0200 block upgrades to VCF 9.1.1 until 9.1.2.

Releases & Release Notes Four security releases

Broadcom's advisory names vCenter 9.0.2.0200 as the fix on VCF 9.0, but its release notes aren't on TechDocs yet. On the 9.1.1 line nothing else has moved: ESX, NSX and VCF Operations are still at 9.1.1.0100 and SDDC Manager at 9.1.1.0200, per the 9.1.1.x patch index, and there's still no 9.1.2 release line.

  • VMware vCenter 9.1.1.0200 Broadcom TechDocs 19 Nov Official Build 25901347, the fix for CVE-2026-123890 on VCF and VVF 9.1. It's a full patch ISO (about 8 GB) applied through VCF Operations in a VCF fleet, and the release notes list no known issues.
  • VMware vCenter 8.0 Update 3m Broadcom TechDocs 19 Nov Official Build 25934264, fixing CVE-2026-123890. It also brings a vCenter alarm for Secure Boot VMs with an out-of-date NULL platform key (KB 423893) and a VAMI alert when API sessions approach their limit. Remember it blocks an upgrade to VCF 9.1.1 for now.
  • VMware ESXi 8.0 Update 3m Broadcom TechDocs 19 Nov Official Build 25926933, a bug-fix release; its headline feature is a Capsule PK update for Secure Boot and vTPM Windows VMs, which needs VMware Tools 13.1.5 or 12.5.5 and the July 2026 Windows cumulative update.
  • VMware Cloud Foundation 5.2.5 Broadcom TechDocs 19 Nov Official Build 25935019, with vCenter 8.0 U3m (25934264), ESXi 8.0 U3m (25926933), NSX 4.2.5 (25877985) and Aria Suite Lifecycle 8.18.0 Patch 10. It fixes the three SDDC Manager CVEs in VMSA-2026-0009 and CVE-2026-111497 (Node.js 22.23.4), removes the eMudhra and Sectigo AAA roots from the trust stores, and adds SDDC Manager log forwarding to Aria Operations for Logs.

Automation & IaC

Terraform & Packer Nothing new

A quiet week for the providers. vcf 0.19.0 is still the one to use for VCF 9.1.1, per the README, and the vsphere provider 2.18.0 from 9 November, nsxt 3.12.1, vcfa 1.2.3, avi 32.1.4 and the vsphere 2.5.1 and vmware 2.1.7 Packer plugins are unchanged. If your pipelines run against vCenter, nothing in this week's patches changes the APIs they use, but expect a short outage while vCenter is patched.

Automation & API Ecosystem Nothing new

No new releases for VCF.PowerCLI 9.1.1, govmomi 0.56.2, vmware.vmware 2.13.0 or vmware.vmware_rest 5.1.0. One practical use for them this week: a short PowerCLI or govmomi script that lists every vCenter's version, so you can prove each one is on 9.1.1.0200, 9.0.2.0200 or 8.0 U3m.

Nested Lab Corner One thing to watch

Patch lab vCenters too: a nested lab is still a vCenter on a network. Just be aware that if your lab is rehearsing a move from 8.0 or 9.0 to VCF 9.1.1, Broadcom's FAQ says the 8.0 U3m and 9.0.2.0200 fixes block that upgrade until 9.1.2, so snapshot before you patch if the upgrade test matters more than the fix. Holodeck 9.1.1 lists support for 5.2 to 5.2.4, so 5.2.5 isn't on its list yet.

Deep Dive of the Day

After the vCenter zero-day: patching is step one, then check your SSO domain and STS signing certificate

This week's vCenter flaw is unusual because of what attackers did with it, not just how bad it is. CVE-2026-123890 sits in the VMware Directory Service (vmdir), the LDAP-style store behind vCenter Single Sign-On. According to the reporting on Mandiant's findings, the attackers' tool, BONESAW, used it to get an [email protected] session, copy the directory database, pull out SAML signing material and create a new SSO administrator account, as The Hacker News and this write-up describe. Installing 9.1.1.0200, 9.0.2.0200 or 8.0 U3m closes the hole. It doesn't remove an account someone created or make stolen keys useless, so it's worth understanding the pieces.

Start with the Security Token Service. Broadcom's 9.0 documentation describes it as "a Web service that issues, validates, and renews security tokens". When you log in, STS checks your credentials and builds a SAML token; it signs that token with a private key, and the other vCenter services check the signature against the published public certificates. Those STS signing certificates are stored in vmdir, which is why a flaw in vmdir matters so much.

That's also why a stolen signing key is serious. With it, anyone can mint tokens the services will trust, which is the "Golden SAML" technique the second tool, SAWSNAKE, used to get administrator session cookies, per the write-up. A forged token doesn't need a password and doesn't go through your identity provider's MFA, so it bypasses the controls you'd normally rely on.

The fix for a stolen key is a new key. The 9.1 procedure is short: log in as [email protected] (or another member of the SSO Administrators group), go to Administration, then Certificates, then Certificate Management, select the certificate on the STS Signing tab and choose "Refresh with vCenter Certificate". VMCA issues a new certificate, replaces the old one in vmdir, and STS signs new tokens with it. The page says the new certificate is pushed to linked vCenters too, and that you don't need to restart this vCenter or the others in Enhanced Linked Mode.

There are traps. If you use a custom or third-party STS certificate for compliance, the refresh overwrites it with a VMCA one, and the docs warn that may put you out of compliance; the alternative is "Import and Replace" with a new certificate of your own. If the client offers "Force Refresh" instead, stop and read: the page says it requires restarting every vCenter and "can render those systems inoperable until you do so". KB 318197 adds one sensible step before any of this: take offline (cold) snapshots of all the vCenters in the SSO domain.

Next, look at who's in the SSO domain. Check the members of the Administrators group and any local SSO users you don't recognise, and compare them with what you expect; the attackers' account in Mandiant's case was an SSO administrator. The reported chain also used the VAMI API to create a local appliance administrator and switch SSH on, and added an SSH key to ESXi root, so check VAMI's SSH setting, the local accounts on the appliance and the authorised keys on your hosts.

Be careful with the timeline. Mandiant believes the group knew about this flaw before VMSA-2026-0006 was published in July, and SecurityWeek reports BONESAW was used against a vCenter already patched for CVE-2026-59309, per SecurityWeek. Broadcom's FAQ confirms the two flaws are distinct. So "we patched in August" doesn't mean "we were safe in September"; if a vCenter was reachable from a network an attacker could have been on, the checks above are worth doing whatever your patch history.

For production, sequence it: patch first (it isn't Quick Patch-eligible, so plan for the management outage; running workloads carry on, per Rapid7), then review SSO administrators, VAMI and host SSH settings, then refresh the STS signing certificate if there's any doubt. Forward vCenter and ESX logs to somewhere an attacker can't edit them; both write-ups note the group cleaned up after itself, and Brandefense relays BeyondTrust's point that local logs were deleted on the appliance they came in through.

If you're running VCF, remember that SDDC Manager and VCF Operations hold service accounts and certificates for vCenter as well. Refreshing the STS certificate is a vCenter operation and the docs don't call out a VCF-specific step, so in a production fleet check the VCF certificate and credential views afterwards and try it in a lab first.

In a nested lab, this is a cheap rehearsal: patch a lab vCenter to 9.1.1.0200, add a throwaway SSO administrator so you know where to find it, then refresh the STS certificate and watch what happens to open vSphere Client sessions, PowerCLI connections and anything else that authenticates. It's much better to learn that before you need to do it on a vCenter you're worried about.

Based on Refresh a vCenter STS Certificate Using the vSphere Client (vSphere 9.1) Official Managing the vCenter Security Token Service (vSphere 9.0) Official KB 318197: STS signing certificates about to expire Official VMSA-2026-0009 questions and answers Official ARMORY CASTLE's VMware vCenter attack chain (NetmanageIT) Community

Industry

Features & Technical Blogs One worth reading

William Lam's newest post is still his vCenter Linking write-up from 18 November.

  • Securing 5G with VMware HyperArmor on VCF Telco VCF Blog 19 Nov Official Written for telcos but a useful summary of HyperArmor, the ESX add-on in VCF: virtual patching on the host without a reboot, an allowlist of what can run, and multi-factor authentication in the ESX SSH login. It names stolen root SSH credentials and unpatched flaws as the two main ways into hypervisors, which is exactly how this week's attacks reached ESXi.

Licensing, Business & Industry News Two worth reading

Broadcom reports its fourth-quarter and fiscal 2026 results on Wednesday 9 December, per Broadcom Investor Relations.

  • China-linked hackers exploit critical VMware vCenter zero-day The Hacker News 20 Nov Press The fullest account of the attack chain: initial access through a BeyondTrust Remote Support zero-day, a tool called BONESAW to steal the directory database and create an SSO administrator, forged SAML tokens, SSH enabled through the VAMI API, and an SSH key added to ESXi root. It's the second VMware zero-day the group has used this year, after the ESX logging flaw CVE-2026-41709.
  • Flaws in VMware and KVM need attention The Register 20 Nov Press A round-up of a heavy patch week: VMSA-2026-0009 and VMSA-2026-0010 alongside a KVM flaw (CVE-2026-99312) that only affects AMD hosts with nested virtualisation, which you can sidestep by turning nested virtualisation off.

Community & Learning

Videos, Podcasts & Events New this week

VMUG Netherlands holds its VCF Techcon on 1 December, VMware Explore on Tour reaches Washington, D.C. on 8 December and Sydney on 3–4 March 2027, and VMware Explore 2027 is at Resorts World Las Vegas on 10–13 May 2027, with registration opening on 12 January.

Certification & Learning Nothing new

No exam changes this week. The role-based VCF 9 VCAP exams, Administrator (3V0-11.26), Architect (3V0-12.26) and Support (3V0-13.26), are unchanged, and Hands-on Labs are still moving from the HOL-26xx labs to HOL-27xx with VCF 9.1 content.

Sources (30)

Recent Briefings

Full archive → RSS

Tags: Official Broadcom and VMware sources, Press trade press, Community community posts and unverified reports.

Thanks for visiting

Let's talk tech!

Questions, ideas, or just want to talk VCF? Drop me an email or find me on the socials.

Email me →