Java4Shell: OpenJDK Vulnerability

A critical vulnerability in OpenJDK could allow unauthenticated attackers to execute code on affected Java servers.

A critical vulnerability in OpenJDK could allow unauthenticated attackers to execute code on affected Java servers.

Tracked as CVE-2026-114938 and named Java4Shell by the researchers at Calif, the flaw affects the Base64 decoder within the Java runtime. It was publicly disclosed on 17th November 2026 and could affect widely used enterprise applications, including Jira, Confluence, Jenkins and Keycloak.

What is Java4Shell?

Java4Shell is a memory-corruption vulnerability in OpenJDK’s optimised Base64 decoder. Base64 is commonly used to process encoded information, including login headers, authentication tokens, SAML messages and file uploads.

When specially crafted input reaches the vulnerable decoder, it can corrupt memory, crash the Java process and potentially allow remote code execution. Calif rates the vulnerability Critical, with a CVSS v4.0 score of 9.2. Oracle rates it High, with a CVSS v3.1 score of 8.1, reflecting its assessment of the attack complexity.

Who could be affected?

The vulnerability affects the HotSpot JVM in OpenJDK 17 (from 17.0.6), Java 21, Java 25 and Java 27, running on x86-64 processors that support the AVX-512 VBMI instruction set. This includes Intel Xeon processors from Ice Lake onwards and AMD Zen 4 or newer.

Older x86-64 processors without these instructions and ARM64 systems are not affected by this vulnerability. Virtualised environments need particular attention. A virtual machine only sees the processor capabilities exposed by its hypervisor, which means AVX-512 VBMI may not be available even where the physical host supports it.

Researchers demonstrated unauthenticated remote code execution in default configurations of Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate. Other products, including Kafka, Solr and Elasticsearch, were also affected in tested scenarios requiring authentication. Many products include their own bundled Java runtime, so checking the Java version installed on the host alone may not be sufficient. Standard Java 8 and Java 11 builds are not affected, although Oracle’s Java SE 8 Enterprise Performance Pack is an exception.

What should organisations do?

The upstream fixed versions are:

  • Java 17: 17.0.21.1
  • Java 21: 21.0.13.1
  • Java 25: 25.0.5.1
  • Java 27: 27.0.1.1

Java vendors may use different version numbers for their builds, so check the relevant supplier’s advisory.

Organisations should:

  • Identify Java runtimes across servers, applications, appliances and container images.
  • Check the actual Java version used by each application, including bundled runtimes.
  • Apply the relevant security updates and restart affected services.
  • Review temporary mitigation guidance where immediate patching isn’t possible.

There is no official workaround from Oracle or the OpenJDK project. An interim option described by Calif is the JVM flag -XX:-UseBASE64Intrinsics, which disables the optimised decoder. This should only be used temporarily and tested before deployment. There are currently no confirmed reports of exploitation in the wild, but organisations should not wait for evidence of attacks before patching.

How can AppCheck help?

Java version information is rarely exposed to the network, meaning an unauthenticated web application scan will usually not identify which runtime a server is using.

We recommend an authenticated infrastructure scan as the better starting point for identifying potentially affected Java versions. An authenticated scan can inspect Java versions installed on the host and match them against CVE-2026-114938. You can find out more about credentialed infrastructure scanning.

We’re also working on an active detection for Java4Shell and aim to make it available soon. If you know you’re running an affected Java version, patch now rather than waiting for a scan. Remember to check application-bundled runtimes and the CPU capabilities available to your JVM separately.

If you have questions or would like help understanding your exposure, please get in touch with our team.

Further reading:

Get started with Appcheck

No software to download or install.

Contact us or call us 0113 887 8380

About AppCheck

AppCheck is a software security vendor based in the UK, offering a leading security scanning platform that automates the discovery of security flaws within organisations websites, applications, network and cloud infrastructure. AppCheck are authorised by the Common Vulnerabilities and Exposures (CVE) Program as a CVE Numbering Authority (CNA)

No software to download or install.
Contact us or call us 0113 887 8380