CVE-2026-114938
Oracle Java SE and OpenJDK Base64 Decoder Heap Buffer Overflow Vulnerability (Java4Shell)
CVE-2026-114938, known as Java4Shell, is a high-severity heap-based buffer overflow in the Java runtime’s optimized Base64 decoder. An unauthenticated attacker who can supply Base64-encoded data to an affected application can make the runtime write past the end of a heap array; the Oracle Critical Security Patch Update Advisory – November 2026 states the flaw can result in takeover of the affected product. Exploitation requires an x86-64 processor with AVX-512 support and attacker-controlled input reaching the basic or URL decoder in java.util.Base64. Oracle rates it 8.1 (High) under CVSS v3.1; several public write-ups cite a preliminary CVSS v4.0 score of 9.2 (Critical) whose source is not named. No confirmed in-the-wild exploitation has been reported. Oracle credits Quang Luong of Calif.io and Albert Yang with the report.
Technical Details
The flaw is in HotSpot’s x86-64 Base64 decode intrinsic — the AVX-512 assembly routine the JIT compiler substitutes for the Java decoding loop in java.util.Base64 once a method runs hot. Handling the final partial block, the routine derives an output length from the block size and subtracts one byte per trailing = padding character, so a tail of one to three bytes yields a negative length. The store mask built from that value is read as a full-width mask, and the routine writes 62 or 63 bytes past the end of the destination array on the Java heap, corrupting the object that follows. Oracle classifies the affected component as Compiler, consistent with the bug living in JIT-generated code rather than in the class library.
Weakness: CWE-122, Heap-based Buffer Overflow
Attack vector: Network — any application that Base64-decodes attacker-supplied data
Authentication: None
User interaction: None
Impact: High confidentiality, integrity and availability impact; Oracle describes the outcome as takeover
CVSS v3.1: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H (8.1, High)
Internet exposure is not required; any internal service that decodes untrusted Base64 reaches the same path. Runtimes on CPUs without AVX-512, including ARM64, do not.
Stop Guessing, Start Proving
Affected Versions & Patch
Affected
- Oracle Java SE: 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3
- Oracle GraalVM for JDK: 17.0.21.0.3, 21.0.13.0.3
- Oracle GraalVM Enterprise Edition: 21.3.20.0.3
- OpenJDK builds: 17.0.6 through versions before 17.0.21.1; Java 21 before 21.0.13.1; Java 25 before 25.0.5.1; Java 27 before 27.0.1.1. [VERIFY: OpenJDK ranges come from independent analysis; the OpenJDK Vulnerability Group has published no advisory]
- Downstream distributions that ship these builds — including Eclipse Temurin, Amazon Corretto and the Red Hat build of OpenJDK — and JREs bundled inside container images and appliance firmware, which release on their own schedules.
Fixed
- Oracle: the builds released in the Oracle Critical Security Patch Update Advisory – November 2026, published November 17, 2026.
Mitigations
Oracle’s Critical Security Patch Update advisory publishes no workaround for this vulnerability; the fix is the patched build. Independent analysis reports that starting the JVM with the following HotSpot flag disables the vulnerable intrinsic:
-XX:-UseBASE64Intrinsics
That flag removes the optimized decoder and its performance benefit. On x86-64 only, -XX:UseAVX=2 also keeps the JVM off the AVX-512 path; ARM64 JVMs fail to start with it. Verify a running process with jcmd <PID> VM.flags -all. Neither flag is published by Oracle as a supported workaround, and neither is a fix.
Timeline
- October 22, 2026: CVE-2026-114938 was reserved.
- November 17, 2026: Oracle published the Critical Security Patch Update Advisory – November 2026, which includes the fix.
- November 17, 2026: The CVE record was published, with Oracle as the assigning CNA.
- November 17, 2026: Independent technical analyses of the Base64 decoder overflow were published.
