Skip to main content
Alert

CVE-2026-114938 (Java4Shell): Critical OpenJDK Vulnerability Allows Remote Takeover of Java Servers

18 November 2026

A critical vulnerability in OpenJDK (CVE-2026-114938) allows an attacker to take over a Java server remotely, often without credentials. A patch has been available since 17 November. Patch internet-facing Java services within 72 hours and set a startup flag until then.

On 17 November a patch was released for CVE-2026-114938, nicknamed "Java4Shell". This vulnerability in Java (OpenJDK) allows an attacker to take over a server remotely, often without credentials. A proof of concept is public. Active exploitation has not yet been confirmed.

Our advice in four points

Patch internet-facing Java services within 72 hours. Set a startup flag until then.

  • Decide what goes first. Internet-facing Java services that decode Base64 from user input go first.
  • Cannot patch today? Set a startup flag. Start the JVM with -XX:-UseBASE64Intrinsics. This requires a restart.
  • Patch within 72 hours. Exposed systems first, internal systems after.
  • Talk to your suppliers. Ask which Java version they ship and when their update will be released.

If you do not know which Java version a system runs, treat it as vulnerable.

What is going on: a single Base64 string is enough

  • Severity: critical (CVSS 4.0: 9.2). Oracle rates it 8.1 under CVSS 3.1.
  • One specially crafted Base64 string is enough to execute code on the server. Base64 appears in authentication headers, session tokens, SAML messages and APIs.
  • Affected are OpenJDK from 17.0.6 onwards and all derived distributions, including Oracle Java SE, Temurin, Corretto, Azul Zulu and Red Hat OpenJDK. Oracle Java SE 8 Enterprise Performance Pack is also affected.
  • This applies only to x86-64 processors with AVX-512 VBMI: Intel Xeon from Ice Lake onwards and AMD from Zen 4 onwards. ARM64 is not affected.
  • Exploitation has been demonstrated without authentication in Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate, and with authentication in Kafka, Solr, Elasticsearch, Gerrit and Spinnaker.

Where is Java? In more places than you think

Include the Java runtimes that suppliers bundle with their products.

  • Your own applications: applications built on Spring Boot, Apache Struts and other Java frameworks.
  • Identity and collaboration: Keycloak, PingFederate, Jira and Confluence.
  • Development pipeline and data: Jenkins, Artifactory, Gerrit, Spinnaker, Kafka, Solr and Elasticsearch.
  • Third-party systems: products and appliances with their own Java runtime, and services a supplier manages for you.

Look internally as well. A Java program that opens a TLS connection to an attacker's server is vulnerable in the same way.

Action plan: what to do now

Carry out steps 1 to 4 today. Steps 5 and 6 follow within 72 hours.

Today: inventory and shield

1. Find out where Java runs. Map every JDK and JRE, including those in third-party products and appliances. Start with internet-facing services that decode Base64 from user input. If you do not know the version, treat the system as vulnerable.

2. Check the processor. On Linux, the host is vulnerable if this command returns all four flags:

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

3. Cannot patch immediately? Set a startup flag. Start the JVM with -XX:-UseBASE64Intrinsics. The alternative, on x86-64 only, is -XX:UseAVX=2. Both require a restart of the service. This is a temporary measure: the flags reduce exposure but do not replace the patch.

4. Contact third parties directly. Ask every supplier and managed service provider which Java version they ship and when their update will be released.

Within 72 hours: patch and verify

5. Patch to the fixed version. Install the fixed version from your distributor. Exposed services first, internal systems after.

  • Oracle Java SE 8 Enterprise Performance Pack: vulnerable 8u511b33-perf, fixed in 8u513-perf
  • Oracle Java SE 17: vulnerable 17.0.21.0.3, fixed in 17.0.21.1
  • Oracle Java SE 21: vulnerable 21.0.13.0.3, fixed in 21.0.13.1
  • Oracle Java SE 25: vulnerable 25.0.5.0.3, fixed in 25.0.5.1
  • Oracle Java SE 27: vulnerable 27.0.1.0.3, fixed in 27.0.1.1
  • Amazon Corretto 17: fixed in 17.0.21.1.2

Other distributors follow their own schedule. Check their advisory.

6. Check for exploitation. Do this before you declare a system clean. Watch for these signs:

  • JVM crashes and new hs_err_pid*.log files.
  • Repeated restarts of the same Java service in a short time.
  • Unusually long Base64 input or irregular padding in headers, cookies and SAML messages.
  • Unexpected child processes of the JVM and new outbound connections.

If you find traces, isolate the system and call in incident response.

Ongoing: heightened vigilance

  • Have your SOC or managed service provider monitor these signs until everything is patched.
  • Stay alert over the coming days. The researchers have announced exploit chains for individual products.

Frequently asked questions

Our servers run on ARM. Are we vulnerable? No. Update anyway: workloads can always move to other hardware.

Does a web application firewall help? Only partly. The input looks like ordinary Base64 and is hard to filter without breaking legitimate traffic.

We use Java 8 or 11. Are we safe? Standard builds fall outside the published range. The exception is Oracle Java SE 8 Enterprise Performance Pack. Ask your distributor for confirmation.

For your security team: the technical details

This is an out-of-bounds heap write in the HotSpot Base64 intrinsic for x86-64. With input that has irregular padding, the write mask (bzhiq) is miscalculated and evmovdqub writes 64 bytes, up to 62 bytes past the end of the buffer. The trigger is a string of 64 times the letter A, followed by an = sign. On OpenJDK 17 it takes 128 times the letter A.

Sources: Calif (calif.io/java4shell), OpenJDK Vulnerability Advisory 2026-11-17, Oracle Security Alerts, Tenable and Cisco Talos.

How DEFION helps

We map where Java runs, search for traces of exploitation with Managed Threat Hunting, help with patching and provide incident response. Follow current threats on our threat intelligence page.

Questions or need help? Contact your usual DEFION contact, call our main number +31 88 733 13 37 or get in touch through our website.

Download the full advisory as a PDF (4 pages, in Dutch).

← Back to news