Urgent Patch CVE

Java4Shell (CVE-2026-114938): Patch Released for the CVSS 9.2 Remote Code Execution Vulnerability

Check your Java runtime and CPU, apply the patch, and verify the running version.

Contents
  1. 1Vulnerability summary
  2. 2Attacks have been reproduced in real Java applications
  3. 3Affected Java versions and fixed releases
  4. 4How to check whether a service is affected
  5. 5How to apply the patch
  6. 6If you cannot apply the patch immediately
  7. 7Include the Java runtime in your component inventory
  8. 8Update history
  9. 9References

Oracle released a security patch for Java4Shell on November 17. Tracked as CVE-2026-114938, the vulnerability can allow remote code execution (RCE) without authentication on affected OpenJDK builds from 17.0.6 onward. It is rated 9.2 (Critical) under CVSS 4.0.

The flaw is in Java's Base64 decoder. On certain CPUs, the optimized code that processes Base64 data can write beyond allocated memory when it encounters malformed input. Researchers at Calif demonstrated memory disclosure and remote code execution using this flaw.

The team demonstrated attacks before authentication against real Java applications, including Keycloak, Jira, Confluence, and Jenkins, running their default configurations. They also reproduced an attack against a sample Spring Boot application.

The impact varies by server. Check the Java version and CPU instruction support, as well as whether external input can reach the vulnerable Base64 decoder.

Vulnerability summary

ItemDetails
NameJava4Shell
CVECVE-2026-114938
Vulnerability typeHeap-based Buffer Overflow (CWE-122)
Vulnerable componentOpenJDK Base64 Decoder / optimized code
SeverityCVSS 4.0: 9.2 (Critical)
Oracle ratingCVSS 3.1: 8.1 (High)
Affected scopeVulnerable OpenJDK builds from 17.0.6 onward, certain performance-optimized Oracle Java SE 8 builds, and related distributions
Attack conditionsA vulnerable runtime, a CPU with AVX-512 VBMI support, and malicious Base64 input reaching the affected code
Potential impactMemory corruption, information disclosure, service disruption, and remote code execution
PoCLimited reproduction code and attack demonstrations published
Patch statusOracle patch released on November 17, 2026

Oracle and Calif used different versions of CVSS. Oracle assigned a score of 8.1 (High) under CVSS 3.1, while Calif published a score of 9.2 (Critical) under CVSS 4.0.

Attacks have been reproduced in real Java applications

Calif reported demonstrating remote code execution against the following applications running on vulnerable JVMs.

Attack conditionsApplications demonstrated by the researchers
RCE before authenticationKeycloak, Jira, Confluence, JFrog Artifactory, Jenkins, PingFederate
RCE after authenticationApache Kafka Broker, Apache Solr, Elasticsearch, Gerrit, Spinnaker
Sample applicationsSpring Boot, Apache Struts

This list reflects the researchers' tests. It does not establish that attacks succeed against every version or deployment of these products.

If you use Spring Boot, distinguish the framework from the JVM. This vulnerability is in the JVM rather than the framework itself. A Spring Boot application may be affected if it runs on a vulnerable JVM and externally supplied Base64 input reaches the vulnerable decoding path.

The attack path described by the researchers does not apply when the CPU lacks the required instructions or the JVM has been patched. The team published memory-corruption reproduction code and demonstrations against real applications, but said they would keep the weaponized, product-specific exploits private for now.

According to the Canadian Centre for Cyber Security's advisory dated November 17, 2026, no exploitation in the wild was known at that time. This does not rule out future exploitation.

Affected Java versions and fixed releases

Oracle published its final Critical Security Patch Update (CSPU) on November 17. The Korea Internet & Security Agency (KISA) also recommended applying security updates for CVE-2026-114938 on November 18. The affected and fixed versions listed in the Oracle and KISA advisories are shown below.

