Java4Shell (CVE-2026-114938): Oracle and OpenJDK Security Updates (November 2026)

Abstract teal hexagon and patched data path illustrating Java4Shell Oracle and OpenJDK security updates in November 2026

Written by

in

Takeaway: On November 17, 2026, Oracle published its November 2026 Critical Security Patch Update and the OpenJDK project issued a matching vulnerability advisory. Both include a fix for CVE-2026-114938, a memory-corruption issue in the HotSpot JVM that U.S. and Canadian agencies are calling Java4Shell. Install a fixed Java build for the release family you actually run, then restart every JVM so the new runtime is what is in memory.

CISA describes Java4Shell as a critical memory-corruption vulnerability in the Base64 decoder of the x86-64 HotSpot JVM and says specially crafted Base64 input could crash the JVM and allow unauthenticated remote code execution. OpenJDK and Oracle assign a CVSS 3.1 base score of 8.1; CERT-EU, in an 18 November advisory, calls it high severity with that same score. CISA’s “critical” label is not the same as Oracle’s 8.1 score or the name of Oracle’s Critical Security Patch Update program. This is a Java runtime update, not a WordPress core or plugin patch, and it is separate from this week’s nginx 1.31.9 and 1.30.7 security releases, the NoisyTCP Linux kernel advisory, and the Oxygen 6.2.2 builder update.

What official sources say

Oracle announced the update in a November 17 security blog post. The Java SE risk matrix lists 11 new security patches, all described as remotely exploitable without authentication; CVE-2026-114938 is one of those issues, not a label for the entire set. Oracle places the CVE in the Compiler component of Oracle Java SE, Oracle GraalVM for JDK, and Oracle GraalVM Enterprise Edition. It says a difficult-to-exploit vulnerability allows an unauthenticated attacker with network access via multiple protocols to compromise those products, and that successful attacks can result in takeover. Oracle also notes that this vulnerability can only be exploited by supplying data to APIs in the specified component without using untrusted Java Web Start applications or untrusted Java applets, such as through a web service. The published CVSS 3.1 vector is AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. OpenJDK places the same CVE in hotspot/compiler and marks it for JDK 17, 21, 25, and 27, not for JDK 8 or 11.

CISA’s November 17 alert, written with a contribution from the Canadian Centre for Cyber Security, urges organizations to inventory JDKs and Java runtimes — including copies bundled with third-party applications or included in container images and appliances — and to patch internet-facing systems first. CISA notes that those runtimes may not appear as separate inventory entries and does not endorse vendors. CCCS alert AL26-029, also dated November 17, classifies the issue as a heap-based buffer overflow (CWE-122) that affects the Base64 standard Java library. CCCS says it could be exploited remotely without authentication by sending specially crafted base64 data to Java processes running on x86-64 processors that contain AVX-512 Vector Byte Manipulation Instructions (VBMI) hardware, with possible memory corruption, information disclosure, crashes, or arbitrary code execution.

CERT-EU Security Advisory 2026-021, published 18 November 2026, adds that ARM64 systems are not affected. It says exploitation requires an x86-64 CPU with avx512f, avx512bw, avx512vbmi, and bmi2 — it names Intel Xeon Ice Lake or later and AMD Zen 4 or later — plus the intrinsic being active, which is the default when those CPU features exist, and attacker-controlled Base64 data reaching the decoder. That is the level of technical detail official advisories give; this article does not describe how to build or test an exploit.

Which versions are affected

Oracle’s risk matrix for this CVE lists these supported versions as affected: Oracle Java SE 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, and 27.0.1.0.3; Oracle GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3; and Oracle GraalVM Enterprise Edition 21.3.20.0.3. That row does not include regular Oracle Java SE 8 builds such as 8u511b33, and it does not include Java 11. The product table at the top of the same CPU advisory does mention 8u511b33 and 11.0.33.0.3 because the November update covers the Java SE family as a whole, including other CVEs.

CERT-EU and CCCS both call out Oracle Java SE 8 performance builds. CERT-EU lists 8u511-perf, fixed in 8u513. CCCS lists 8u511b33-perf, fixed in 8u513-perf. They also publish ranges for the 17, 21, 25, and 27 families that go beyond the single build string in Oracle’s matrix; confirm the exact build you run against the vendor advisory. One CCCS table row is easy to misread: it compresses “Oracle OpenJDK” as versions 17.0.6 through 27.0.1.0.3, with a fixed version of 27.0.1.1. That is not an instruction to move every Java 17, 21, or 25 install up to 27.0.1.1. Use the per-family fixed builds: 17.0.21.1, 21.0.13.1, 25.0.5.1, or 27.0.1.1.

The OpenJDK advisory’s opening sentence says the affected versions are 27.0.1.0.3, 25.0.5.0.3, 21.0.13.0.3, 17.0.21.0.3, 11.0.33, 8u512, and earlier. That statement is for the release as a whole. The same advisory fixes other CVEs, some marked for JDK 8 and 11, including CVE-2026-114939 and CVE-2026-114940. Operators on 8 or 11 may still need those separate fixes. A separate OpenJFX row for CVE-2026-86144 is also not Java4Shell.

What to install, and temporary measures

Install the fixed build that matches your release family, then restart all JVMs. CERT-EU is explicit that you should restart after the update. Oracle’s Java Management Service note for this update, dated November 17, 2026, points to the 17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1 release notes, plus 11.0.33.1 and 8u513 for the broader Java SE update. The JDK 17.0.21.1 release notes are dated November 17, 2026. For Java4Shell on Oracle Java SE 8, use the performance-build fix (8u513-perf in CCCS’s wording; 8u513 in CERT-EU’s wording for those performance builds).

