OpenJDK Remote Code Execution Vulnerability (CVE-2026-114938) (Java4Shell)

A critical Java flaw, Java4Shell, exists in OpenJDK, the open-source implementation of Java. Tracked as CVE-2026-114938, the vulnerability can allow unauthenticated attackers to execute code remotely.

Java4Shell is a part of the Java runtime itself, so no application or library must be at fault for a service to be exposed. The flaw lies in handwritten assembly that speeds up Base64 decoding with AVX-512 instructions. A short, malformed input causes that code to write 62 bytes past the end of the buffer before Java rejects the input.

Base64 carries login headers, tokens, and file uploads, so the vulnerable code often runs before a user has authenticated. Calif, the firm that discovered the flaw, demonstrated remote code execution against the following products in their default configurations:

Access required Products
None (pre-authentication) Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, PingFederate
Authenticated user Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit, Netflix Spinnaker

Affected Versions

The vulnerability affects the following versions:

  • OpenJDK 17 before 17.0.21.1
  • OpenJDK 21 before 21.0.13.1
  • OpenJDK 25 before 25.0.5.1
  • OpenJDK 27 before 27.0.1.1

Pre-requisite

The vulnerability is exploitable only when both conditions are true. For an attack to succeed, attacker-controlled data must also reach the vulnerable Base64-decoding path in the application.

Condition Affected Not affected
Java runtime Unpatched OpenJDK-based builds from 17.0.6 onward, including 21, 25, and 27. Also Oracle Java SE 8 Enterprise Performance Pack 8u511b33-perf Releases before 17.0.6, including standard OpenJDK 8 and 11. Also any vendor build that contains the fix
Processor x86-64 with AVX-512 VBMI: Intel Xeon (Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids), AMD EPYC and Ryzen (Zen 4 and newer) ARM64, and x86-64 without AVX-512 VBMI

The runtime condition covers every OpenJDK-based distribution, including Oracle Java SE, Oracle OpenJDK, Oracle GraalVM for JDK, Eclipse Temurin, Amazon Corretto, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, and Red Hat OpenJDK. There is one exception for Java 8. Oracle lists the 8u511b33-perf build of Java SE 8 as vulnerable.

On Linux, run this command to check the processor. The host meets the hardware condition only if all four flags appear.

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

Two cautions when scoping:

  • Check the runtime each application runs. Many products and container images bundle their own JDK, which operating system updates do not touch. CISA notes that bundled runtimes, including those in appliances, may not appear as separate entries in a software inventory.
  • Use the processor condition to order the work, not to close findings. A workload on an unaffected CPU today can be assigned to an affected one after an instance resize or a move to newer hardware.

Mitigation

The vendor has released updates to patch the vulnerability.

For more information, please refer to the OpenJDK Security Advisory.

Qualys Detection

Qualys customers can scan their devices with QIDs 389494, 389610, and 389608 to detect vulnerable assets.

Continue to follow Qualys Threat Protection for more coverage on the latest vulnerabilities.

References
https://calif.io/java4shell
https://openjdk.org/groups/vulnerability/advisories/2026-11-17

Author: Diksha Ojha

Senior Technical Writer

Leave a Reply

Your email address will not be published. Required fields are marked *