Protect.Computer
NEWS

Oracle Patches Java Flaw CVE-2026-114938 (Java4Shell)

· 2 min read · Device safety Network safety
Oracle Patches Java Flaw CVE-2026-114938 (Java4Shell)

Oracle’s November 17 Critical Security Patch Update lists CVE-2026-114938 in its Java SE risk matrix: a flaw in the Compiler component that Oracle rates 8.1 (CVSS 3.1), exploitable over the network without credentials, with high attack complexity. Oracle’s acknowledgments credit Quang Luong of Calif.io for it. Calif, the security firm behind the find, nicknamed it “Java4Shell” and said the details had leaked before the patch; early reports gave it a 9.2 under CVSS 4.0 and called it remote code execution.

The public technical analysis points to something narrower. According to The Hacker News, Upwind and Equixly both read the OpenJDK source and place the bug in the AVX-512 accelerated Base64 decoder used by java.util.Base64. Equixly describes a crafted input that writes 62 or 63 bytes past the end of a heap buffer, but says the decoder, not the attacker, chooses those bytes, so the realistic result is a JVM crash rather than code execution. Per The Hacker News, neither firm reported reproducing the overflow on AVX-512 hardware. Equixly states there are no reports of exploitation in the wild and no public proof-of-concept as of November 17, and that the CVE record was still reserved. Oracle’s own advisory does not describe the mechanism.

How to check if you’re affected

Affected versions, according to Oracle’s risk matrix for CVE-2026-114938, are Oracle Java SE 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3, plus Oracle GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3 and GraalVM Enterprise Edition 21.3.20.0.3. Equixly says standard Java 8 and 11 have no Base64 decode intrinsic and are not affected, and that the vulnerable path only runs on x86-64 CPUs with AVX-512 VBMI (Intel Ice Lake or later, AMD Zen 4 or later). ARM servers such as AWS Graviton and Apple Silicon are not affected, according to Equixly.

  • Find the runtime you actually use. Equixly notes that java -version reports only the first Java on the path and many applications bundle their own JDK. It suggests jcmd <PID> VM.version on running processes.
  • Check the CPU. On Linux, Equixly says grep -c avx512vbmi /proc/cpuinfo returns 0 on hosts that cannot reach the vulnerable path.
  • Update, then restart. The Hacker News lists Oracle’s planned replacement builds (Java 8 8u513, 11 11.0.33.1, 17 17.0.21.1, 21 21.0.13.1, 25 25.0.5.1, 27 27.0.1.1) and reported that Oracle’s download page still showed the earlier builds as of 16:59 UTC, so confirm on Oracle’s pages before relying on that list. Equixly adds that a running JVM does not change when files are replaced on disk, and that container images need rebuilding.
  • Third-party distributions and bundled JDKs. The Hacker News says Oracle’s notice does not establish the patch status of third-party OpenJDK builds; check each vendor’s advisory.
  • Stopgaps, if you cannot patch yet. Equixly and Upwind (as reported by The Hacker News) name two JVM options, -XX:-UseBASE64Intrinsics and -XX:UseAVX=2 (the second can slow other work). No vendor has confirmed either for this flaw, so test before rolling out.

At the time of writing we had not read Calif’s own technical write-up, which it said it would publish after Oracle’s release.

Sources

Related reading