The OpenJDK and Oracle advisories dated November 17, 2026, identify Java4Shell (CVE-2026-114938), but the affected scope is specific to each runtime. OpenJDK marks release lines 17, 21, 25 and 27 as affected; Oracle lists exact builds for its Java SE and GraalVM products. Calif describes a hardware requirement of x86-64 with AVX-512 VBMI and recommends upgrading, with two temporary JVM flags for administrators who need a stopgap.
What Java4Shell affects
Java4Shell is a memory-corruption flaw in OpenJDK HotSpot’s accelerated Base64 decoder. Calif says malformed padded input can trigger an out-of-bounds write in the x86-64 decoding path, which OpenJDK classifies under hotspot/compiler. Calif identifies an x86-64 processor with AVX-512 VBMI support as a hardware condition for the vulnerable path and says ARM64 CPUs are not affected. Calif’s technical account and the OpenJDK advisory describe the flaw and its scope.
Which OpenJDK lines and Oracle builds are listed?
The OpenJDK advisory marks release lines 17, 21, 25 and 27 as affected by CVE-2026-114938. Oracle’s risk matrix lists affected builds for its own products; those entries should be matched to the Oracle runtime in use, not applied to another distribution. OpenJDK’s CVE-specific entry and Oracle’s Java risk matrix list:
| Runtime or product | Affected release lines or builds listed |
| OpenJDK | 17, 21, 25 and 27 |
| 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 and 21.0.13.0.3 |
| Oracle GraalVM Enterprise Edition | 21.3.20.0.3 |
The advisories also give severity scores using different CVSS versions: OpenJDK and Oracle assign 8.1 under CVSS v3.1, while Calif gives 9.2 under CVSS v4.0. OpenJDK · Oracle · Calif
Upgrade guidance and temporary mitigations
OpenJDK recommends upgrading as soon as possible. Calif also recommends upgrading and describes two temporary JVM options: -XX:-UseBASE64Intrinsics disables the accelerated Base64 operations, while -XX:UseAVX=2 disables AVX-512 on x86-64. Calif warns that OpenJDK on ARM does not recognize the second flag and will fail to start with it. These flags are temporary measures, not replacements for the relevant vendor update. OpenJDK · Calif
Match the advisory to the runtime distribution and exact build before choosing a mitigation; a Java release-line number alone does not identify every product’s affected build.
How Calif describes the discovery
Calif researcher Quang Luong says he directed Codex to inspect selected OpenJDK code areas, including the JIT compiler and intrinsics, before the Base64 issue surfaced. His account describes researcher-directed code review, rather than an autonomous discovery by the AI tool. Luong’s account