Oracle is preparing to release security patches for 11 vulnerabilities in Java SE on Tuesday, November 17, 2026, all of which may be exploited remotely without authentication, as separate reports warn of a potentially critical remote code execution (RCE) flaw affecting OpenJDK.
The 11 vulnerabilities carry a maximum CVSS 3.1 severity score of 8.1, according to Oracle's advance security notice. The company has not disclosed their CVE identifiers, affected components, or the individual consequences of exploitation.
The separate OpenJDK vulnerability, tracked as CVE-2026-114938, has reportedly been assigned a CVSS 4.0 score of 9.2 and affects OpenJDK 17.0.6 and later. However, those details remain unconfirmed, and there is no evidence yet that the reported flaw is among the 11 vulnerabilities Oracle plans to patch.
Security firm Calif said in a post on X that it discovered and reported the flaw, which it calls Java4Shell, and that the vulnerability had leaked. Calif said it would publish technical details by 1 p.m. Pacific time on November 17, after Oracle releases a patch.
Security company watchTowr acknowledged the reports in a post on X, but cautioned that the technical details were still unconfirmed.
Separate analyses of the OpenJDK source code by security companies Upwind and Equixly point to a flaw in Java's Base64 decoder whose likely result is a crash of the Java virtual machine (JVM) rather than code execution.
The vulnerability's CVE record remains reserved without a public description. No official advisory has specified the vulnerable component, precise exploitation requirements, affected version range, or the availability of a fix.
Oracle's ops.java site now lists the replacement builds below as its current releases. Oracle's advance notice, release notes and download page still showed the earlier builds as of 16:59 UTC.
Oracle Prepares Java Security Updates
Oracle advises customers to stop using its current builds of Java 8, 11, 17, 21, 25, and 27 after the November 17 security update and move to the corresponding replacement releases.
The company's Java release notes contain the update guidance, while ops.java lists the following planned builds:
| Java line | Current build | Planned build |
|---|---|---|
| Java 8 |
8u511 b33
|
8u513
|
| Java 11 |
11.0.33.0.3
|
11.0.33.1
|
| Java 17 |
17.0.21.0.3
|
17.0.21.1
|
| Java 21 |
21.0.13.0.3
|
21.0.13.1
|
| Java 25 |
25.0.5.0.3
|
25.0.5.1
|
| Java 27 |
27.0.1.0.3
|
27.0.1.1
|
The November security notice identifies the following affected Oracle products and versions:
- Oracle Java SE: 8u511, 8u511-perf, 11.0.33, 17.0.21, 21.0.13, 25.0.5, and 27.0.1.
- Oracle GraalVM for JDK: 17.0.21 and 21.0.13.
- Oracle GraalVM Enterprise Edition: 21.3.20.0.3.
- Oracle JavaFX: 21.0.13, 25.0.5, and 27.0.1.
Oracle says all 11 Java SE vulnerabilities may be exploited over a network without requiring credentials. That does not necessarily mean they all allow remote code execution or that every application running an affected Java version can be attacked directly.
The advance notice does not identify the vulnerable Java components or specify what an attacker could accomplish by exploiting each flaw.
Oracle also warns that the information may change before the complete security advisory is published.
Critical OpenJDK RCE Report Remains Unverified
The reported CVE-2026-114938 vulnerability introduces a separate concern for organizations operating Java applications, particularly those exposed to the internet.
However, the public information does not establish whether the flaw affects the Java runtime itself, a particular library, or functionality that applications must expose for exploitation to succeed.
However, Oracle's notice and the OpenJDK advisories do not establish whether the flaw affects the Java runtime itself, a particular library, or functionality that applications must expose for exploitation to succeed.
Upwind said in a technical analysis that its reading of the OpenJDK source points to a flaw in Java's AVX-512 Base64 decoder, and Equixly reached the same finding in a separate analysis. The flawed code runs only on x86-64 processors with AVX-512 VBMI support, when untrusted data reaches the basic or URL decoder of java.util.Base64. ARM servers do not run it.
The code is in Java 17.0.6 and later and in Java 21, 25 and 27, but not in standard Java 8 or 11. A crash is the likely result because the bytes written past the buffer are fixed and not chosen by the attacker. Neither firm reported reproducing the overflow on AVX-512 hardware.
Oracle's 8u371-perf release notes show that its Java 8 Enterprise Performance Pack added a "Base64 Decoding optimization for x86 using AVX-512". Neither firm said whether the Performance Pack is affected.
Both firms named two JVM options as stopgaps to keep the flawed code from running: -XX:-UseBASE64Intrinsics, which turns off the Base64 intrinsics, and -XX:UseAVX=2, which turns off all AVX-512 code paths and can slow other work. Neither option has been confirmed by a vendor for this flaw, the firms said.
Oracle's November notice covers Oracle products and does not establish the patch status of third-party OpenJDK distributions.
The OpenJDK Vulnerability Group, which coordinates security disclosures affecting OpenJDK source code, had not published an advisory newer than October 24 at the time of the earlier review.
Until official details are available, organizations cannot determine from the reported CVE alone whether their Java deployments are vulnerable or which specific update addresses the issue.
Oracle began a monthly security patch cycle on May 28, introducing targeted security releases between its quarterly Critical Patch Updates.
Its Java security update plan, last updated September 10, identified November 17 as the next scheduled monthly release.
Organizations should inventory deployed Java runtimes, identify internet-facing applications, and prepare to test and install the relevant vendor updates once they become available.
This is a developing story. We will update this article as Oracle publishes its full vulnerability advisory and additional verified details about CVE-2026-114938, affected versions, and available patches emerge.