ProductAffected versionFixed version
Oracle Java SE 88u511b33-perf8u513
Oracle Java SE 1717.0.21.0.317.0.21.1
Oracle Java SE 2121.0.13.0.321.0.13.1
Oracle Java SE 2525.0.5.0.325.0.5.1
Oracle Java SE 2727.0.1.0.327.0.1.1
GraalVM for JDK 1717.0.21.0.317.0.21.1
GraalVM for JDK 2121.0.13.0.321.0.13.1
GraalVM Enterprise21.3.20.0.321.3.20.1

The affected versions in this table are those listed in Oracle's official risk matrix. Older vulnerable builds that have missed previous updates may also be affected. A version string that differs from the table does not establish that a system is safe.

Oracle's affected-product list for this CVE does not include standard Oracle Java SE 8 or Java SE 11. Red Hat also states that standard OpenJDK 8 and OpenJDK 11 do not contain the vulnerable code path. Other vulnerabilities in these versions were fixed in November, however, so regular security updates are still needed.

Distributions other than Oracle JDK may also be affected, including Eclipse Temurin, Amazon Corretto, Azul Zulu, Red Hat OpenJDK, and Microsoft Build of OpenJDK. Their fixed version numbers and release dates may differ from Oracle's. Check the official security advisory from your runtime vendor.

How to check whether a service is affected

Check the Java version, CPU capabilities, and JVM startup configuration together.

Check the Java version and distribution

Start by checking the Java version.

java -version

Example output:

openjdk version "17.0.21"
OpenJDK Runtime Environment Temurin-17.0.21+9
OpenJDK 64-Bit Server VM

This identifies the Java version and distribution used by the current shell. The production service may use a different runtime, so check the running process too.

Find the actual JVM executable on Linux

# List running Java processes
ps -eo pid,args | grep '[j]ava'

# Find the Java executable used by the process
readlink -f /proc/<PID>/exe

# Check the running JVM version
jcmd <PID> VM.version

# Check JVM startup options
jcmd <PID> VM.command_line

Replace <PID> with the actual Java process ID. Using jcmd requires permission to access the target JVM and an environment that supports the tool. If several Java versions are installed in production, record the actual executable path and version for each application.

Check CPU support for AVX-512

Java4Shell occurs in code that uses specific CPU instructions. On Linux, check for the relevant CPU features with:

grep -m1 '^flags' /proc/cpuinfo \
  | tr ' ' '\n' \
  | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'

A CPU that meets the hardware conditions should report all four features:

bmi2
avx512f
avx512bw
avx512vbmi

The output order may differ.

The researchers identified potentially affected CPU families including Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, and certain AMD CPUs based on Zen 4 or later.

The currently known vulnerable code path is reported not to execute on ARM64 or on CPUs without AVX-512 VBMI support.

CPU support alone does not establish that an attack can succeed. Check JVM startup options and whether external input reaches the affected code as well. A virtual machine or container may not expose every feature of the physical CPU. Assess the environment in which the JVM actually runs.

Check Docker and Kubernetes environments

For Docker, check the Java version inside the running container.

docker exec <container> java -version

For Kubernetes, use:

kubectl exec -n <namespace> <pod> -- java -version

If the Pod contains multiple containers, specify the target with the -c option. If the container has no shell or diagnostic tools, inspect the image configuration and the Java runtime used during the build.

How to apply the patch

Oracle released the security patch on November 17, 2026. Teams should now move from preparing a response to applying the fixed release.

For Java 17, Oracle's fixed build is 17.0.21.1+4.

If you use Oracle JDK

  1. Check the affected versions in Oracle's official security advisory.
  2. Obtain the fixed release for your product and operating system.
  3. Test Java compatibility and the application's key functions.
  4. Apply the update in production and restart the JVM.
  5. Check the version of the Java process that is actually running.

For Oracle JDK 17, the 17.0.21.1 release notes identify the fixed version and build number.

If you use another OpenJDK distribution

