Blog

Java4Shell: Update Every Java Runtime You Can Find

Java4Shell can turn malformed Base64 data into memory corruption and remote code execution. Update Java, bundled applications, containers, and appliances now.

Dmytro
java java4shell cve-2026-114938 security

Java4Shell: Update Every Java Runtime You Can Find

A serious vulnerability in Java can turn malformed Base64 data into memory corruption and, under the right conditions, remote code execution. Patches are available, the technical details are public, and the short version is uncomplicated: update every Java runtime you operate immediately.

That includes the obvious Java installations on servers and developer workstations. It also includes Java hidden inside containers, business applications, NAS devices, management appliances, and whatever smart device in the corner has quietly been running the same firmware since everyone still called televisions “not smart.” If Java is built into a TV or another appliance, check its manufacturer’s security notices and install the relevant firmware update.

The vulnerability is tracked as CVE-2026-114938 and has a CVSS 3.1 score of 8.1. The researchers who demonstrated a complete exploitation path rate it as critical under CVSS 4.0.

A Base64 decoder should not become a shell

Java includes optimized machine code for common operations. On supported x86-64 processors, HotSpot can use AVX-512 instructions to decode Base64 faster. Unfortunately, an error in that optimized path can make specially formed input write beyond the end of its allocated buffer.

In plain English, data that should merely be rejected can corrupt the Java process’s memory first.

The Calif research team showed how this primitive could be developed into disclosure of data from the Java heap and, for selected applications, remote code execution. An attacker may need an application-specific route that accepts Base64 data and suitable conditions inside the JVM, so this is not one universal magic request that compromises every Java program. It is still a dangerous vulnerability in a very widely used runtime, with public research explaining the underlying technique.

Oracle and OpenJDK published fixes on November 17, and CISA is urging organizations to apply them immediately. At the time of publication, there was no confirmed evidence of active exploitation in the wild. That is useful context, not permission to schedule the update for some peaceful weekend next month.

Which systems are affected?

The vulnerable optimized decoder is present in recent HotSpot-based Java releases. Calif identifies OpenJDK 17 from 17.0.6 onward, as well as the current Java 21, 25, and 27 lines. Oracle also lists an affected performance build of Java 8. OpenJDK distributions derived from the same code can be affected, including Oracle Java, Eclipse Temurin, Amazon Corretto, Microsoft Build of OpenJDK, Azul Zulu, Red Hat OpenJDK, BellSoft Liberica, and others.

Exploitation of this particular code path requires an x86-64 processor with AVX-512 VBMI support. That includes modern Intel Xeon and AMD EPYC generations commonly found in servers. ARM64 systems do not use the vulnerable path.

However, using the CPU model as a reason not to update is a poor inventory strategy. Virtual machines move between hosts, container images get deployed elsewhere, hardware is replaced, and the same application may have several copies of Java. The November OpenJDK release also corrects other security issues across supported Java branches. Install the current security update supplied by your Java distributor.

You can see which runtime a shell uses with:

java -version

That command finds one Java installation. It does not prove there are no others.

The Java you cannot see still counts

Many products include their own JRE or JDK. Updating the operating system’s java package may leave the private runtime inside Jenkins, Jira, Confluence, Keycloak, an identity appliance, or another packaged application unchanged. In that case, follow the product vendor’s security bulletin and update the application or its bundled runtime exactly as supported.

For containers, pull or build an image containing a corrected Java release, redeploy it, and confirm that old replicas are gone. Updating Java on the container host does not change the runtime inside an existing image.

For a NAS, smart TV, router, storage appliance, or other embedded device, check the manufacturer’s support page. Do not unpack a random JDK archive onto an appliance and hope it improves the evening. The vendor may need to test and ship a complete firmware or product update, and the device may use a different architecture that is not affected by this exact flaw. What matters is obtaining a clear answer from the vendor and keeping the product’s software current.

An inventory should cover at least:

  • Operating-system Java packages and manually installed JDKs
  • Application-bundled runtimes
  • Container base images and CI runners
  • Development, staging, and forgotten test systems
  • NAS devices, management appliances, and other embedded products

After updating, restart the Java processes and verify the runtime actually in use. New files on disk do not patch a JVM that is still running from memory.

Temporary controls are only temporary

If an update genuinely cannot be installed at once, the Calif researchers describe two JVM options that disable the affected optimized path: -XX:-UseBASE64Intrinsics, or -XX:UseAVX=2 on x86-64 systems. Test either change carefully before production use. The second option is not accepted by ARM builds and can prevent Java from starting there.

Reducing unauthenticated access, limiting request sizes, validating Base64 input, and applying vendor-provided WAF rules may also make known attack routes harder to reach. These measures are useful for buying a small amount of maintenance time. They are not substitutes for a corrected runtime, particularly because different applications expose Base64 decoding in different ways.

Update Java, then look for the copies you missed

Java4Shell is serious because the vulnerable component sits below a huge range of applications. The affected fast path is hardware-specific and reliable exploitation requires more than discovering an open port, but public research has already demonstrated memory disclosure and remote code execution.

Update supported JDKs and JREs now. Rebuild containers, update products with bundled runtimes, and ask appliance manufacturers for their security status. Yes, even check the TV. It may not be affected by this exact vulnerability, but finding out that its last security update arrived four years ago is still valuable information.

The best time to discover every hidden Java runtime was before a critical vulnerability. The second-best time is before someone else discovers it for you.

Need Help?

Our support team is available 24/7 to assist you with any questions or issues.

Contact Support