HighVulnerabilityPatch available

Java4Shell OpenJDK Base64 RCE flaw (CVE-2026-114938)

Java4Shell (CVE-2026-114938) is an OpenJDK Base64 decoder flaw on x86-64 AVX-512 VBMI CPUs; update Java 17, 21, 25 and 27 runtimes.

Published
Updated
Fixed in
Oracle Java SE 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1; Amazon Corretto 17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2, 27.0.1.1.4; other vendors not confirmed
Exploitation
No confirmed exploitation as of November 18, 2026 per Aikido; Sophos is not aware of public reports of exploitation; not listed in CISA KEV per Aikido

What happened

On November 17, 2026, Oracle released Java SE updates that address CVE-2026-114938, nicknamed “Java4Shell”. Sophos describes it as a memory corruption flaw in the Base64 decoder of the x86-64 HotSpot JVM. Crafted Base64 input could crash the JVM or lead to unauthenticated remote code execution.

Datadog Security Labs calls it an out-of-bounds write in OpenJDK’s optimized Base64 decoder. Its analysis says a malformed value with trailing padding produces a negative output length, which leads to a full-width AVX-512 store past the end of the destination array. Datadog says denial of service is the more readily achievable impact. Reliable code execution needs extra work tailored to each application and JVM environment, and no universal exploit exists.

Aikido credits the discovery to Calif. It reports that Calif claims remote code execution against default configurations of Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins and PingFederate without authentication, and against Apache Kafka, Solr, Elasticsearch, Gerrit and Spinnaker after authentication. Aikido also says other researchers have so far reproduced crashes and memory leaks rather than code execution, and that Calif’s public proof of concept triggers the corruption but does not give code execution.

CISA issued an alert on November 17 urging organizations to patch immediately. It also credits the Canadian Centre for Cyber Security with contributing.

Severity scores differ by source:

  • Oracle scores it CVSS 3.1 8.1 (High), according to Sophos.
  • The researchers who reported it rate it CVSS 4.0 9.2 (Critical), per the same Sophos advisory.
  • Cloudflare Radar notes that the CVE record was not yet published as of November 17, and that Aikido says the two figures may describe different issues.

Exploitation status: Sophos is not aware of public reports of exploitation. Aikido saw no confirmed reports as of November 18. Cloudflare says it detected no signs of exploits on its own Java workloads; it does not report on exploitation more broadly.

Am I affected?

You are exposed only if all of these are true, per Datadog and Aikido:

  • You run an affected Java build.
  • The CPU is x86-64 with AVX-512 VBMI (Aikido names Intel Xeon from Ice Lake and AMD Zen 4 and newer).
  • The JVM was not started with -XX:UseAVX=2.
  • The application passes attacker-controlled data to the JDK Base64 decoder.

ARM64 and x86-64 CPUs without AVX-512 VBMI are not affected. Datadog suggests this Linux check: grep -om1 -E 'avx512[_]?vbmi' /proc/cpuinfo. No output indicates no VBMI support.

Datadog also reports that in the OpenJDK 17.0.6 build it tested, the basic and URL decoders (Base64.getDecoder() and Base64.getUrlDecoder()) use the vulnerable path, while the MIME decoder does not. Libraries that implement their own decoding, or reject the value before calling the JDK decoder, can behave differently.

Affected Oracle Java SE builds, per Datadog’s table of Oracle’s statement:

LineAffectedFirst fixed
Java 1717.0.6 up to before 17.0.21.117.0.21.1+4
Java 21before 21.0.13.121.0.13.1+4
Java 25before 25.0.5.125.0.5.1+4
Java 27before 27.0.1.127.0.1.1+4

Where sources differ:

  • Java 8 and 11. Aikido says standard Java 8 and 11 are not affected, except Oracle’s Java SE 8 Enterprise Performance Pack build 8u511-perf. Cloudflare Radar lists Java SE 8u511 and 11.0.33 as affected by Oracle’s November update overall, with fixed builds 8u513 and 11.0.33.1, and the update covers multiple issues. Which Java 8 and 11 builds are affected by this specific CVE is not confirmed, so check Oracle’s advisory.
  • Eclipse Temurin. Aikido’s summary says Temurin has released fixes (17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1), but its table says there is no confirmed Temurin fix. Check the Temurin release page directly.
  • Amazon Corretto. Aikido lists fixed builds 17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2 and 27.0.1.1.4.
  • Other vendors. Aikido says Red Hat is expediting fixes. Fixed builds for Zulu, Microsoft and distribution packages are not confirmed in these sources, and build numbers may differ from Oracle’s.

Java runtimes bundled in applications, container images and appliances can also be affected, according to CISA, which notes they may not appear as separate software inventory entries.

What to do now

  1. Inventory every Java runtime, including JDKs bundled in third-party products, container base images and distribution packages (CISA). Check the version the running JVM reports, not only the installed package (Cloudflare Radar).
  2. Check which x86-64 hosts support AVX-512 VBMI, and prioritize internet-facing services that decode untrusted Base64 such as authentication headers, tokens or file uploads (Sophos).
  3. Apply the fixed build from your Java vendor. For Oracle Java SE these are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Rebuild and redeploy container images after updating a base image, and restart Java processes so they load the updated runtime (Datadog).
  4. If you cannot patch yet, Datadog says its tests confirmed two JVM options prevent the out-of-bounds writes:
    • -XX:-UseBASE64Intrinsics is the narrower option. Aikido warns that apps decoding a lot of Base64 may run slower.
    • -XX:UseAVX=2 works on x86-64 only. ARM64 JVMs do not recognize it and may fail to start, so do not put it in shared startup settings. It also affects other AVX-512 uses.

Sophos says neither Oracle nor the OpenJDK project has published a workaround and that it has not validated these options, so test them first. Sophos’s blog also relays Oracle’s general guidance to block the required network protocols, which may break functionality. Updating Java is the fix.

  1. Verify the result with jcmd <PID> VM.version and jcmd <PID> VM.flags -all, and confirm UseBASE64Intrinsics = false or UseAVX = 2 if you used a workaround (Datadog).
  2. If you cannot patch immediately, CISA also suggests restricting and validating Base64 input at the application boundary, enforcing input-size limits and limiting unauthenticated access. It also advises monitoring for unexpected JVM crashes and suspicious Java processes.
  3. Cloudflare reports six Managed Ruleset rules for this CVE on paid plans, with Log as the default action. It describes them as a compensating control, not a fix.

Sources