← All articles

Java vulnerability alert: 11 flaws and an open-source RCE report

Java vulnerability alert: 11 flaws and an open-source RCE report

A Java vulnerability alert is developing ahead of the Java vendor’s planned security release on Tuesday, November 17, 2026. The vendor says it will patch 11 vulnerabilities in Java SE, all potentially exploitable remotely over a network without authentication. Separately, CVE-2026-114938 has been reported as a potentially critical issue in the open-source implementation of Java, but its severity, impact and connection to the vendor’s 11 planned fixes remain unconfirmed.

The vendor’s advance security notice gives the 11 Java SE vulnerabilities a maximum CVSS 3.1 score of 8.1. CVSS, or Common Vulnerability Scoring System, is a scale used to describe the seriousness of security flaws. The vendor has not yet published the CVE identifiers, affected components or individual consequences for those 11 vulnerabilities. The company also warns that the information may change before the complete advisory appears.

The vendor says the affected products and versions include Java SE 8u511, 8u511-perf, 11.0.33, 17.0.21, 21.0.13, 25.0.5 and 27.0.1. The notice also covers the vendor’s GraalVM for JDK 17.0.21 and 21.0.13, the vendor’s GraalVM Enterprise Edition 21.3.20.0.3, and the vendor’s JavaFX 21.0.13, 25.0.5 and 27.0.1. GraalVM is a Java development and runtime technology, while JavaFX is a Java technology for building application interfaces.

The vendor’s guidance tells customers to stop using the current builds after the November 17 security update and move to the corresponding replacements. The planned builds listed on ops.java are Java 8 8u513, Java 11 11.0.33.1, Java 17 17.0.21.1, Java 21 21.0.13.1, Java 25 25.0.5.1 and Java 27 27.0.1. As of 16:59 UTC, ops.java listed those replacement builds as current releases, while the vendor’s advance notice, release notes and download page still showed the earlier builds.

Remote exploitation without credentials does not automatically mean that every flaw enables remote code execution, or RCE, which means making a vulnerable computer run an attacker’s commands. It also does not mean every application using an affected Java version can be attacked directly. The vendor has not identified the vulnerable Java components or explained what an attacker could achieve with each flaw.

The separate report concerning the open-source implementation involves CVE-2026-114938. Calif said it discovered and reported the issue, called Java4Shell, and said technical details had leaked. Calif planned to publish those details by 1 p.m. Pacific time on November 17, after the vendor released a patch. WatchTowr acknowledged the reports but cautioned that the technical information was still unconfirmed. The CVE record remains reserved, with no public description, and no official advisory has identified the component, exact exploitation requirements, affected version range or a fix.

Analyses by Upwind and Equixly reached a different and more limited technical conclusion from the public reports. Their reviews of the open-source Java implementation’s source code point to a possible flaw in Java’s AVX-512 Base64 decoder. Base64 is a method for representing data as text, and a decoder converts that representation back into data. The likely result is a crash of the Java virtual machine, or JVM, rather than code execution.

The suspected flaw appears to run only on x86-64 processors with AVX-512 VBMI support, when untrusted data reaches the basic or URL decoder in Java’s Base64 utility. ARM servers do not run this code. The code is present in Java 17.0.6 and later and in Java 21, 25 and 27, but not in standard Java 8 or 11. The likely outcome is a crash because the bytes written beyond the buffer are fixed and cannot be selected by an attacker. Neither Upwind nor Equixly reported reproducing the overflow on AVX-512 hardware.

Both firms identified two possible stopgaps, but neither has been confirmed by a vendor for this flaw. The first option disables the Base64 intrinsics, while the second limits AVX use to level 2, disabling all AVX-512 code paths and potentially slowing other work. The vendor’s Java 8 Enterprise Performance Pack release notes for 8u371-perf describe a Base64 decoding optimisation for x86 using AVX-512, but neither firm said whether that Performance Pack is affected.

The vendor’s November notice covers its products and does not establish the patch status of third-party open-source Java distributions. The OpenJDK Vulnerability Group, which coordinates security disclosures affecting the open-source Java source code, had not published an advisory newer than October 24 at the time of the earlier review. Until official details emerge, organisations cannot determine from CVE-2026-114938 alone whether their deployments are vulnerable or which update addresses the issue.

The vendor began a monthly security patch cycle on May 28, adding targeted releases between its quarterly Critical Patch Updates. Its Java security update plan, last updated September 10, listed November 17 as the next scheduled monthly release. IT teams should inventory Java runtimes, identify internet-facing applications, and prepare to test and install the relevant vendor updates when available. For organisations reviewing their wider exposure, AEU-I provides security-first IT, infrastructure and consulting.

Also available in: DeutschItalianoShqip