VMware vCenter CVE-2026-123890
A critical VMware vCenter flaw, CVE-2026-123890 (CVSSv3 9.8), lets attackers open a vCenter administrator session without a password. Mandiant says it was exploited in early September 2026, and Broadcom lists no workaround.
Where Worldwide
On this page 9 sections
A critical flaw in VMware vCenter Server, tracked as CVE-2026-123890, lets an attacker with no password open a session as administrator@vsphere.local, the main vCenter administrator account. Mandiant says a group it calls ARMORY CASTLE, which it describes as a suspected PRC-nexus threat actor, exploited the flaw in early September 2026. Broadcom lists no workaround, so any business running vCenter should patch it before any other server work this week.
vCenter Server is the management console for a VMware virtual machine environment. An administrator session there gives an attacker more than one server: it puts them at the controls for the virtual machines vCenter manages. Below is what Broadcom and Mandiant actually say, what is still unknown, and a checklist for the next few days.
What happened with VMware vCenter CVE-2026-123890
Broadcom publishes VMware's security advisories, and its advisory lists the issue as "vCenter authentication-bypass vulnerability (CVE-2026-123890)". In its words: "VMware vCenter contains an authentication bypass vulnerability in the VMware Directory Service." Broadcom rates it Critical, with a maximum CVSSv3 base score of 9.8.
Mandiant, writing on Google Cloud's threat intelligence blog, describes the flaw as "an unauthenticated Secure Remote Password (SRP-6a) session key disclosure vulnerability over Distributed Computing Environment/Remote Procedure Calls (DCE/RPC)". Put simply, part of the login process gives away a session secret to someone who never signed in. Mandiant says successful exploitation results in a remote authentication bypass that creates a session as administrator@vsphere.local.
Who exploited the vCenter flaw, and when
According to Mandiant, forensic evidence shows ARMORY CASTLE exploited this vulnerability in early September 2026 using a tool called BONESAW. Mandiant also says it has evidence the group knew about CVE-2026-123890 before July 29, 2026. That is the date a separate vCenter flaw, CVE-2026-59309, was disclosed.
Mandiant sums up the campaign this way: "ARMORY CASTLE exploited two zero-days, and deployed three sets of malware specifically tailored for operating on targeted devices, indicating deep platform expertise and substantial resource backing."
The practical point: this bug was not just found in a lab. A skilled, well-funded group used it against real systems. If an attacker could reach your vCenter in September, patching now closes the hole. It does not tell you whether someone already got in through it.
What is confirmed and what is claimed
| Point | Status | Who says so |
|---|---|---|
| CVE-2026-123890 is an authentication bypass in the VMware Directory Service in vCenter | Confirmed by the vendor | Broadcom |
| Severity is Critical, CVSSv3 base score up to 9.8 | Confirmed by the vendor | Broadcom |
| There is no workaround | Confirmed by the vendor | Broadcom |
| Exploitation creates a session as administrator@vsphere.local | Researchers' technical finding | Mandiant |
| ARMORY CASTLE exploited it in early September 2026 with BONESAW | Researchers' finding, based on forensic evidence | Mandiant |
| The group is PRC-nexus | Researchers' assessment, stated as suspected | Mandiant |
| The group knew of the flaw before July 29, 2026 | Researchers say they have evidence | Mandiant |
What is not known yet
- Who was hit. The sources we checked do not say how many organizations were targeted, or in which industries or countries.
- Version numbers. This post does not list affected or fixed vCenter builds. Look up your exact build in Broadcom's advisory, not in a summary.
- Changes to the advisory. Broadcom's change log notes: "Updated advisory to clarify the impacted VMware Tools versions." The advisory has changed since it first appeared, and the change is about VMware Tools. Read the current version even if you saw an earlier one.
- The second zero-day. Mandiant says the group used two zero-days. The material we checked does not say whether CVE-2026-59309 is the other one.
- Signs of compromise. We have not copied Mandiant's technical warning signs for BONESAW here. Your security team or provider should read Mandiant's report directly.
Is there a VMware vCenter patch or workaround?
There is no workaround. Broadcom's advisory states plainly: "Workarounds: None". There is no setting you can change to stay safe while you wait for a maintenance window.
Mandiant's advice is direct: "We strongly recommend that affected organizations immediately apply the security patches provided by Broadcom to remediate the vulnerability."
The advisory also says: "Contact Broadcom Support if you have extended support contract." If your vCenter release is covered by extended support, open a case with Broadcom Support now.
One more warning: a console that says it is up to date does not prove this particular fix is installed.
What to do this week
| Step | How to do it |
|---|---|
| 1. List every vCenter Server you run | Include production, disaster recovery, test labs and any instance a hosting provider or IT contractor runs for you |
| 2. Read Broadcom's current advisory | Check your exact vCenter build against it, and read it again if you saw an earlier copy |
| 3. Apply Broadcom's security patch | There is no workaround, so the patch is the only fix |
| 4. On extended support? Contact Broadcom | The advisory says to contact Broadcom Support if you have an extended support contract |
| 5. Check VMware Tools | Broadcom updated the advisory to clarify which VMware Tools versions are affected, so compare yours |
| 6. Review administrator@vsphere.local activity | Look at sign-ins and changes made by this account going back to at least early September 2026 |
| 7. Limit who can reach vCenter | Keeping management consoles off the internet and off general staff networks is good practice. It is not a Broadcom workaround and does not replace the patch |
| 8. Escalate anything odd | If you find activity you cannot explain, treat it as a security incident. A patch does not remove an attacker who is already inside |
Why it matters for a company network
In many businesses, the file server, the accounting database, the main business software and sometimes the domain controller all run as virtual machines under one vCenter. That gives one system control over all of them. An attacker with an administrator session there does not need to break into each server one by one.
vCenter is also often the system nobody clearly owns. It was set up years ago, it works, and patching it means planning downtime. If you are not sure who patches yours, or whether a provider does it for you, settle that this week.
VMware vCenter vulnerability questions people are asking
Is CVE-2026-123890 being exploited?
Yes, according to Mandiant. It says forensic evidence shows ARMORY CASTLE exploited the flaw in early September 2026 using BONESAW.
What is the CVSS score for CVE-2026-123890?
Broadcom rates it Critical, with a maximum CVSSv3 base score of 9.8.
Is there a workaround for the vCenter authentication bypass?
No. Broadcom's advisory lists "Workarounds: None". Broadcom's patch is the fix.
What can an attacker do with this vCenter flaw?
Mandiant says successful exploitation creates an authenticated session as administrator@vsphere.local without a password.
Who is ARMORY CASTLE?
It is the name Mandiant gives a group it calls a suspected PRC-nexus threat actor. Mandiant says the group used two zero-days and three sets of custom malware in this campaign.
Which vCenter versions are affected?
Check Broadcom's advisory for your exact build. We have not listed version numbers here because the advisory is the official source, and Broadcom has already updated it once.
What if my vCenter release is on extended support?
Broadcom's advisory says to contact Broadcom Support if you have an extended support contract.
Is this the same as the vCenter flaw from July?
No. CVE-2026-59309 is a separate vCenter vulnerability, disclosed on July 29, 2026. Mandiant says ARMORY CASTLE knew about CVE-2026-123890 before that date.
The bigger lesson
The systems that manage other systems give attackers the most for their effort. A management console that is critical, reachable and patched only when someone gets around to it is an open invitation. The fix this week is a patch. The protection that lasts is knowing where every console is, who can reach it and who is responsible for updating it, and checking its history when a flaw like this appears.
For help locking down the servers your business depends on, see security hardening or request a quote.
Get security alerts like this by email, with the free checklist, at our security alerts page.
Sources: Broadcom security advisory for CVE-2026-123890; Mandiant on Google Cloud: ARMORY CASTLE exploits vSphere.
Have a question about this article?
Ask it here and we will answer you directly by email. Questions are private, never posted.
Security alerts by email
Hear about the next one first.
When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.
Want a result like this?
Security alerts, breaches and the technology a business runs on: what happened, who it affects and what to do.
Get a Tech QuoteKeep reading
CISA KEV: Apache Axis, REDCap, Synology DSM and LiteLLM Flaws Exploited, No Patch Coming for Axis 1.x, and the Fixed Versions to Install
CISA has added exploited flaws in Apache Axis, REDCap, Synology DSM and LiteLLM to its KEV catalog. Apache wil...
Database RCE: PostgreSQL CVE-2026-116331, ClickHouse, MySQL and Oracle Flaws Show Locked-Down Database Accounts Can Still Reach the Server, and the Fixed Versions
Depthfirst researcher Zheng Yu showed that tight database permissions still leave room for attacks that run co...
Java4Shell Vulnerability CVE-2026-114938: Critical OpenJDK Base64 Flaw, Attack-Shaped Traffic Recorded, and What to Patch This Week
Java4Shell (CVE-2026-114938) is a critical memory-corruption flaw in OpenJDK's Base64 decoder. It affects unpa...