If you use an OpenJDK distribution such as Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK, BellSoft Liberica, SAP SapMachine, or a Red Hat build of OpenJDK, CERT-EU says those builds are also affected and that vendors release fixes on their own schedules. Products that ship their own Java runtime remain affected until that vendor supplies an update. Use the fixed build your vendor has actually published.

If you cannot patch immediately, CERT-EU says it is possible to disable the intrinsic with -XX:+UnlockDiagnosticVMOptions -XX:-UseBASE64Intrinsics, or alternatively to disable AVX-512 with -XX:UseAVX=2. The second option can reduce performance, and both need a JVM restart. CERT-EU suggests verifying with java -XX:+PrintFlagsFinal -version | grep UseBASE64Intrinsics. CCCS also mentions -XX:UseAVX=2 if you cannot patch, and, for inventory, lscpu | grep avx512 on Linux. CISA’s temporary compensating controls include restricting and validating Base64 input at the application boundary, enforcing input-size limits, and limiting unauthenticated access, plus monitoring for rogue runtimes, unexpected JVM crashes, and suspicious Java processes. CCCS also recommends considering isolation of internet-facing applications from public networks until a fix can be applied. None of those steps replaces the patch.

CCCS stated on November 17, 2026, that it was not aware of active exploitation at that time, and added that this can change quickly. We have not seen a later official update retracting that point-in-time statement.

Key facts

ItemWhat official sources say
Date17 November 2026 for the Oracle update, OpenJDK advisory, CISA alert, and CCCS AL26-029. CERT-EU 2026-021 is dated 18 November 2026.
CVE / nameCVE-2026-114938, widely called Java4Shell by CISA and CCCS.
ComponentOpenJDK: hotspot/compiler. Oracle: Compiler. CISA: Base64 decoder of the x86-64 HotSpot JVM. CCCS: CWE-122 in the Base64 standard library.
Scores and labelsOpenJDK and Oracle: CVSS 3.1 8.1. CISA: “critical.” CERT-EU: “high severity,” CVSS 8.1. CCCS: “critical vulnerability.”
Oracle-listed affected builds for this CVEOracle Java SE 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3; GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3; GraalVM EE 21.3.20.0.3. Regular Java 8 and Java 11 are not on this CVE’s Oracle row.
Per-family fixed versionsCCCS/CERT-EU: 8u513-perf / 8u513 for Oracle Java SE 8 performance builds; 17.0.21.1; 21.0.13.1; 25.0.5.1; 27.0.1.1; GraalVM for JDK 17.0.21.1 and 21.0.13.1; GraalVM EE 21.3.20.1 (CCCS). Do not jump every 17.x install to 27.0.1.1.
CERT-EU preconditionsARM64 is not affected. Requires an x86-64 CPU with avx512f, avx512bw, avx512vbmi, and bmi2, an active intrinsic, and attacker-controlled Base64 data reaching the decoder.
ExploitationCCCS said on 17 November 2026 that it was not aware of active exploitation at that time.
What to doInstall the fixed build for your release family and restart all JVMs. Temporary JVM flags and CISA compensating controls are stopgaps.

FAQ

Which Java versions should I install for Java4Shell?

Install the fixed build that matches your release family: 17.0.21.1, 21.0.13.1, 25.0.5.1, or 27.0.1.1 for the corresponding Oracle Java SE / OpenJDK lines, or your vendor’s matching fixed build. For Oracle Java SE 8 performance builds, CCCS lists 8u513-perf and CERT-EU lists 8u513. Confirm the exact string on the vendor’s release notes, then restart the JVM.

Are regular Java 8 and Java 11 affected by Java4Shell?

Not according to the OpenJDK risk matrix for CVE-2026-114938, which marks 17, 21, 25, and 27 only, or according to Oracle’s row for this CVE, which lists the Java 8 performance build 8u511b33-perf and does not list regular 8u511b33 or Java 11. The November 17 advisory as a whole still patches other issues that do affect 8 and 11.

Is Java4Shell officially rated critical?

It depends on the source. CISA calls it a critical vulnerability. CCCS also describes a critical vulnerability. OpenJDK and Oracle publish a CVSS 3.1 score of 8.1, and CERT-EU calls it high severity with that same score. Oracle does not use “critical” as the severity label on this CVE’s risk-matrix row.

Do I need to restart the JVM after I install the update?

Yes. CERT-EU recommends updating and restarting all JVMs after the update. A package install that leaves the old process running does not put the patched runtime into service.

What if I cannot patch immediately?

CERT-EU documents two temporary JVM options that require a restart: -XX:+UnlockDiagnosticVMOptions -XX:-UseBASE64Intrinsics, or alternatively -XX:UseAVX=2, which may reduce performance. CISA also recommends compensating controls such as restricting and validating Base64 input at the application boundary, enforcing input-size limits, and limiting unauthenticated access. The durable fix remains the patched build plus a restart.

Are Temurin, Corretto, Zulu, and other OpenJDK builds affected?

CERT-EU says OpenJDK-based distributions, including Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK, BellSoft Liberica, SAP SapMachine, and the Red Hat build of OpenJDK, are also affected and release fixes on their own schedules. Bundled runtimes stay affected until the product vendor ships an update. Use that vendor’s fixed build rather than a version number invented here.

Does the November 17 OpenJDK advisory only fix Java4Shell?

No. The advisory fixed multiple issues. Java4Shell is CVE-2026-114938 in hotspot/compiler. Other CVEs in the same advisory, including some marked for JDK 8 and 11, are separate. The opening “affected versions” sentence covers the release as a whole, not automatically this CVE.

Has Java4Shell been exploited in the wild?

CCCS said on November 17, 2026, that it was not aware of active exploitation at that time, while noting that this can change quickly. Treat that as a dated statement and check later official advisories rather than assuming it remains true indefinitely.

Comments

Leave a Reply