Alert

Logo de Oracle

Alert 2026-169 Oracle Java November out-of-cycle patch and confirmed remote code execution in OpenJDK

First update: Nov 17, 2026

On the afternoon of Nov 17, 2026 the vendor published the complete November Critical Security Patch Update advisory (Rev 1; last modified at 6:21 p.m. (PYT)). The notice is no longer in pre-release announcement form. The official batch goes from the 652 fixes cited in the pre-release announcement to 655 new security patches. There are still 11 fixes for Oracle Java SE, all exploitable over a network without authentication; the vendor’s highest score in that batch remains CVSS 8.1, high, and it corresponds to CVE-2026-114938.

CVE-2026-114938 is now confirmed and linked to this batch: it appears in the Oracle Java SE risk matrix (Compiler component) and in the OpenJDK project’s advisory of Nov 17, 2026 (hotspot/compiler component). The official record was published on Nov 17, 2026 at 6:32 p.m. (PYT) and updated at 7:02 p.m. (PYT). The vendor describes a difficult-to-exploit flaw, exploitable over a network without authentication, that can result in takeover of the product, and rates it CVSS 8.1, high; the OpenJDK project publishes the same 8.1. Researchers assign CVSS 9.2, critical. That 9.2 is still not a score from Oracle or from OpenJDK.

Researchers published a technical report on Nov 17, 2026 at 6:11 p.m. (PYT) and demonstrated remote code execution. The flaw is a memory-corruption issue in the hardware-accelerated (intrinsic) code of OpenJDK’s Base64 decoder, on x86-64 processors with AVX-512 VBMI. They demonstrated unauthenticated remote code execution with default configuration on Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate; with authentication, on Kafka, Solr, Elasticsearch, Gerrit and Spinnaker; also on sample Struts and Spring Boot applications, and a client case: a Java program that opens a TLS connection to a malicious server can be compromised. The lists are not exhaustive and are not product advisories from those vendors. The memory-corruption trigger is public; the researchers are for now holding back the product-specific chains and note that there is no universal exploit. As of this review there is no known active exploitation and no complete public remote-code-execution exploit. Product, mitigation and solution details are below.

Affected product(s): 

Product (11-fix batch)Affected versions
Oracle Java SE8u511 (and 8u511-perf), 11.0.33, 17.0.21, 21.0.13, 25.0.5 and 27.0.1. Fixed on Nov 17, 2026: 8u513 (and 8u513-perf), 11.0.33.1, 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1
Oracle GraalVM for JDK17.0.21 and 21.0.13, according to the announcement. Fixed: 17.0.21.1 and 21.0.13.1
Oracle GraalVM Enterprise Edition21.3.20.0.3. Fixed: 21.3.20.1
Oracle JavaFX21.0.13, 25.0.5 and 27.0.1. Fixed: 21.0.13.1, 25.0.5.1 and 27.0.1.1
Product (CVE-2026-114938)Affected versions
OpenJDK and derivative distributions17.0.6 or later (branches 17, 21, 25 and 27), according to the technical report. The OpenJDK advisory marks those four branches as affected; the columns for 8 and 11 are empty for this CVE
Oracle Java SE8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3. Standard 8 and 11 are not listed
Oracle GraalVM for JDK17.0.21.0.3 and 21.0.13.0.3
Oracle GraalVM Enterprise Edition21.3.20.0.3

Exploitation of CVE-2026-114938 also requires an x86-64 processor with AVX-512 VBMI; ARM64 is not affected. Having Java 17, 21, 25 or 27 is not, by itself, enough to claim exposure. Oracle’s standard 8 and 11 are not listed for this CVE, but they are in other fixes in the same batch and should be updated for that reason. The official GraalVM calendar publishes 25.0.5.1 on Nov 17, 2026, without listing that branch in this CVE. Amazon Corretto has already published replacement builds; equivalent builds were not located in other packagers at this time. Embedded and containerized runtimes should also be inventoried.

Description

An out-of-cycle Oracle security patch has been published, corresponding to the November 2026 Critical Security Patch Update. The complete advisory (Rev 1, Nov 17, 2026) covers 655 new security patches across various vendor products; this bulletin focuses on Oracle Java SE, GraalVM and JavaFX, where 11 fixes are published. The vendor states that all 11 may be exploited over a network without authentication. The highest score it publishes for that batch is CVSS 8.1, high, and it corresponds to CVE-2026-114938. This bulletin is classified as CRITICAL because of the takeover the vendor describes, because of demonstrated remote code execution in widely used products, and because of a CVSS 9.2, critical, assigned by researchers. That 9.2 is not a score from Oracle or from OpenJDK.

