Digital security

Java and VMware vCenter: two critical November updates not to postpone

E
ElaraTeq
Cover: Java and VMware vCenter, two critical November 2026 updates with NCSC warning; glass panels with processor, server, alert, padlock and update symbol over a night lake

Oracle fixes eleven Java flaws and the NCSC asks operators to check their systems; Broadcom closes a critical vCenter flaw exploited since September. Inventory, updates and checks for SMEs.

Within a few days, two security updates arrived that affect parts of business IT that are often out of sight. On 17 November 2026 Oracle and the OpenJDK project fixed several Java vulnerabilities, and the National Cyber Security Centre (NCSC) published a warning for system operators. On 19 November Broadcom fixed a critical VMware vCenter flaw that, according to Google, had already been exploited since September.

Not every SME in Ticino uses vCenter, but many use Java-based software without knowing it. In both cases the first question is the same: where is this component in our company, and who updates it?

Java: eleven fixes and an often hidden component

Oracle’s November security update contains eleven fixes for Java SE; according to Oracle, all of them can be exploited over the network without credentials. The most severe, CVE-2026-114938 (CVSS score 8.1), is a memory handling error in the compiler of the Java virtual machine. Oracle rates it as difficult to exploit. According to CERT-EU it can crash the application and, in some cases, allow remote code execution, but only when several conditions are met at the same time: a recent x86-64 processor with AVX-512 instructions (Intel Xeon Ice Lake or later, AMD Zen 4 or later) and externally controlled data reaching a specific decoding function. ARM64 systems are not affected.

The fixed versions of Oracle Java SE are 8u513, 11.0.33.1, 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1; the OpenJDK advisory lists the same flaws for the open distributions. Distributions such as Eclipse Temurin, Amazon Corretto or Azul Zulu release fixes on their own schedules, and programs that ship their own Java remain vulnerable until their vendor provides an update. The sources consulted do not report attacks so far, but the NCSC advises not to wait.

Java is often found in business software, application servers, access systems and development tools, sometimes installed by the vendor and never touched again. That is why the NCSC first asks for an inventory.

VMware vCenter: critical flaw already exploited

vCenter is the console used to manage VMware virtual servers. The vulnerability CVE-2026-123890 (CVSS 9.8) lies in the vCenter directory service: anyone who can reach the system over the network can bypass authentication and gain access without a password. Broadcom’s VMSA-2026-0009 advisory of 19 November, updated on the 20th, lists 9.1.1.0200, 9.0.2.0200, 8.0 U3m and, for VMware Cloud Foundation 5.x, 5.2.5 as fixed versions. For vCenter 7.0, which is no longer supported, customers with an extended support contract should contact Broadcom. There are no official workarounds. The same advisory fixes four other flaws in SDDC Manager and VMware Tools for Windows.

According to the report by Google Threat Intelligence and Mandiant, a group believed to be linked to the Chinese state exploited the flaw from early September 2026, before a fix existed, creating administrator accounts and then moving on to other servers in the network. On 20 November the US agency CISA added the flaw to its catalogue of exploited vulnerabilities.

What to do in your company

  1. Take an inventory of Java. List the programs and servers that use Java, the version and who is responsible, including software supplied by third parties. Ask vendors whether their products are affected and when the update will arrive.
  2. Update and restart. After a Java update, applications must be restarted, otherwise they keep using the old version. Give priority to systems reachable from the internet.
  3. Update vCenter now. If you use VMware, check the vCenter version today with whoever manages your infrastructure and schedule the update as a priority. A console still on version 7.0 is a risk to address with a migration plan.
  4. Consoles only from the admin network. vCenter and other management consoles should not be reachable from the internet or from the whole office network. See also the internet-exposed services to check in the office.
  5. Check after patching. Because the flaw was exploited before the advisory, updating is not enough: have your provider check for unknown administrator accounts and review the technical guidance published by Google.

If there has been an incident

If an attack affected personal data, Article 24 of the Federal Act on Data Protection (FADP) requires data security breaches that are likely to result in a high risk for the persons concerned to be reported to the FDPIC as soon as possible; the FDPIC guidelines help with the assessment. Incidents can be reported to the NCSC through its reporting form. For most SMEs reporting is voluntary; operators of critical infrastructure, however, have a reporting obligation for cyberattacks within 24 hours.

Our approach

ElaraTeq Sagl keeps an inventory of the components of the servers it manages for SMEs, applies security updates in a planned way and restricts management consoles to the admin network (hosting). For other urgent November updates see Outlook and Chrome and firewalls and VPNs; for the late October cases, including VMware ESX, see the exploited vulnerabilities of late October. For a review of your infrastructure you can request consulting or contact us.

Sources

Tags: #Java #OpenJDK #Oracle #VMware #vCenter #CVE-2026-123890 #CVE-2026-114938 #UFCS #PMI
Share:

Want to Work With Us?

Let's discuss how we can help bring your vision to life.

Get in Touch