A critical vulnerability dubbed “Java4Shell” (CVE-2026-114938) has been reported in OpenJDK. According to early reports, it lets unauthenticated attackers achieve remote code execution by sending a crafted Base64 string to a Java application running on x86 servers with AVX-512 support. Early reports rate it 9.2 under CVSS 4.0. Java runs a large share of enterprise and cloud backends, so organizations should start inventorying their Java runtimes now and prepare to patch as soon as vendor builds are confirmed.

Security firm Calif, which says it discovered and reported the flaw, disclosed it publicly on November 17 because the details had already leaked, and says it will publish full technical details later that day, after Oracle releases its patch. Neither Oracle nor the OpenJDK Vulnerability Group has published an advisory that names this CVE, and as of this writing CVE records are only reserved but unpublished . [VERIFY @23:00]

Java4Shell key facts

FactDetail
CVECVE-2026-114938 [VERIFY @23:00: no CVE.org/NVD record yet]
Severity9.2 (CVSS 4.0, per early reports)
TypeReported heap buffer overflow in OpenJDK’s intrinsic Base64 decoder, leading to unauthenticated RCE
Likely affectedOpenJDK 17.0.6 and later; JDK 18+ lines contain the same code (scope unconfirmed)
Unlikely affectedJava 8 and 11; ARM-based hosts
Hardwarex86-64 with AVX-512 VBMI for the reported path
PatchOracle Nov 17 builds released; CVE not yet confirmed among fixes
ExploitationNo known in-the-wild exploitation or public PoC

What is Java4Shell (CVE-2026-114938)?

The issue is a memory-corruption bug in OpenJDK’s hardware-accelerated (intrinsic) Base64 decoder, the native code the JVM uses in place of the Java implementation of java.util.Base64 decoding on supported CPUs. A crafted 65-byte input reportedly causes an integer underflow in padding handling. The result is a 62-byte heap buffer overflow that can corrupt adjacent Java objects and lead to code execution. Base64 decoding of untrusted input is very common in Java applications (such as authentication headers, tokens and encoded API payloads), so the reachable attack surface can be large. Exploitation still requires attacker-controlled data to reach the decoder.

Which Java versions could be affected by Java4Shell?

Public reports so far say “OpenJDK 17.0.6 and later”. Orca Research reviewed the OpenJDK source history to see which Java versions contain the reported vulnerable code. Containing the code does not by itself confirm that a version is exploitable; confirmation is expected once full technical details and vendor advisories are published:

  • The 17.0.6 boundary matches the code. The AVX-512 Base64 decoding intrinsic (JDK-8268276) was backported to the JDK 17 update line in November 2022 and first shipped in OpenJDK 17.0.6 (January 2023). It is not present in 17.0.5.
  • Newer Java lines likely carry the same code. The same decoder was added to mainline OpenJDK in 2021 and first released in JDK 18. JDK 21, 25 and 27 therefore contain it. Early reports mention only Java 17, and it has not been confirmed whether these newer lines are affected; until Oracle or OpenJDK clarifies the scope, organizations may want to treat them as potentially exposed. [VERIFY @23:00]
  • Java 8 and 11 do not contain this decoder intrinsic in OpenJDK, so they are unlikely to be affected by Java4Shell. Oracle released updates for these lines on November 17 (8u513 and 11.0.33.1) as part of the same patch update.
  • Hardware matters. On Java 17, the Base64 intrinsic is enabled only on x86-64 CPUs with AVX-512; on Java 21 and later it is also enabled on CPUs with AVX2. However, the AVX-512 decoding path that early reports point to runs only on CPUs with the AVX-512 VBMI extension (e.g., Intel Ice Lake and later, AMD Zen 4 and later). ARM-based hosts (e.g., AWS Graviton) use different decoder code and are not known to be affected.
  • All distributions are in scope. The code is in upstream OpenJDK, so Oracle JDK, Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK, Red Hat and distro OpenJDK packages built from affected versions should all be considered potentially affected, including JDKs bundled inside applications and container images.

Is there a patch for CVE-2026-114938?

On November 17, Oracle released new builds for Java 8, 11, 17, 21, 25 and 27 (8u513, 11.0.33.1, 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1) as part of its November Critical Security Patch Update. According to Oracle’s pre-release announcement, the update contains 11 Java SE fixes, all remotely exploitable without authentication (highest CVSS 3.1 score 8.1). The 9.2 figure in early reports is a CVSS 4.0 score, while Oracle uses CVSS 3.1, so Oracle’s 8.1 maximum neither confirms nor rules out that CVE-2026-114938 is among the fixes. Oracle’s release notes for these builds do not name CVE-2026-114938. Oracle has not confirmed that CVE-2026-114938 is among the fixes, and other OpenJDK vendors (Temurin, Corretto, Zulu and others) release on their own schedules. [VERIFY @23:00  –  confirm fixed versions per vendor]

How to mitigate Java4Shell before a patch is confirmed

No vendor-validated workaround has been published.  It can be suggested to limit AVX usage or disable Base64 intrinsics as temporary measures. In HotSpot, the JVM option -XX:-UseBASE64Intrinsics disables the Base64 intrinsic entirely, while -XX:UseAVX=2 prevents the JVM from using the AVX-512 decoding path (on Java 21 and later the intrinsic remains active through its AVX2 path). These options exist in affected JDKs, but they have not been validated by Oracle or OpenJDK as a fix for this CVE, they may affect performance, and they do not replace patching. Recommended steps:

  • Inventory every Java runtime: OS packages, tarball/zip installs, JDKs bundled in applications and container base images, on both Linux and Windows.
  • Prioritize internet-facing Java services that decode untrusted Base64 input.
  • Apply vendor updates as soon as fixed builds for CVE-2026-114938 are confirmed, and rebuild container images on patched base images.

Is Java4Shell being exploited in the wild?

At the time of writing, there are no reports of in-the-wild exploitation and no public proof-of-concept. Technical details are expected to become public within hours, which typically shortens the time to working exploits significantly. Organizations should treat this as urgent.

How can Orca help?

Orca enables customers to quickly identify assets running potentially vulnerable Java versions across installation methods  –  OS packages, standalone JDK installations and JDKs bundled in container images  –  on both Linux and Windows. Customers can understand each asset’s exposure in context, including internet accessibility, runtime reachability and asset criticality, and prioritize remediation based on real risk.