Back

20/11/2026

Java4Shell (CVE-2026-114938): who is affected, how to check, and which Java builds fix it

Java4Shell lets attackers run code on Java 17+ servers with AVX-512 CPUs, without logging in. How to check your systems, the workaround and fixed builds.

On 17 November 2026, Oracle shipped fixes for a critical flaw in Java that researchers have named Java4Shell (CVE-2026-114938). Under the right conditions, an attacker can run code on a Java server without logging in, simply by sending a specially crafted Base64 string. Most Java vendors have now published fixed builds. This post explains who is affected, how to check your own systems in a few minutes, the temporary workaround, and which build to install from each vendor.

Key takeaways

  • Java4Shell is a memory corruption bug in Java’s built-in Base64 decoder. It can lead to remote code execution without authentication.
  • Only Java 17.0.6 and later (17, 21, 25 and 27) running on x86-64 CPUs with the AVX-512 VBMI instruction set are exposed. Standard Java 8 and 11, ARM64 servers and older x86-64 CPUs are not.
  • Many modern servers and cloud instances (Intel Ice Lake or newer, AMD Zen 4 or newer) have AVX-512 VBMI, and Base64 is decoded before login in many applications.
  • Fixed builds are available from Oracle, Eclipse Temurin, Amazon Corretto, BellSoft Liberica, Azul Zulu and Microsoft. Red Hat has fixed its portable builds; RHEL packages were still pending at the time of writing.
  • Until you can update, start the JVM with -XX:-UseBASE64Intrinsics.

What Java4Shell is

The flaw was reported by the security research firm Calif. It sits in java.util.Base64.Decoder, the Base64 decoder that ships with every Java runtime. Since OpenJDK 17.0.6, when the CPU supports the AVX-512 VBMI instruction set, the JVM automatically switches to a hardware-accelerated version of this decoder. That accelerated code mishandles certain malformed input and writes past the end of its output buffer. Red Hat states that an attacker who controls the input may be able to run code with the privileges of the Java process.

Severity scores differ because vendors use different scoring systems. Oracle rates the flaw 8.1 under CVSS 3.1, the researchers rate it 9.2 (Critical) under CVSS 4.0, and Red Hat rates it Critical. These are different scales for the same vulnerability, not a disagreement about whether it is serious.

As of 18 November, no exploitation in the wild had been reported, and the flaw was not in CISA’s Known Exploited Vulnerabilities catalog. Calif says it has demonstrated pre-authentication code execution against widely used Java applications in their default configuration, but it is holding back its exploit code. Now that the root cause is public, that window may not stay open for long.

Who is affected: four conditions

According to Red Hat’s security bulletin RHSB-2026-018, a system is exposed only when all four of these are true:

  1. The application runs on OpenJDK 17.0.6 or later, including Java 21, 25 and 27, on a build without the fix.
  2. The host CPU is x86-64 and supports AVX-512 VBMI. That includes Intel Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, and AMD Zen 4, Zen 5 and Zen 6.
  3. The JVM has not been limited to AVX2 or lower with -XX:UseAVX=2.
  4. The application passes attacker-controlled Base64 data to the standard Java decoder.

The fourth condition sounds narrow, but it is not. HTTP Basic authentication headers, SAML artifacts, CSRF tokens and MIME encoded email headers are all Base64, and they are often decoded before the user has logged in. No special setting is needed: on a matching CPU, a default installation is vulnerable. Researchers have named products such as Keycloak, Jenkins and Jira as reachable without a login.

The cloud makes condition 2 easy to meet. Red Hat lists AWS C6i, M6i, R6i, C7i, M7i and R7a, Google Cloud C3, C3D, C4, C4D, N4, N4D, M3 and M4, and Azure Dsv5, Dsv6, Dasv6 and Dasv7 as instance families that are likely affected.

Not affected: standard Java 8 and 11, where this accelerated code does not exist, ARM64 servers (including AWS Graviton), and x86-64 CPUs older than Ice Lake or Zen 4. One exception: Oracle also lists its Java SE 8 Enterprise Performance Pack build (8u511-perf) as affected.

How to check your systems

Start with the Java version. Any 17.x from 17.0.6 onward, and any 21, 25 or 27 build older than the fixed builds below, is a candidate.