The complete advisory has now published the risk matrix, with the identifiers and the component of each flaw. CVE-2026-114938, also referred to in public as “Java4Shell” (it previously circulated as “Java2Shell”; it is not an official name from the vendor or from the OpenJDK project), is in Oracle’s Compiler component and in hotspot/compiler according to OpenJDK. The vendor states that the flaw is difficult to exploit, that it can be exploited over a network without authentication, and that a successful attack can result in takeover of the product. It also states that this flaw is exploited only by supplying data to APIs of the indicated component, for example through a web service, and not through untrusted Java Web Start applications or applets. The other ten CVEs in the Java batch are now identified in the matrix; they are not the focus of this update, and it is not claimed that all 11 are remote code execution.

According to the technical report, the flaw is a memory-corruption issue in OpenJDK’s Base64 decoder, in hardware-accelerated code using AVX-512 VBMI instructions. A malformed input can write past the output buffer on the heap and, with additional work, be used to read memory and reach remote code execution. The memory-corruption trigger is public; at this time there is no complete public remote-code-execution exploit and no universal exploit: the chain depends on how the application uses Base64. Researchers demonstrated unauthenticated remote code execution, with default configuration, on Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate, and with authentication on Kafka, Solr, Elasticsearch, Gerrit and Spinnaker; also on sample Struts and Spring Boot applications, and on a Java program that opens a TLS connection to a malicious server. Those lists are not exhaustive and do not replace a product advisory from each vendor. As of this review there is no known active exploitation. Product advisories from those applications were not located.

Oracle’s replacement builds, published on Nov 17, 2026, are 8u513 (full string 1.8.0_513-b04, and 8u513-perf), 11.0.33.1 (11.0.33.1+4), 17.0.21.1 (17.0.21.1+4), 21.0.13.1, 25.0.5.1 and 27.0.1.1, with equivalents in GraalVM and JavaFX. The vendor states that it is not recommended to remain on these builds after the next critical patch, planned for Jan 19, 2027. Amazon Corretto published 17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2 and 27.0.1.1.4 the same day; the 17 build explicitly lists CVE-2026-114938. Equivalent builds were not located in other packagers at this time. As background, Alert 2026-121 covered a distinct October advisory on Java SE and GraalVM; the builds from that advisory are superseded by those in this patch.

Mitigation

The confirmed fix is to update to the builds published on Nov 17, 2026 and listed in Solution, and to restart the virtual-machine processes so they load the new runtime, starting with internet-facing services. Java runtimes should be inventoried (servers, applications, middleware, containers, embedded installations and images generated with jlink), with vendor, version and build, and hardware should be checked for x86-64 with AVX-512 VBMI. On Linux, that check can be done by verifying that /proc/cpuinfo includes avx512f, avx512bw, avx512vbmi and bmi2 together.

If the patch cannot yet be applied, researchers publish a temporary mitigation: start the virtual machine with -XX:-UseBASE64Intrinsics (disables Base64 hardware acceleration; this is the narrower option) or, on x86-64 hosts only, -XX:UseAVX=2 (disables AVX-512 and has a broader performance impact). That second flag must not be applied on ARM: OpenJDK does not recognize it on that architecture and fails to start. Neither is a workaround published by Oracle.

Those using Amazon Corretto can move to the .1 builds listed in Solution. Those using another packager should follow that vendor’s channel; at this time those builds were not located, except for Corretto. The patch should be tested in a staging environment and then deployed, with backups ready. The patch does not undo a prior compromise. The vendor has not published indicators of compromise.

Solution

The solution is to inventory installations of Oracle Java SE, GraalVM and JavaFX, and OpenJDK runtimes from other vendors, including embedded ones and those running in containers. After the usual tests, apply the updates and restart the virtual-machine processes:

  • Oracle Java SE: 8u513 (and 8u513-perf, if applicable), 11.0.33.1, 17.0.21.1, 21.0.13.1, 25.0.5.1 or 27.0.1.1, according to the branch.
  • Oracle GraalVM for JDK: 17.0.21.1, 21.0.13.1 or, if that branch is in use, 25.0.5.1 according to the official calendar.
  • Oracle GraalVM Enterprise Edition: 21.3.20.1.
  • Oracle JavaFX: 21.0.13.1, 25.0.5.1 or 27.0.1.1.
  • Amazon Corretto: 17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2 or 27.0.1.1.4, according to the branch.

Those using another OpenJDK distribution should follow that vendor’s channel; at this time .1 builds were not located, except for Corretto’s. Prioritize internet-facing systems and check whether the hardware is x86-64 with AVX-512 VBMI. In parallel, restrict network access that is not required until the update is complete.

For information on how to update, visit the following link:

https://www.oracle.com/security-alerts/cspunov2026.html

Additional information: