On November 17, 2026, Oracle and OpenJDK published security advisories and fixes for Java4Shell (CVE-2026-114938), a Java vulnerability. On Java Virtual Machines (JVMs) that use certain CPU instructions, processing specially crafted Base64 data could lead to remote code execution (RCE) without authentication. The affected environments and the way to apply fixes differ depending on whether Java was installed as an OS package, bundled with a product, or provided as a runtime managed by a cloud provider. Details are available in Oracle's security alert and OpenJDK's advisory.

AD

Environments affected by the Base64 acceleration code

Base64 is an encoding scheme that represents byte sequences as text, and Base64 decoding is the process of converting encoded data back into the original bytes. According to Red Hat's technical explanation, the HotSpot JVM uses the CPU instruction extension "AVX-512 VBMI" on certain x86-64 environments to speed up Base64 decoding. Passing crafted data to this code can corrupt memory. According to Clever Cloud's explanation, the flaw lies in the decoding routine writing data outside the allocated memory region. If exploited, it could cause service outages and leak sensitive information, and it could let an attacker remotely execute arbitrary code with the privileges of the Java process.

To determine whether a system is affected, you need to check the build of the running JVM and whether the CPU supports the relevant instructions. According to Red Hat, unpatched versions from 17.0.6 onward in the OpenJDK 17 series are affected. Meanwhile, JPCERT/CC's advisory states that ARM64 processors are not affected by this vulnerability. If you use an affected JVM and CPU, what matters is at which stage your application Base64-decodes data it receives from outside. Oracle says the flaw could be exploited through multiple protocols, and it envisions cases in which data from web services and similar sources is passed to Java APIs. In applications that run the decoding before login, even a service with authentication features could be attacked without going through authentication.

Calif, the security research organization that discovered the vulnerability, published details on November 17. According to JPCERT/CC, Calif demonstrated unauthenticated remote code execution in a research environment against Java-based applications including Keycloak, Jira, Confluence and Jenkins. However, as of November 18, JPCERT/CC had not confirmed any reports of the vulnerability being exploited in actual attacks.

OpenJDK and Oracle treat Java 8 differently

OpenJDK's impact list for CVE-2026-114938 covers four series—Java 17, 21, 25 and 27—and Java 8 and 11 carry no marker indicating impact. The top of the advisory also lists Java series related to other vulnerabilities, which must be distinguished from those affected by Java4Shell. Oracle's Java SE list, on the other hand, includes 8u511b33-perf, the Java 8 performance-enhanced "Enterprise Performance Pack." For this reason, even systems running Java 8 cannot be assessed by checking only the major version; you need to examine the product and build actually in use.

Oracle lists the affected Java SE versions as 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3. Oracle GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3, and Oracle GraalVM Enterprise Edition 21.3.20.0.3, are also affected. These are vulnerable versions, not fixed ones, so the update target must be confirmed for each product and distributor. In the fixed releases published the same day, Oracle JDK 17 became 17.0.21.1 (full version 17.0.21.1+4), and the Enterprise Performance Pack became 8u513-perf. Details are in the Oracle JDK 17 release notes and the Enterprise Performance Pack release notes.

Both Oracle and OpenJDK rate the severity at 8.1 on the CVSS 3.1 base score. Oracle rates attack complexity as "high," while saying the flaw can be exploited over the network and requires neither prior privileges nor user interaction from the attacker. By contrast, Atlassian assessed the impact on its own Data Center products and rated it CVSS 9.2. In practice, besides these severity ratings, it is important to check whether your configuration allows externally supplied data to reach the vulnerable code.

AD

Distributor fixes and deployment to running environments are separate steps

How the response to Java4Shell proceeds depends on the Java distributor and how the service is operated. Amazon Linux published fixed Corretto packages, while Atlassian issued interim workarounds for its Data Center products and said it would provide product patches once fixed Temurin versions are released. Clever Cloud added a mitigation to its default JVM startup settings and, as of its November 17 announcement, was restarting customer instances in sequence. The responses each vendor had announced as of November 18, 2026, and what users need to do, are as follows.

Provider and target Announced response What users should check or do
Amazon Linux 2023 Corretto 17, 21, 25 and 27 Published fixed packages for all four series as of November 17 Update the relevant packages, restart services, and confirm that the new build is in use
Affected Atlassian Data Center products (latest versions with standard configurations) Published product-specific interim workarounds; plans to release emergency product patches once fixed Temurin versions are available Apply the workaround suited to your product and configuration, restart, and update once the product patch is released
Clever Cloud standard Java startup environment and custom startup environments Added an option disabling Base64 acceleration to the standard JVM startup settings; restarting customer instances in sequence Check which startup method you use. If you use custom commands or another runtime, set the mitigation yourself and redeploy

Atlassian's interim workarounds cover the Data Center editions of Bamboo, Bitbucket, Crowd, Confluence, Jira and Jira Service Management. The company says it is investigating the impact on Cloud products but is not currently asking Cloud customers to take action. Clever Cloud, for its part, says it applied the same mitigation to services it manages, including Keycloak, Jenkins and the Elastic Stack.

Check updates and workarounds on the running JVM

JPCERT/CC recommends promptly updating affected environments to fixed versions. Particular attention is needed when an application or product bundles its own Java runtime (JRE). Updating Java on the host OS does not take effect if the product uses its bundled JRE. If the JRE bundled with a product is affected, the product itself must be updated. To confirm that the Java version an administrator sees on the command line matches the one the service actually uses, cross-check the startup settings against the running process.

In container environments, the base image that serves as the application's runtime foundation must also be updated. Red Hat says it is working quickly to deliver fixes for its OpenJDK 17, 21 and 25, and advises updating RHEL and UBI base images and rebuilding application container images. However, updating an image alone does not apply the fix to a running service. You need to redeploy the rebuilt image and confirm that the instances actually handling the service have been switched to the new ones.

For environments that cannot apply the fixed versions immediately, JPCERT/CC lists two JVM startup options as interim workarounds:

  • -XX:-UseBASE64Intrinsics: Disables the acceleration code used for Base64 encoding and decoding.
  • -XX:UseAVX=2: Prevents the JVM from using AVX-512 instructions on x86-64 environments. This also affects processing other than Base64.

Both settings avoid the vulnerable code, but the performance impact varies depending on the option and what the application does. When applying them, follow the procedures given by the product or Java distributor, and after restarting, confirm that the specified option is reflected in the actual JVM startup settings.

If the same service runs on multiple instances, every instance that handles user traffic must be checked. By verifying that each JVM after redeployment is running a fixed version, and that the specified workaround is active in any environment not yet updated, you can judge whether Java4Shell countermeasures have been applied across the whole running environment.