SentinelOne Names LevelBlue Global Delivery Partner for Wayfinder Services. Learn More

Critical Vulnerability in Java: Java4Shell (CVE-2026-114938)

A new critical vulnerability in Java was disclosed on November 17th. Specifically, there's a memory corruption bug in OpenJDK's Base64 decoder. OpenJDK is the most popular Java runtime. It is currently rated 9.2 under CVSS 4.0 and labeled CVE-2026-114938.

As a trusted security partner, LevelBlue is on heightened alert for our clients and partners and is monitoring for any suspicious activity. Should new information arise that alters this assessment, we will provide an update directly.

To speed up Base64 decoding, OpenJDK uses specialized assembly code on supported x86-64 processors. In certain circumstances, while calculating a Base64 string, the code mishandles the trailing "=" symbol and calculates a negative result. This invalid result is sent to memory, writing 62 bytes past the end of the allocated buffer and corrupting neighboring objects. Java rejects the malformed input afterward, but by then the neighboring memory has already been overwritten.

The vulnerability was discovered using human-directed AI research, with the researchers pointing AI to specific logic flows that might contain vulnerabilities. The research was conducted by Calif.

 

Impact and Exploitation Status

Because the flaw is in the Java runtime itself, an application doesn't need a bug of its own to be exposed. Any Base64 value an application decodes, such as HTTP Basic credentials, session cookies, SAML artifacts, JWTs or CSRF tokens, can carry a malicious payload.

Calif reports achieving remote code execution in default configurations of several widely used products:

  • Without authentication: Atlassian Jira and Confluence, Jenkins, Keycloak, JFrog Artifactory and PingFederate

  • With authentication: Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker

  • Sample applications built on Apache Struts and Spring Boot, plus a client-side exploit against a Java client that connects to a malicious TLS server

Calif notes these lists aren't exhaustive. Exploitation isn't one-size-fits-all, though: each target needs its own heap layout and timing, and crashing the JVM is the easier outcome. Failed attempts can crash the application, and attackers can retry. Heap memory disclosure can also expose tokens, keys and other sensitive data.

As of November 18, no exploitation in the wild has been reported, and the vulnerability isn't listed in CISA's Known Exploited Vulnerabilities (KEV) catalog. Calif has published only a reproducer that triggers the memory corruption and is withholding its product-specific exploit chains, but researchers expect working exploits to appear quickly. CISA has urged organizations to patch immediately.

Dedicated to hunting and eradicating the world's most challenging threats.

SpiderLabs

Affected Versions

Java4Shell affects OpenJDK from version 17.0.6 or newer (Java 17, 21, 25 and 27). Because they are built from OpenJDK, the following Java distributions are also vulnerable:

  • Amazon Corretto
  • Eclipse Temurin
  • Microsoft Build of OpenJDK
  • Azul Zulu
  • BellSoft Liberica
  • SAP SapMachine
  • Red Hat OpenJDK
  • Oracle OpenJDK
  • Oracle Java SE
  • Oracle GraalVM for JDK

The vulnerable code is hardware-specific and requires an x86-64 processor with AVX-512 VBMI support. ARM64 CPUs are not affected. Affected processors include Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, and AMD EPYC and Ryzen processors based on Zen 4 or newer. In AWS, this includes instance families such as c6i, m6i, c7i, c7a and m7a.

On Linux, a host is affected only if /proc/cpuinfo lists all four of the avx512f, avx512bw, avx512vbmi and bmi2 flags. Because exposure depends on the host CPU, the same container image can be vulnerable on one node and safe on another.

 

Recommended Actions and Remediation

Inventory and document every instance of Java runtime. Record the vendor, full build version, operating system, CPU architecture and owner, including containers, bundled runtimes and appliances. Prioritize internet-facing systems, identity and single sign-on services, and CI/CD systems.

Apply the Oracle security updates. According to Oracle, the following Java SE versions are affected, and fixes are available:

  • Java 17: 17.0.6 to 17.0.21 affected. Oracle fix: 17.0.21.1.
  • Java 21: up to 21.0.13 affected. Oracle fix: 21.0.13.1.
  • Java 25: up to 25.0.5 affected. Oracle fix: 25.0.5.1.
  • Java 27: up to 27.0.1 affected. Oracle fix: 27.0.1.1.
  • Java 8: Oracle lists 8u511b33-perf, its Performance Pack build, as affected. Standard Java 8 has no vulnerable decoder.
  • Not affected: Java 11 and Java 17.0.0 to 17.0.5.

For other OpenJDK distributions, apply your vendor's fixed builds as they're released. For products that bundle their own Java runtime, follow the product vendor's update guidance. Note that JDK-8321599, fixed in 17.0.11 and 21.0.3, is a different bug in the same decoder and doesn't address Java4Shell.

Restart Java applications, and rebuild and redeploy container images, so the fixed runtime is actually in use. Also update Java clients that make outbound TLS connections, since a client-side exploit has been demonstrated.

If you can't patch immediately, the researchers recommend starting the JVM with -XX:-UseBASE64Intrinsics, which disables the vulnerable code path on any architecture. Oracle and OpenJDK haven't published an official workaround, so test it before rolling it out, and recreate containers so the flag reaches the running process. Avoid two common pitfalls: -XX:UseAVX=2 prevents ARM JVMs from starting, and -XX:DisableIntrinsic=_base64_decodeBlock on its own prevents the JVM from starting at all.

 

Detection and Hunting

Where your WAF, reverse proxy, or application logs capture Base64 values (HTTP Basic credentials, SAML artifacts, CSRF tokens), inspect them after normal application parsing.

Look for any Base64-alphabet token of 32 characters or more that ends in “=” and whose length is not a multiple of 4. Start with Authorization headers. In your Application logs look for bursts of IllegalArgumentException from java.util.Base64$Decoder. In your JVM crash logs look for unexplained hs_err_pid*.log files or bursts of restarts. For a narrower filter, flag values that are at least 65 characters long including padding, whose length modulo 64 is 1, 2 or 3, and that end in one or two “=” characters.

Also watch for post-exploitation behavior: JVM processes spawning shells or other programs, unexpected outbound connections from application servers, and new or modified files such as web shells. None of these indicators proves compromise or safety on its own, and no indicators of compromise (IOCs) have been published yet.

If you believe you've been compromised, contact LevelBlue's incident response team immediately at response@levelblue.com.

About the Author

Karl Sigler is Security Research Manager, SpiderLabs Threat Intelligence at LevelBlue. Karl is a 20-year infosec veteran responsible for research and analysis of current vulnerabilities, malware and threat trends at LevelBlue. Follow Karl on LinkedIn.

About LevelBlue

LevelBlue secures what's next with intelligence-led security delivering visibility and speed to stop threats faster. As the world’s largest and most analyst-recognized pure-play managed security services provider, our AI-powered managed services and cyber expertise across managed, advisory, and incident response services help clients operate with confidence. Learn more about us.

Discover how our specialists can tailor a security program to fit the needs of your organization.

Request a Demo