Skip to main content
CybersecurityVulnerability Management

Oracle to Patch 11 Java Flaws as OpenJDK RCE Vulnerability Emerges

Cluttered developer's workstation with laptop and monitor on a desk amidst papers and coffee cups in a bright office setting.
A reported OpenJDK vulnerability tracked as CVE-2026-114938 has been reported with a CVSS 4.0 score of 9.2, even as Oracle prepares security patches for 11 separate remotely exploitable Java SE flaws on Tuesday, November 17, 2026.

Oracle's November 17 Java SE patches

Oracle issued an advance security notice saying it will release updates for 11 Java SE vulnerabilities on November 17, 2026. The advance notice assigns those issues a maximum CVSS 3.1 score of 8.1 and says each may be exploited over a network without authentication. Oracle has not published the CVE identifiers for those 11 issues, nor has it disclosed the vulnerable components or the precise effects of exploitation.

Oracle cautions that the advance information may change before the full security advisory is published. The company’s ops.java site shows replacement builds listed as current releases; as of 16:59 UTC on the day of the notice, Oracle’s advance notice, release notes and download page still showed the earlier builds.

Affected Oracle products and versions

Oracle’s November security notice identifies specific Oracle products and builds that customers should stop using after the November 17 update and move to replacement releases. The notice names these affected builds:

  • 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’s release notes contain update guidance directing customers to stop using the listed builds and migrate to the corresponding replacement releases once the security update is applied.

The CVE-2026-114938 report and Java4Shell claim

Separately, security firm Calif posted on X that it discovered and reported a potentially critical OpenJDK vulnerability — which Calif calls “Java4Shell” — and said 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.

The public reports say CVE-2026-114938 affects OpenJDK 17.0.6 and later and has been assigned a CVSS 4.0 score of 9.2, but those details remain unconfirmed in official sources. The CVE record for CVE-2026-114938 was reported as reserved without a public description; no official advisory had specified the vulnerable component, the precise exploitation requirements, the affected version range, or whether a fix is available.

Security company watchTowr acknowledged the reports on X while cautioning that the technical details were still unverified. The OpenJDK Vulnerability Group had not published an advisory newer than October 24 at the time of the earlier review, and Oracle’s November notice covers Oracle products specifically without establishing the patch status of third-party OpenJDK distributions.

Oracle's release cadence and update guidance

Oracle began a monthly security patch cycle on May 28, 2026, adding targeted security releases between its quarterly Critical Patch Updates. Oracle’s Java security update plan, last updated September 10, listed November 17 as the next scheduled monthly release.

Because Oracle’s advance notice does not identify which components are vulnerable or what an attacker could accomplish by exploiting each of the 11 flaws, organizations are advised by Oracle to inventory deployed Java runtimes, identify internet-facing applications, and prepare to test and install the relevant vendor updates once they become available.

What this means for technologists, enterprises, and adversaries

  • Technologists and security teams: Inventory Java runtimes and internet-facing applications now, and be ready to test Oracle’s replacement builds once the full advisories are published. The advance notice states that the listed Oracle builds should be stopped and replaced after the November 17 update.
  • Oracle customers and enterprises: Follow Oracle’s release notes and migration guidance for the listed Java SE, GraalVM, GraalVM Enterprise Edition, and JavaFX builds; do not assume the OpenJDK CVE report is addressed by Oracle’s patches unless Oracle’s full advisory explicitly states that.
  • Adversaries and threat actors: Public reporting of an unconfirmed, high-scoring CVE and the promise of imminent technical details creates a temporal window in which defenders will be installing patches and attackers will be testing exploitability; the public record does not yet establish whether the reported CVE affects the Java runtime itself, a library, or an application-exposed feature.

Oracle’s scheduled updates and Calif’s promised disclosure leave critical details in flux: whether CVE-2026-114938 is one of Oracle’s 11 network-exploitable flaws, which specific builds or third-party distributions are vulnerable, and when fully verified technical guidance will be available. This is a developing story; we will update the report as Oracle publishes its full vulnerability advisory and as Calif or other parties release verified technical details.

Original story