Researchers Report Java4Shell RCE in OpenJDK Base64 Decoder; Patches Available

Summary
Researchers report CVE-2026-114938, an OpenJDK Base64 decoder heap overflow affecting specified Java builds on x86-64 AVX-512 VBMI systems. Fixes are available; no in-the-wild exploitation was confirmed as of Nov. 18, 2026.
Key points
- Malformed Base64 padding can trigger a heap out-of-bounds write in HotSpot’s AVX-512 decoder after JIT optimization; researchers chained it into heap disclosure and remote code execution.
- The flaw affects specified OpenJDK-based Java 17, 21, 25 and 27 builds, plus Oracle Java SE 8 Enterprise Performance Pack, only on x86-64 systems with AVX-512 VBMI.
- Researchers demonstrated pre-authentication RCE in default installations of Jira, Confluence, Jenkins, Keycloak, JFrog Artifactory and PingFederate; other demonstrated application chains require authentication.
- No in-the-wild exploitation was confirmed as of Nov. 18, 2026. A safe trigger PoC is public, while product-specific weaponized exploits remain private.
- Oracle and OpenJDK released fixes on Nov. 17, 2026; downstream distributions have differing release statuses, so teams should verify their vendor’s fixed build.
- Patching and restarting affected JVMs is the complete fix. Until then, researchers recommend restarting with -XX:-UseBASE64Intrinsics; bundled runtimes and container images also need updating.
Article Details
- Vulnerability Types
- Heap out-of-bounds write (memory corruption) in OpenJDK’s AVX-512 VBMI Base64 decoder
- Padding-handling error that can cause a 64-byte vector write past the destination array
- Severity
- CVSS v3.1 8.1 (High), from Oracle and the OpenJDK Vulnerability Group; Calif rates it 9.2 (Critical) under CVSS v4.0.
- Affected Versions
- OpenJDK-based Java 17: 17.0.6 through 17.0.21.0.3
- OpenJDK-based Java 21: 21.0.13.0.3 and earlier
- OpenJDK-based Java 25: 25.0.5.0.3 and earlier
- OpenJDK-based Java 27: 27.0.1.0.3 and earlier
- Oracle Java SE 8 Enterprise Performance Pack: 8u511b33-perf
- Oracle GraalVM for JDK: 17.0.21.0.3 and 21.0.13.0.3
- Oracle GraalVM Enterprise Edition: 21.3.20.0.3
- Exploitation Status
- not_reported
- Exploit Availability
- public_poc
- Patch Status
- available
- Workarounds
- Restart affected JVMs with -XX:-UseBASE64Intrinsics until a fixed build is installed.
- On x86-64 hosts, use -XX:UseAVX=2 to disable AVX-512; the article notes this is not suitable for ARM systems.
- Restrict and validate Base64 input at the application boundary, enforce input-size limits, and limit unauthenticated access.
MITRE ATT&CK
T1190 · Exploit Public-Facing ApplicationThe article maps server-side Java4Shell exploit chains against exposed Java applications to Exploit Public-Facing Application.T1203 · Exploitation for Client ExecutionThe article maps the client-side scenario, in which a Java program is compromised after opening a TLS connection to a malicious server, to Exploitation for Client Execution.
CVE
People
Albert YangCredited in Oracle’s November 2026 advisory for Java4Shell; the article does not specify his particular contribution.Jenish RakholiyaCredited with improvements to the Java4Shell exploit.Quang LuongCalif researcher credited with discovering Java4Shell; the article says he found the bug and developed a first working exploit.samczsunShared a client-side Java4Shell exploit, according to the article.
Vendors
AmazonHotSpot JVM (hotspot/compiler) and distributions built from it, including Oracle Java SE, Oracle GraalVM, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, andAzulincluding Oracle Java SE, Oracle GraalVM, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, and Red Hat build of OpenJDKOracleCalif published its write-up on November 17, 2026, the same day Oracle and the OpenJDK project released fixes, and reported pre-authentication Remote Code Execution (RCE) against default installs of Jira, Confluence,Red HatCorretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, and Red Hat build of OpenJDK
Products
Amazon CorrettoJVM (hotspot/compiler) and distributions built from it, including Oracle Java SE, Oracle GraalVM, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, and RedAzul Zuluincluding Oracle Java SE, Oracle GraalVM, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, and Red Hat build of OpenJDKHotSpot JVMAffected Products OpenJDK HotSpot JVM (hotspot/compiler) and distributions built from it, including Oracle Java SE, Oracle GraalVM, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoftOpenJDKJava4Shell (CVE-2026-114938) is a memory corruption vulnerability in OpenJDK that lets malformed Base64 input write past the end of a heap array on servers with AVX-512 VBMI processors.Oracle GraalVMOpenJDK HotSpot JVM (hotspot/compiler) and distributions built from it, including Oracle Java SE, Oracle GraalVM, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAPOracle Java SEWho is affected: Unpatched Java 17.0.6 and later, the Java 21, 25, and 27 lines, and Oracle Java SE 8u511b33-perf, on x86-64 processors with AVX-512 VBMI (Vector Byte Manipulation Instructions); ARM64 hosts and standard
