DEV Community

Madhurima Kommuru
Madhurima Kommuru

Posted on Edited on

Java4Shell (CVE-2026-114938): What It Is and How to Fix It

On November 17, 2026, a critical memory-corruption flaw in OpenJDK's Base64 decoder was disclosed: CVE-2026-114938, nicknamed Java4Shell (CVSS 4.0: 9.2, Critical).

What is it?

The HotSpot JVM compiles Base64 decoding into an optimized AVX-512 VBMI intrinsic. A flaw in that path causes a heap out-of-bounds write when it processes crafted input. That can lead to memory disclosure, a crash, or, in the worst case, remote code execution. It is a JVM bug, not a bug in your application code.

how the attack works, what goes wrong in memory, and how to mitigate

Who is affected?

  • Unpatched builds of OpenJDK 17.0.6+ and the 21, 25 and 27, including affected vendor distributions.
  • x86-64 CPUs with AVX-512 VBMI (Intel Ice Lake+, AMD Zen 4+)
  • Not affected: ARM64, or x86-64 CPUs without AVX-512 VBMI
  • Java based products such as Keycloak, Jira, Confluence and Jenkins may be affected, depending on their bundled or configured java runtime.

How to fix it

  1. Permanent fix: upgrade to a Java build explicitly confirmed by your runtime vendor as containing the fix for CVE-2026-114938.Verify the exact build number and patch status against the vendor's security advisory. Oracle released security updates on November 17,2026, and other OpenJDK distributors are issuing their own patched builds.
  2. Interim workaround: add -XX:-UseBASE64Intrinsics and restart the JVM.
java -XX:-UseBASE64Intrinsics -jar your-app.jar
Enter fullscreen mode Exit fullscreen mode

Prioritize internet-facing apps that process authentication. RCE is rated difficult to exploit, but patch promptly.

Decision Flow:

References

By Madhurima Kommuru

Top comments (0)