For Eclipse Temurin, Amazon Corretto, Azul Zulu, and other distributions, apply the fixed package from your vendor.

Check the distribution's security advisory to confirm that CVE-2026-114938 has been fixed. Its package may use a different version number from Oracle's 17.0.21.1.

For Docker or Kubernetes, rebuild and deploy using a base image that includes the fixed JDK.

After patching, check the running JVM version against the vendor's patch information. An image tag alone is not enough.

If you cannot apply the patch immediately

If compatibility issues prevent an immediate update, you can temporarily disable the vulnerable JVM optimization.

Disable the Base64 optimization

Calif recommends the following JVM option as a mitigation:

-XX:-UseBASE64Intrinsics

Include it when starting the Java application.

java -XX:-UseBASE64Intrinsics -jar app.jar

This option disables the JVM's hardware-accelerated Base64 optimization path. It avoids the vulnerable optimized code while retaining the application's functionality. Base64 processing performance may be affected, so test compatibility and performance before applying it.

Limit AVX-512 use

The following option has also been recommended for x86-64 environments:

-XX:UseAVX=2

This limits the JVM's AVX instruction level so that it does not use the AVX-512 path. It may affect the performance of operations beyond Base64. The option is not supported on ARM and can prevent the JVM from starting there.

Both options must be set at JVM startup, so the service needs to be restarted. Changing an environment variable alone does not apply them to an application that is already running.

Restrict network access and service permissions

Review the Java service's external exposure while waiting to apply the patch.

On Linux, list listening ports with:

sudo ss -lntp

Restrict unnecessarily exposed administrative ports through firewalls and security groups. Java4Shell can be triggered through ordinary Base64 decoding, however, so blocking a particular port or deploying a WAF does not guarantee that the vulnerability is addressed.

Even if you have applied a temporary mitigation, update to the patched JVM when it becomes available.

Include the Java runtime in your component inventory

Java4Shell is not a vulnerability in a particular Spring Boot library. The flaw is in the JVM's optimized Base64 code, so it can affect multiple Java applications that use the same runtime.

Security teams need to track both the application and the Java runtime actually deployed with it. Record the following:

  • Java distribution, version, and build number for each service and product
  • CPU architecture and supported instructions in the actual execution environment
  • Paths through which external input reaches Base64 decoding
  • Java runtimes included in Docker images and products
  • Patch status and verification results after redeployment

Including the Java runtime's vendor and version in a software bill of materials (SBOM) helps identify affected assets when a new vulnerability is disclosed.

Z-BOM is ZIEN's SBOM-based supply chain security management platform. Component management through such a platform also requires identifying the Java runtime and comparing CVE information with the Java version actually deployed to determine the affected scope.

In Java4Shell, optimized code inside the JVM corrupted memory. The memory safety generally expected from Java is not always guaranteed in that internal code.

Attack demonstrations and security patches are now public. Organizations using Java should check for vulnerable JVMs and the required CPU conditions, then apply their vendor's fixed release. After patching, verify the actual processes running in production.

Update history

Date (Korea Standard Time)Changes
2026-11-17Response preparations based on Oracle's November CSPU advance notification
2026-11-18Added the disclosure of CVE-2026-114938 and the Java4Shell technical analysis
2026-11-18Added Oracle's fixed versions and KISA's security update advisory

References

Oracle — Critical Security Patch Update Advisory, November 2026

Oracle official security advisory

Calif — Java4Shell: Write once, RCE everywhere

Technical analysis by the researchers who discovered the vulnerability

KISA — Oracle Product Security Update Advisory

KISA official security advisory

Red Hat — RHSB-2026-018, Java4Shell

Red Hat security bulletin and affected configurations

Oracle — JDK 17.0.21.1 Release Notes

Java 17 security update release notes

Canadian Centre for Cyber Security — AL26-029

Java4Shell risk and response advisory

Z ZIEN
Free 30-minute assessment · Z-BOMCould our service be affected? Request consultation →