Technology advice

Critical Java Flaw CVE-2026-114938: Check Business PCs and Servers

CISA says organisations should patch CVE-2026-114938. Here is how to find separate and bundled Java runtimes without breaking essential software.

Java is still used by some accounts packages, line-of-business tools, server software and older specialist applications. A serious flaw in the Java runtime therefore matters even if nobody remembers installing Java as a separate program.

On 17 November 2026, the US Cybersecurity and Infrastructure Security Agency (CISA) told organisations to patch CVE-2026-114938. CISA calls the flaw "Java4Shell". It affects the Base64 decoder in the x86-64 HotSpot Java Virtual Machine, part of the Java Development Kit.

Specially made Base64 data could crash Java or allow an attacker to run code remotely without signing in. Oracle gives the flaw a CVSS score of 8.1. Its risk matrix says the attack can come over a network, needs no privileges or user interaction, but has high attack complexity. Neither CISA nor Oracle says in these advisories that the flaw is being actively exploited.

Which computers need checking?

This is mainly a job for businesses and people who use specialist software. A normal home PC with no Java-based software may have nothing to update.

The difficult part is finding every copy. CISA warns that Java runtimes may be:

  • installed as a separate program;
  • bundled inside another application;
  • included in a container image; or
  • built into an appliance.

That means a quick look through the Windows installed-apps list is useful, but it is not a complete check. Oracle's November 2026 risk matrix lists affected Oracle Java SE builds including 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3. It also lists affected Oracle GraalVM products.

What to do now

Start with the software that matters to the business. Check the support page or contact the supplier for each Java-based application. Install the supplier's approved update where Java is bundled, because replacing the embedded runtime by hand can stop the application working.

For separately managed Oracle Java installations, use Oracle's November 2026 security advisory to identify the relevant patch. Test updates on one non-critical computer before rolling them out across a workplace. Back up important business data first, and plan a short maintenance window for server software.

Prioritise systems that accept connections from the internet. CISA also recommends watching for unexpected Java crashes, unknown Java runtimes and suspicious Java processes. A crash by itself is not proof of an attack, but repeated unexplained crashes deserve investigation.

Do not download a "Java fix" from a pop-up, advert or unsolicited email. Use Oracle, the application supplier or your managed IT provider. Do not remove Java blindly either: an old but essential application may depend on a particular runtime.

When local help makes sense

If you are unsure which application installed Java, or several office PCs and a server need checking, this is a sensible small-business IT task. We can inventory the machines, identify bundled and separate runtimes, check the software supplier's guidance and plan updates with less disruption. A straightforward check on an individual computer may also be suitable for remote support.

Related local help

Sources

CallEmail