Oracle Readies 11 Java Patches as Unconfirmed OpenJDK Flaw 'Java4Shell' Raises Alarm
Oracle is preparing security patches for 11 vulnerabilities in Java SE, due on Tuesday, 17 November 2026. Its advance notice says all 11 may be exploited over a network without credentials, with a top CVSS 3.1 score of 8.1. Oracle has not released CVE identifiers, affected components or the specific impact of each flaw, and warns the details may change before the full advisory.
Separately, reports describe an OpenJDK flaw tracked as CVE-2026-114938 and nicknamed Java4Shell by Calif, the firm that says it found and reported it. It has reportedly been given a CVSS 4.0 score of 9.2 and affects OpenJDK 17.0.6 and later. Calif says the flaw leaked and plans to publish technical details after Oracle's patch. watchTowr has cautioned that the details are unconfirmed, and the CVE record is still reserved with no public description. There is no evidence yet that this flaw is among Oracle's 11.
Analyses by Upwind and Equixly of the OpenJDK source point to a bug in Java's AVX-512 Base64 decoder. The code only runs on x86-64 processors with AVX-512 VBMI support, when untrusted data reaches the basic or URL decoder in java.util.Base64. ARM servers do not run it. It is present in Java 17.0.6 and later, and in Java 21, 25 and 27, but not standard Java 8 or 11. The firms think a crash is the likely outcome rather than code execution, because the overflowed bytes are fixed, though neither reproduced the overflow on AVX-512 hardware.
Both firms named two JVM options as possible stopgaps: -XX:-UseBASE64Intrinsics and -XX:UseAVX=2, the latter of which can slow other work. No vendor has confirmed either. Oracle advises customers to stop using its current Java 8, 11, 17, 21, 25 and 27 builds after the update and move to the replacement releases. Its notice does not establish the patch status of third-party OpenJDK distributions.
Why it matters
Teams cannot tell from the CVE alone whether they are exposed, so patch priority has to rest on inventory: which Java versions, which CPUs, and which apps pass untrusted data to Base64 decoding. The gap between a 9.2 score and a likely crash shows why severity ratings should not be accepted without checking the details. Businesses using third-party OpenJDK builds cannot assume Oracle's patch timing applies to them.
What to do
- Inventory all Java runtimes and note which are 17.0.6 or later, or Java 21, 25 or 27.
- Identify internet-facing Java applications that decode untrusted Base64 input.
- Check whether servers are x86-64 with AVX-512 VBMI support, since ARM servers do not run the flawed code.
- Test the replacement builds Oracle lists for 17 November and deploy them once available.