Skip to content

Java4Shell: a JVM bug lets attackers skip login on Jenkins and Jira

A heap overflow in the JVM's Base64 decoder gives pre-auth code execution on default installs of Jenkins, Jira, Confluence and Keycloak. Patching the app will not fix it, only patching the JDK will.

Source: Horizon3.ai

CVE-2026-114938, now being called Java4Shell, is a heap buffer overflow in the hardware-accelerated Base64 decoder built into OpenJDK’s HotSpot virtual machine. It only triggers on x86-64 CPUs with AVX-512 VBMI support, once the JIT has compiled the decoder into its fast assembly routine. Security researchers showed pre-auth remote code execution against default configurations of Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate, simply by sending malformed Base64 input to any endpoint that decodes it.

Oracle shipped fixed builds on 17 November: Java SE 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1, along with matching OpenJDK and GraalVM updates. Oracle rates the bug 8.1 under CVSS 3.1; independent researchers put it at 9.2 under CVSS 4.0. There is no official workaround, but starting the JVM with -XX:-UseBASE64Intrinsics disables the vulnerable routine as an unsupported stopgap.

java -XX:-UseBASE64Intrinsics -jar your-app.jar

Why it matters: this sits in the JVM itself, not in any one application, so patching Jira or Jenkins at the application layer does nothing. You have to update the JDK underneath them and restart. If your stack runs Jenkins, Keycloak, Confluence or similar on affected hardware, check your Java version today.

The caveat: no in-the-wild exploitation was confirmed as of 18 November, but a working proof of concept was built within hours of disclosure, so that gap will not last.

Share

Related reading

More from The Wire

All briefs