java -version

Then check whether the CPU supports AVX-512 VBMI. On Linux:

grep -o avx512vbmi /proc/cpuinfo | head -1

If this prints avx512vbmi, the CPU is in scope. If it prints nothing, Red Hat says the system is not affected by this vulnerability. Run the check on each host type you use, because a cluster can mix CPU generations.

Do not stop at the Java installed on the operating system. Many applications and appliances ship their own Java runtime inside the product or inside a container image. List every runtime your applications actually use, including the vendor and the full build number.

Temporary workaround

If you cannot install a fixed build right away, Red Hat recommends starting each affected JVM with one of these options:

  • Preferred: -XX:-UseBASE64Intrinsics. This turns off only the hardware-accelerated Base64 code. The vulnerable path is removed, and other AVX-512 optimisations stay on. Applications that decode a lot of Base64 may run slightly slower.
  • Alternative: -XX:UseAVX=2. This turns off all AVX-512 instructions. Use it only on x86-64: an ARM64 JVM given this option will fail to start.

To confirm the option is active on a running JVM, check the live flags instead of the startup script:

jcmd <pid> VM.flags -all | grep -F UseBASE64Intrinsics

The result should show UseBASE64Intrinsics = false. These options are a stopgap. Once you have installed a fixed build, remove them.

Fixed builds by vendor

LOGIQ checked each vendor’s official downloads and release information on 19 November 2026. Vendors are still updating their pages, so confirm the build with your vendor before you roll it out.

VendorJava 17Java 21Java 25Java 27
Oracle JDK17.0.21.121.0.13.125.0.5.127.0.1.1
Eclipse Temurin17.0.21.1+221.0.13.1+225.0.5.1+227.0.1.1+4
Amazon Corretto17.0.21.1.221.0.13.1.225.0.5.1.227.0.1.1.4
BellSoft Liberica17.0.21.1+521.0.13.1+525.0.5.1+527.0.1.1+5
Azul Zulu17.0.21.121.0.13.125.0.5.127.0.1.1
Microsoft Build of OpenJDK17.0.21.121.0.13.125.0.5.1–
Red Hat build of OpenJDK17.0.21.1 (portable, Windows)21.0.13.1 (portable, Windows)25.0.5.1 (portable)–

Red Hat Enterprise Linux is the main gap. The java-17, java-21 and java-25 OpenJDK packages for RHEL 8, 9 and 10 were still listed as affected on 19 November, with fixes being expedited. Products built on RHEL or UBI, including container images, Keycloak and JBoss images, inherit that status. Until the updated packages arrive, use the workaround on these systems.

The same Oracle update fixed 10 other Java vulnerabilities. Several of them, including CVE-2026-114939 (JGSS) and CVE-2026-114940 (JSSE), both rated 7.4, also affect Java 8 and 11. So even if Java4Shell does not apply to you, plan to install this month’s update on your Java 8 and 11 systems too.

What to do now

  1. Find your exposure. Run the version and CPU checks above. Start with internet-facing services and anything that handles logins, such as single sign-on, CI servers and API gateways.
  2. Update where a fix exists. Install your vendor’s fixed build from the table, then restart the application. A new JDK on disk does nothing until the JVM restarts.
  3. Apply the workaround where it does not. On RHEL packages and on products that bundle their own Java, start the JVM with -XX:-UseBASE64Intrinsics and confirm it with jcmd. Remove the flag after you update.
  4. Ask your product vendors. For appliances and commercial software with a bundled JVM, get the update through the vendor’s support channel rather than replacing the runtime yourself.
  5. Rebuild container images. Images built on older Java base images keep the vulnerable runtime until they are rebuilt and redeployed.
  6. Patch Java 8 and 11 as well. They are not exposed to Java4Shell, but the same update fixes other vulnerabilities that do affect them.

The bottom line

Java4Shell needs four conditions to line up, but on modern x86-64 servers and cloud instances running Java 17 or later, those conditions are common, and the attacker does not need to log in first. Fixed builds are available from almost every vendor. Check your Java versions and CPUs today, update where you can, and use the workaround everywhere else until the fix arrives.

Need help finding and updating Java runtimes across your servers and containers? Contact the LOGIQ team.

Sources

Photo: luis gomes / Pexels