Cybersecurity Research

Java4Shell: Critical OpenJDK Flaw Lets Attackers Run Code on Servers Without a Login

Wiz Research · 18 Nov 2026
Key Takeaway Find every Java application you run, especially internet-facing ones like Jira, Confluence and Jenkins, and update OpenJDK now or apply the vendor workaround.

Wiz Research has detailed a critical flaw in OpenJDK, tracked as CVE-2026-114938 and nicknamed "Java4Shell". It scores 9.2 on the CVSS v4.0 scale. Security firm Calif discovered and disclosed it, and details emerged on 17 November 2026. A remote attacker with no login can corrupt heap memory on an affected system, which can lead to remote code execution.

The bug sits in optimised code that the Java Virtual Machine uses to decode Base64 data on supported x86-64 processors. That code miscalculates the output size when the input has an unexpected number of trailing padding characters. The result is a write past the end of a memory buffer, which can overwrite neighbouring object data. Wiz says it showed remote exploitation is feasible against common Java applications including Jenkins, Confluence and Apache Tomcat.

Wiz notes that exploitation is possible with AI assistance but is not trivial. Its own AI research tool built a proof-of-concept within two hours, even before full details were public. Generalising an exploit across arbitrary targets is hard, so attackers are likely to go after popular packaged applications where builds and memory layouts repeat. Determined attackers may also tailor exploits to home-grown applications.

The flaw affects OpenJDK 17.0.6 and later, plus downstream distributions such as Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, Red Hat OpenJDK and certain Oracle Java SE builds. It applies only on x86-64 hardware with AVX-512 VBMI support, including Intel Xeon (Ice Lake and newer) and AMD EPYC/Ryzen (Zen 4 or newer). ARM64 is unaffected. Wiz says a web application firewall may block some attempts but cannot reliably cover every code path, so upgrading OpenJDK is the best fix.

Why it matters

Many businesses treat the Java runtime as invisible plumbing and patch only the applications on top, yet this flaw lives in the runtime itself, so a fully updated Jira or Jenkins can still be exposed. It also undercuts reliance on web application firewalls, since the vulnerable code can be reached through many input paths and custom-built applications are the least likely to be covered. Teams must now inventory both the JDK version and the underlying CPU capability to know whether they are truly at risk.

What to do

  • Identify all systems running OpenJDK 17.0.6 or later on AVX-512 capable x86-64 hardware.
  • Apply the official patches released on 17 November 2026 or update to your vendor's fixed OpenJDK build.
  • Add the JVM flag -XX:-UseBASE64Intrinsics as a workaround if you cannot patch yet, and expect some performance impact.
  • Restrict public access to internet-facing management portals such as Jira, Jenkins and Keycloak until they are patched.
OpenJDK Java4Shell CVE-2026-114938 remote code execution patch management

Summarised by CISO AI from Wiz Research, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.