November 18, 2026 / news

Java4Shell (CVE-2026-114938): OpenJDK Base64 Decoder Bug Gives Pre-Auth RCE on Jira, Jenkins, Keycloak

Out-of-bounds write in the AVX-512 Base64 decoder of OpenJDK 17.0.6+ (CVE-2026-114938, CVSS 9.2) allows pre-auth RCE on six Java apps. Fixes shipped November 17; otherwise disable the intrinsic.

Title: Java4Shell: Out-of-Bounds Write in OpenJDK’s AVX-512 Base64 Decoder Enables Unauthenticated RCE — Patch or Disable -XX:-UseBASE64Intrinsics

Summary: Calif has disclosed CVE-2026-114938 (“Java4Shell”), a memory-corruption bug in the x86-64 Base64 decoder intrinsic of OpenJDK’s HotSpot JIT, scored 9.2 out of 10 under CVSS 4.0. On processors that support AVX-512 VBMI (Intel Xeon Ice Lake through Granite Rapids, AMD Zen 4 or newer; ARM64 is unaffected), a malformed Base64 string of 64 A characters followed by a stray = (128 A + = on older OpenJDK 17 builds) makes the decoder compute a negative output length and write 62 bytes past the end of its 50-byte result buffer. Java rejects the input, but only after the write — and the write consists of fixed bytes, so Calif turned the fixed spill into a chosen-value linear write by grooming the heap to enlarge a neighboring array, then built a heap-disclosure primitive it calls JavaBleed, and from there reached code execution. In its initial testing, the exploit chain ran code without authentication on six applications in default configurations: Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate. Five more — Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker — fell after authentication, and sample apps on Apache Struts and Spring Boot also fell. Because the vulnerable code is only reached after the JIT compiles the decoder for hot paths, the same container image can be exploitable on one server and not on another; on Linux, all four CPU flags avx512f, avx512bw, avx512vbmi and bmi2 must appear in grep -m1 '^flags' /proc/cpuinfo output. Anything built from OpenJDK 17.0.6 or newer is affected, including Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, Red Hat’s OpenJDK builds and Oracle Java SE (including the 8u511b33-perf Performance Pack). The OpenJDK project released a security advisory and Oracle shipped its patch at 1:00 p.m. PT on November 17, 2026; per The Hacker News, Amazon has already fixed Corretto (17.0.21.1.2 and equivalent builds), Azul fixed Zulu, and SAP shipped SapMachine updates, while Red Hat had no fixes for RHEL or its OpenJDK builds when checked on November 18. Until you can update and restart services (rebuilding container images so running processes actually pick up the new build), start the JVM with -XX:-UseBASE64Intrinsics to disable the vulnerable code, or -XX:UseAVX=2 to disable AVX-512 entirely on x86-64 hosts — on ARM64 Java the latter flag prevents startup. There is no evidence yet of exploitation in the wild: the flaw was not in CISA’s KEV catalog when The Hacker News checked on November 18, and Canada’s Cyber Centre said it was not aware of any attacks.

References:

← All news