AI for Business

Oracle to Patch 11 Java Flaws on November 17 as Unverified OpenJDK RCE Report Circulates

Oracle plans to ship security fixes for 11 Java SE vulnerabilities on Tuesday, November 17, 2026, all of which can be attacked over a network without credentials, according to the company's...

Share:
Oracle to Patch 11 Java Flaws on November 17 as Unverified OpenJDK RCE Report Circulates

Oracle plans to ship security fixes for 11 Java SE vulnerabilities on Tuesday, November 17, 2026, all of which can be attacked over a network without credentials, according to the company's advance security notice. The flaws carry a maximum CVSS 3.1 score of 8.1. Oracle has not released their CVE identifiers, affected components, or what exploitation of each one could achieve.

Separately, an OpenJDK flaw tracked as CVE-2026-114938 is being reported with a CVSS 4.0 score of 9.2, affecting OpenJDK 17.0.6 and later. Those details remain unconfirmed, and nothing yet shows the flaw is among the 11 Oracle intends to patch. Security firm Calif said on X that it found and reported the bug, which it calls Java4Shell, and that it had leaked; Calif said it would publish technical details at 1 p.m. Pacific on November 17, after Oracle releases a patch. Security company watchTowr acknowledged the reports but cautioned the technical details are unconfirmed.

Analyses of OpenJDK source code by Upwind and Equixly separately point to a flaw in Java's AVX-512 Base64 decoder whose likely outcome is a JVM crash rather than code execution. The code runs only on x86-64 processors with AVX-512 VBMI support when untrusted data reaches java.util.Base64's basic or URL decoder; ARM servers do not run it. It appears in Java 17.0.6 and later plus Java 21, 25 and 27, but not standard Java 8 or 11. Neither firm reported reproducing the overflow on AVX-512 hardware. The CVE record remains reserved with no public description, and no advisory has named the vulnerable component, exploitation requirements, affected version range, or a fix.

Oracle is directing customers to move off current builds of Java 8, 11, 17, 21, 25 and 27 after the update. Planned replacement builds listed on ops.java include 8u513, 11.0.33.1, 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. The notice covers Oracle Java SE, 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 warns the information may change before the full advisory is published.

Upwind and Equixly named two JVM options as stopgaps to block the flawed code: -XX:-UseBASE64Intrinsics and -XX:UseAVX=2, the latter disabling all AVX-512 paths and potentially slowing other work. Neither option has been confirmed by a vendor for this flaw. Oracle's notice covers its own products and does not establish the patch status of third-party OpenJDK distributions. The OpenJDK Vulnerability Group had published no advisory newer than October 24 at the time of the earlier review. Oracle began monthly Java security releases on May 28, and its plan last updated September 10 set November 17 as the next release.

Source: The Hackers News

Ready to Modernize Your Business?

Get your AI automation roadmap in minutes, not months.

Analyze Your Workflows →