Back to all news
Industry NewsUsama Asif5 min read

Java4Shell (CVE-2026-114938): What Businesses Running Java Should Do Now

On 17 November 2026, Oracle and OpenJDK fixed Java4Shell (CVE-2026-114938), a flaw in the Java runtime's fast Base64 decoder on newer Intel and AMD servers. Which Java versions and CPUs are affected, how far exploitation has got, and what to patch first.

Illustrative example

On 17 November 2026, Oracle and the OpenJDK project fixed Java4Shell (CVE-2026-114938), a memory corruption flaw in the Java runtime's fast Base64 decoder on newer Intel and AMD servers. A crafted Base64 string can crash a Java service and, in some applications, allow remote code execution without logging in. Code that reproduces the bug was public by 18 November.

What happened

Researchers at Calif found the flaw and named it Java4Shell. Oracle credits Quang Luong of Calif.io and Albert Yang, and shipped the fix in its November 2026 Critical Security Patch Update on 17 November, the same day as the OpenJDK fixes.

The bug sits in a hardware-specific optimisation in HotSpot, the standard Java virtual machine. On x86-64 processors that support the AVX-512 VBMI instructions (Intel Xeon Ice Lake or later, AMD Zen 4 or later), the JVM switches Base64 decoding to an accelerated routine. A malformed final group of characters makes its length calculation go negative, and the routine writes past the end of its output buffer. On other processors, ARM64 included, Java uses a different decoding path that does not contain the defect.

An attacker needs the application to decode Base64 they control, and that is common: HTTP Basic credentials, JWTs, SAML messages and cookies are all Base64. Some services decode these before checking the password, which is why no login is needed. Oracle rates the flaw 8.1 on CVSS 3.1; Calif scores it 9.2 on CVSS 4.0.

Java lineAffected, per CERT-EUFixed build
Java 1717.0.6 to 17.0.2117.0.21.1
Java 2121.0.13 and earlier21.0.13.1
Java 2525.0.5 and earlier25.0.5.1
Java 2727.0.1 and earlier27.0.1.1
Java 8 and 11Standard builds not listed as affected; Oracle's Java SE 8 Performance builds (8u511-perf) are8u513-perf for those builds

Microsoft released fixed builds of its OpenJDK on 18 November. Tenable lists fixed builds from Amazon Corretto, Azul, Ubuntu and Red Hat, while Eclipse Temurin and Debian are still rolling them out.

How far exploitation has got. Calif published code that reproduces the memory corruption without taking control of a system, and is holding back its product-specific exploit chains. Tenable reports Calif's pre-authentication code execution results against Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate. VulnCheck says it has a working exploit for its customers, and says that crashing a JVM is easy while code execution needs extra steps. Tenable reports that, as of 18 November, GreyNoise had seen exploitation attempts but no confirmed success. As of 20 November, Sophos knows of no confirmed successful exploitation, and the flaw was not in CISA's Known Exploited Vulnerabilities catalog.

What it means for businesses

Our reading, not the researchers' or Oracle's:

The exposure is in the runtime, not your code. A Java service can be reachable even if nobody on your team ever wrote a line of Base64 handling, because login and token libraries do the decoding. Identity servers, issue trackers, build servers, search clusters and many internal business applications run on the JVM.

A version number alone does not answer the question. A service is exposed only when three things line up: an affected Java build, an affected processor, and untrusted Base64 reaching the decoder. Rapid7 makes the same point. That makes the inventory harder, but it also means a calm, ordered patch plan is realistic.

Bundled runtimes are the easy ones to miss. Updating the server's Java package does not fix the runtime that ships inside a vendor product, an appliance or a container image. Those stay vulnerable until the vendor or your build pipeline replaces them.

What to do next

  1. List every Java runtime you run, including ones bundled with vendor products and baked into container images. Check the running process, for example with jcmd and the process ID followed by VM.version, because the java on the command line may not be the one the service uses.
  2. Upgrade internet-facing services first, especially those that decode credentials or tokens before authentication, then the rest. Restart every JVM after the update and rebuild container images.
  3. Chase vendors for their own advisories. A product that carries its own Java runtime stays affected until its vendor ships an update.
  4. Treat the JVM flag as a stopgap only. CERT-EU and Deepwatch describe disabling the accelerated Base64 routine with a JVM option. Oracle and OpenJDK have not published it as a workaround and Sophos has not validated it, so test it before relying on it and patch anyway.
  5. Tighten input at the edge. As CISA advises, size limits and validation for Base64 fields, and less unauthenticated access, reduce what an attacker can send.
  6. Keep a runtime support calendar. Microsoft also says its Build of OpenJDK ends support for JDK 11 and 17 in September 2027. Runtime end dates deserve the same planning as the .NET 8 and 9 end of support.

Timeline Digital, a custom software development company founded in 2013 in Islamabad, keeps business systems patched under software maintenance and support agreements, which cover security patching and upgrades, and replaces runtimes close to end of support as part of legacy software modernization. Every project starts with a free pilot: Before you commit to the full project, we build 2 to 3 of your key modules as working software, free of charge, ready in about 2 days. Your team tests the pilot, and the full build starts only after you approve it.

Sources

Tags

  • Java4Shell
  • CVE-2026-114938
  • OpenJDK
  • Java Security
  • Patch Management
  • Software Maintenance

Start a conversation

Tell us how your business works.

Describe what is slowing your team down. We will help you work out what to build, and how a free pilot lets you judge our work before the full project.

Prefer WhatsApp? Start a chat

What happens next

  1. You send a short brief

    The problem, the people involved and any target date. A senior engineer replies within 4 business hours.

  2. We understand your workflow

    A first call about how your business works today. An NDA can be signed before you share details.

  3. You test a free pilot

    You choose 2 to 3 key modules and we build them first, so you judge real software before the full project.