Zero-day in VMware vCenter: patch now or assume the risk
A China-linked group exploited a critical flaw in vCenter before a patch existed. We explain what it means for your SMB and how to act.
4 min read

In this article
Some news deserves a second read. The one we're covering this week directly affects anyone with virtualization in their infrastructure: a cyberespionage group suspected of being linked to China, known as Armory Castle (formerly UNC5221), has been identified as responsible for exploiting a critical zero-day in VMware vCenter Server in early September 2026. The flaw, registered as CVE-2026-123890 with a CVSS score of 9.8, is a case of authentication bypass in VMware's directory service that allows unauthorized access to be obtained.
Translated into SMB language: someone could enter your virtualization control panel without valid credentials and, from there, move through the rest of the infrastructure. And they did so, moreover, before a public patch existed. That is what turns a high CVE into a real problem rather than a colorful footnote.
What vCenter is and why it matters so much
vCenter is not just any server. It is the control plane of vSphere: hosts, virtual machines, permissions, templates and policies are managed from there. If an attacker manages to bypass authentication in that service, they don't need to compromise each server one by one; sitting in the engine room is enough. And in an SMB with few IT resources, that leap can mean access to file servers, ERP, email or backups.
The news mentions administrative access and data theft. This is not a theoretical laboratory scenario: it is an espionage group with motivation and resources. For an industrial SMB, a professional firm or a services company, the information that moves through those systems is usually not trivial.
A recurring pattern: patching is not enough
The first thing usually demanded in the face of a 9.8 CVE is applying the patch. And it is right to demand it, but it comes too late if the attacker was already inside. The correct sequence is different: first check whether there was exposure, then patch and, in parallel, review what could have been touched. An authentication bypass does not necessarily leave a noisy trail; it can look like just another legitimate access.
That is why it is worth looking at vCenter logs, after-hours administrator sessions, creation of new accounts, changes in roles or template exports. If your team does not have that visibility, that is the first hole to plug, beyond the patch.
What we recommend from ForgeNEX
- Identify your exposure. Locate all vCenter instances, including lab or test ones that are sometimes forgotten and exposed to the Internet.
- Apply the update that VMware has published for CVE-2026-123890 as soon as it is available for your version. If you cannot update immediately, limit access to the service with network rules and segmentation.
- Review signs of compromise in the period since early September 2026: anomalous administrative access, new accounts, permission changes and unexpected outbound connections.
- Rotate credentials for vCenter administration and for the systems that depend on it, especially if you suspect there may have been access.
- Strengthen authentication with two-factor authentication for administrative access and avoid publishing the vCenter panel directly on the Internet.
- Check backups and their restoration. Not out of alarmism, but because it is the only clean way out if the control plane is affected.
This case fits with an idea we often repeat: virtualization is critical infrastructure even though in many SMBs it is treated as “the machine server.” If you want to organize the risk map of your environment, you can review our analysis on vSphere Express and what it means for SMBs, or go over how a poorly managed trust incident can end up as a technical problem in the Schwalbe case.
The lesson for the IT team
Zero-days exploited by espionage groups are not fought only with a patch bulletin. They are fought with up-to-date inventory, segmentation, least privilege and the ability to detect anomalies. For an SMB, that does not require a 24-hour SOC; it requires sensible decisions: not exposing administration panels, applying updates judiciously and having a clear plan for what to do if one day privileged access stops being trustworthy.
A 9.8 CVE is not just a number: it is an invitation to review who can touch the heart of your infrastructure.
If in your company vCenter supports more than it seems, it is worth dedicating an afternoon to it this week. And if you don't know where to start, better to start with the inventory than with the patch.
Source: The Hacker News. Analysis and adaptation: ForgeNEX.
Keep reading
- Alpine and musl flaw: passwordless SSH login under certain configurations19 November 2026
- WordPress 7.1.5 fixes 20 flaws: unauthenticated RCE and critical SQL19 November 2026
- SHA pinning is no longer enough: the warning every SME should read18 November 2026
- Cyberattack on the cold chain: the real risk for SMEs and supermarkets17 November 2026
- N-able fixes 17 critical flaws in N-central and warns of crypto miners17 November 2026