Oracle prepares Java security releases for 11 remotely exploitable flaws

Oracle is preparing security updates for 11 vulnerabilities in Java SE on November 17, 2026. Oracle says every flaw can be exploited remotely without authentication, and the highest published CVSS 3.1 score is 8.1. At the same time, researchers have reported an unverified potentially critical OpenJDK remote-code-execution issue, CVE-2026-114938, creating an additional concern for organisations running Java workloads.
Oracle has not yet published CVE identifiers, affected components or exploitation outcomes for the 11 Java SE flaws. Remote, unauthenticated exploitability does not establish that each issue enables remote code execution, nor does it mean every application using an affected runtime is directly reachable by an attacker.
Replacement builds listed for Java releases
Oracle advises customers to stop using the current Java 8, 11, 17, 21, 25 and 27 builds after the November security update and move to the corresponding replacement releases. The releases listed on ops.java are Java 8u513, Java 11.0.33.1, Java 17.0.21.1, Java 21.0.13.1, Java 25.0.5.1 and Java 27.0.1.1.
The advance notice identifies Oracle Java SE versions 8u511, 8u511-perf, 11.0.33, 17.0.21, 21.0.13, 25.0.5 and 27.0.1 as affected. It also includes Oracle GraalVM for JDK 17.0.21 and 21.0.13, Oracle GraalVM Enterprise Edition 21.3.20.0.3, and Oracle JavaFX versions 21.0.13, 25.0.5 and 27.0.1.
Reported OpenJDK RCE lacks confirmed technical details
Security firm Calif said it discovered and reported CVE-2026-114938, which it calls Java4Shell, and planned to publish technical details after Oracle released a patch. The reported issue has been assigned a CVSS 4.0 score of 9.2 and is said to affect OpenJDK 17.0.6 and later, but these details have not been confirmed publicly.
watchTowr acknowledged the reports while warning that technical information remained unverified. The CVE record is reserved without a public description, and no official advisory has identified the vulnerable component, precise exploitation requirements, full affected-version range or an available fix.
Oracle update status does not settle third-party OpenJDK exposure
There is no evidence that CVE-2026-114938 is one of Oracle’s 11 announced vulnerabilities. Oracle’s notice applies to Oracle products and does not establish patch availability for third-party OpenJDK distributions. At the time of review, the OpenJDK Vulnerability Group had not issued an advisory newer than October 24.
Oracle began its monthly Java security patch cycle on May 28, supplementing quarterly Critical Patch Updates with targeted releases. Its update plan, last revised on September 10, named November 17 as the next monthly release date. Until vendors publish complete advisories, teams cannot determine from the reported CVE alone whether a particular deployment is exposed or which update addresses it.
Actions for Java operators
Organisations should inventory deployed Java runtimes, identify applications exposed to the internet and map each installation to its distribution vendor. They should then prepare testing and change windows for the relevant replacement builds, while monitoring Oracle and OpenJDK advisories for confirmed scope. This approach gives security and operations teams a practical basis for deploying verified updates without assuming that the unconfirmed OpenJDK report applies to every Java environment.

