Skip to main content
All incident reports
Incident report

Oracle readies Java patches for 11 flaws as separate OpenJDK flaw report stays unverified

Oracle's advance notice schedules Java SE security updates for 17 November, covering 11 flaws that can be exploited over a network without credentials. A separate report of a critical remote code execution flaw in OpenJDK, called Java4Shell by the firm that says it found it, remains unconfirmed.

· First published

The short version

  • The patch batch. Oracle's advance security notice lists 11 Java SE vulnerabilities, all of which may be exploited over a network without authentication, with a maximum CVSS 3.1 score of 8.1. Oracle has not disclosed their CVE identifiers, affected components or the consequences of each.
  • The unconfirmed flaw. A separate report concerns CVE-2026-114938, said to score 9.2 under CVSS 4.0 and to affect OpenJDK 17.0.6 and later. The CVE record is reserved with no public description, and no source establishes that it is among the 11 flaws being patched.
  • What the code reviews found. Upwind and Equixly both read the OpenJDK source as pointing to a flaw in Java's AVX-512 Base64 decoder, reachable only on certain x86-64 hardware. They expect a Java virtual machine crash rather than code execution, and neither reported reproducing it.
  • Who is affected. Oracle names Java SE 8u511, 11.0.33, 17.0.21, 21.0.13, 25.0.5 and 27.0.1, plus GraalVM and JavaFX builds, and advises moving to replacement releases after the update. It says nothing about third-party OpenJDK distributions.

Timeline

DateEvent
28 MayOracle starts a monthly Java security patch cycle, adding targeted releases between its quarterly Critical Patch Updates.
10 SeptemberOracle's Java security update plan, last revised on this date, names 17 November as the next monthly release.
24 OctoberAt the time of the earlier review, the OpenJDK Vulnerability Group had published no advisory newer than this date.
17 NovemberOracle's Java SE security update is scheduled; Calif says it will publish technical details on the reported OpenJDK flaw after Oracle releases a patch.

Oracle's November Java update

Oracle's advance security notice lists 11 Java SE vulnerabilities, all reachable over a network without credentials, with a maximum CVSS 3.1 score of 8.1. The notice does not give CVE identifiers, vulnerable components or what an attacker could achieve with each flaw, and Oracle warns the information may change before the full advisory appears. Network reachability does not by itself mean every flaw allows remote code execution.

The notice names Java SE 8u511, 11.0.33, 17.0.21, 21.0.13, 25.0.5 and 27.0.1, along with GraalVM for JDK 17.0.21 and 21.0.13, GraalVM Enterprise Edition 21.3.20.0.3 and JavaFX 21.0.13, 25.0.5 and 27.0.1. Oracle advises customers to stop using current builds after the update and move to the replacement releases; for Java 17 that is 17.0.21.1, with the rest listed on Oracle's ops.java site.

As of 16:59 UTC on the publication day, Oracle's advance notice, release notes and download page still showed the earlier builds, and the article was written while the update was still due rather than shipped.

The unconfirmed OpenJDK flaw

A separate report concerns CVE-2026-114938, said to carry a CVSS 4.0 score of 9.2 and to affect OpenJDK 17.0.6 and later. Calif said in a post on X that it discovered and reported the flaw, calls it Java4Shell, said the vulnerability had leaked, and planned to publish technical details after Oracle's patch. WatchTowr acknowledged the reports but said the details were unconfirmed.

Source code reviews by Upwind and Equixly point instead to a flaw in Java's AVX-512 Base64 decoder. The 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. It is present in Java 17.0.6 and later and in Java 21, 25 and 27, but not in standard Java 8 or 11, and ARM servers do not run it.

Both firms expect a crash of the Java virtual machine rather than code execution, because the bytes written past the buffer are fixed and not chosen by the attacker, and neither reported reproducing the overflow on AVX-512 hardware. They named two JVM options as stopgaps, -XX:-UseBASE64Intrinsics and -XX:UseAVX=2, said neither is vendor-confirmed, and warned the second slows other work. Neither firm said whether Oracle's Java 8 Enterprise Performance Pack, which added an AVX-512 Base64 optimisation, is affected.

Where the record stands

No advisory yet specifies the vulnerable component, exploitation requirements, the full affected version range or a fix for CVE-2026-114938. Oracle's notice covers Oracle products and does not establish the patch status of third-party OpenJDK distributions. The article states there is no evidence that the reported OpenJDK flaw is among the 11 vulnerabilities in Oracle's update.

What is not known yet

  • Whether CVE-2026-114938 is one of the 11 Java SE flaws Oracle is patching, or a separate issue.
  • What each of the 11 flaws lets an attacker do, since Oracle has not named the affected components or their individual impact.
  • Whether the Base64 decoder issue can be turned into code execution rather than a Java virtual machine crash.
  • Whether third-party OpenJDK distributions carry the reported flaw and when their maintainers will ship fixes.
  • Whether either the 11 flaws or the reported OpenJDK issue is being exploited in the wild.

What to do

If you run Oracle Java SE, GraalVM or JavaFX

  1. Inventory every Java runtime in use and record its version, including application servers and build tooling.
  2. After the 17 November update, move off the current builds named in Oracle's notice to the replacement releases listed in its release notes.
  3. Identify internet-facing applications running Java and test and install the updates there first.

If you run OpenJDK or another third-party Java build

  1. Ask your distribution's maintainer whether it carries the reported Base64 decoder flaw and when a fix will ship, since Oracle's notice does not cover third-party builds.
  2. If you need an interim mitigation on x86-64 hardware with AVX-512, Upwind and Equixly name the JVM options -XX:-UseBASE64Intrinsics and -XX:UseAVX=2; neither is vendor-confirmed and the second slows other work.
  3. Do not conclude from the reserved CVE record alone that your deployment is vulnerable or that a given update fixes it.

For everyone else

  1. Wait for Oracle's full advisory and an OpenJDK Vulnerability Group advisory before treating the reported 9.2 severity and version range as settled.
  2. Treat claims posted on social media about a leaked flaw as unverified until technical details are published and the behaviour reproduced.

Update log

  • First published.

Sources

New incident reports by email

One email a week with the reports published since the last one.

Want us to look at your domain?

Give us one apex domain and we'll send back a written snapshot of what is already visible from outside. No call required.