Skip to content

All of the watch

VMware vCenter Vulnerability: Authentication Bypass Scored 9.8 Out of 10, Exploitation Reported

Cybersecurity · World

  • Critical vulnerability
  • CVE-2026-123890
  • VMware vCenter
  • virtualization

The VMware vCenter vulnerability disclosed on November 19, 2026 affects the tool that runs the virtual servers of many businesses, scoring 9.8 out of 10 according to the NVD listing. If your organization uses this product, applying the vendor’s patch should move to the top of your priority list.

What is it?

An unauthorized person can be recognized as a legitimate user of the console that manages your virtual servers, without holding a valid password.

VMware vCenter is the central dashboard that administers virtual servers, servers that don’t exist as separate hardware but run by the dozens on a single physical machine. The NVD listing describes, under identifier CVE-2026-123890, an authentication bypass: identity verification can be sidestepped. Think of a subway station with a side door that opens straight onto the platform: nothing is forced, the fare gate is simply avoided.

Why is it serious?

The score is 9.8 out of 10 according to the NVD listing, assigned by the reporting organization (CNA), and the Canadian Centre for Cyber Security reports that the vulnerability is being exploited.

We always separate theoretical risk from confirmed exploitation. Here, a Canadian authority states that exploitation is occurring, in its bulletin AV26-1185 dated November 19, 2026. vCenter controls the entire fleet of virtual servers. Access gained at this level can lead to a complete shutdown of operations, the leak of customer or employee personal information, or the groundwork for internal fraud.

Who is affected?

Versions 9.1.x, 9.0.x, 8.0 and 5.x of VMware vCenter, along with several versions of Telco Cloud Platform and Telco Cloud Infrastructure.

According to the NVD listing, the fixed versions are 9.1.1.0200 for the 9.1.x branch, 9.0.2.0200 for the 9.0.x branch, 8.0 U3m for version 8.0, and 5.2.5 for the 5.x branch. Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x and 5.2, as well as Telco Cloud Infrastructure 3.0, are also affected. For these products, the listing points to a vendor technical note (KB463116) and does not list a fixed version number. In Quebec, this concerns SMBs that host their own servers (manufacturers, carriers, clinics, accounting firms). If your servers are managed by a provider, check your exposure with them rather than assuming it.

How do I check my business?

A few questions in writing to your provider are enough to gauge your exposure, with no technical expertise required on your part.

  • Ask your IT provider by email whether vCenter is used for your servers, which version is running, and when the patch will be applied (management).
  • Compare the version in production against the fixed versions listed above, then schedule the patch starting with servers reachable from the network (IT provider).
  • Confirm the applicable procedure if Telco Cloud Platform or Telco Cloud Infrastructure is present in your environment (software vendor).

Scenario

Fictional example: a regional carrier with about twenty employees had not applied the patch.

On a Monday morning, the management console stops responding and the servers that handle truck dispatching and delivery slips stay down. The day turns into a string of phone calls: drivers to redirect, customers to warn that deliveries are slipping by a day, invoices on hold. The provider rebuilds access, then the logs need to be reviewed to determine whether employee records were accessed. A late delivery is easy to explain; doubt about personal information is not.

What to do now

  • Find out today, with your provider, whether vCenter is present and which version is running.
  • Apply the vendor’s patch as a priority on servers reachable from the network.
  • Restrict access to the management interface to authorized administration workstations only, and do not expose it directly to the internet.
  • Have someone review the authentication logs, the technical records of connections, to spot unusual logins or unplanned administrator access.
  • Document the steps taken and their dates. A preventive update is not a confidentiality incident: the Law 25 register applies to confirmed incidents.

Key points on the VMware vCenter vulnerability

A patch is available, exploitation has been reported, and the time it takes to apply it is now the real variable. There is no absolute protection: be wary of any claim promising zero risk.

FAQ

Our servers are hosted with a provider. Are we affected?

You cannot know this on your own: the management console may belong to the provider and serve several clients, and only their answer will confirm it. Ask the question in writing, naming the vulnerability, and keep the response on file. This record helps if a review is requested later, and simplifies the conversation with your insurers and your clients.

Can we wait for the next maintenance window?

This is a management decision, not a technical one. When an authority such as the Canadian Centre for Cyber Security reports active exploitation, we recommend treating the fix as a priority. If a planned outage isn’t possible in the short term, ask your provider what access-limiting measures it is applying in the meantime, and set a written date for the fix.

How do we know if someone has already taken advantage of this?

Having a qualified person review the authentication logs is the first step. Be aware: the absence of a trace is not proof that no intrusion occurred. If a confidentiality incident involving personal information is confirmed, it must be entered in the register, and notification to the Commission d’accès à l’information (Quebec’s privacy regulator) and to affected individuals depends on the risk of serious harm.

Sources


Source: NVD (NIST) · https://nvd.nist.gov/vuln/detail/CVE-2026-123890

Article prepared by RISS Canada’s threat intelligence team from the public sources cited above, with the assistance of artificial intelligence tools, then reviewed according to our editorial standards.

Related reading

Cybersecurity · World

jDownloads Security Vulnerability: 10.0 out of 10 Score for Unpatched Joomla Sites

The jDownloads security vulnerability, an extension for Joomla sites, scores 10.0 out of 10 according to the NVD record, and a fix is available in version 4.1.8. No exploitation has been reported so far, but a site takeover would still cost customer trust.

  • Critical vulnerability
  • CVE-2026-117551
  • jDownloads

Cybersecurity · World

AutomatorWP Security Vulnerability Rated 9.8 Out of 10 by NIST’s NVD

An AutomatorWP security vulnerability affects the Webhooks module in AutomatorWP Pro for WordPress, in versions up to and including 1.4.4. The NVD listing reports no known exploitation, but the severity score is among the highest possible.

  • Critical vulnerability
  • CVE-2026-126173
  • AutomatorWP

Cybersecurity · World

ELEX HelpDesk Vulnerability Scores 9.8 Out of 10 From Reporting Body

The ELEX HelpDesk vulnerability affects every version up to and including 3.3.9 of this WordPress customer-support plugin. The 9.8 out of 10 score, assigned by the reporting body and listed in the NVD entry, is near the maximum, and no exploitation has been reported to date.

  • Critical vulnerability
  • CVE-2026-119077
  • WordPress

Where do you really stand with Law 25?

Our assessment measures your exposure and concrete obligations, no jargon.