Java4Shell OpenJDK Base64 flaw: who is affected (CVE-2026-114938)
At a glance
| Severity | HIGH |
|---|---|
| CVSS | CVE-2026-114938: 8.1 |
| In CISA KEV (exploited) | No |
| Vendor | Jira |
| CVE IDs | CVE-2026-114938 |
Primary-source details
- CVE-2026-114938: CVSS 8.1 (High), per NVD; a fixed version has not been published.
Java4Shell (CVE-2026-114938) is a memory-corruption flaw in the Base64 decoder of OpenJDK-based Java builds that lets an unauthenticated attacker crash a Java server and, with considerable effort, run code on it. Oracle and OpenJDK shipped fixes on Tuesday, and The Hacker News reports that there is no evidence of exploitation in the wild so far, although CISA has urged immediate patching.
The Java4Shell vulnerability only fires on x86-64 hosts whose CPU exposes AVX-512 VBMI, so the first job is working out which of your servers actually qualify.
What happened
Researchers at Calif, who named the bug Java4Shell, found that an optimised x86-64 code path used to decode Base64 can write past the end of its output buffer when it receives a malformed string ending in an extra =. Java rejects the input, but only after the out-of-bounds write has happened. Calif says the trigger is as small as 64 A characters followed by one = (128 on older OpenJDK 17), as Help Net Security relays.
Servers decode Base64 constantly: HTTP Basic credentials, SAML artifacts, CSRF tokens and MIME encoded words all pass through it, often before authentication is checked. That is why a remote attacker with no account can reach the flaw. According to The Hacker News, the bytes written past the buffer are fixed, so the attacker controls only where they land, which is why early analysis pointed to a crash rather than code execution.
Calif says it nonetheless built working attacks by grooming the heap so the overflow enlarges a neighbouring array, then using it to read and write memory. It is holding back its attack code. Other labs have reproduced crashes and a memory leak but, as reported, not code execution.
Am I affected?
Oracle lists these Java SE builds as affected: 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3. Oracle GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3, and GraalVM Enterprise Edition 21.3.20.0.3, are also listed. Several reports describe the issue as present in OpenJDK from 17.0.6 onward.
Exposure depends on more than the Java version. The Keycloak team’s guidance, as quoted by The Hacker News, treats an instance as at risk when all of these hold:
- It runs an unpatched OpenJDK build from 17.0.6 onward, including unpatched 21 and 25 builds.
- The x86-64 host or virtual machine exposes the
avx512vbmiCPU feature to Java. - The JVM has Base64 intrinsics enabled and has not been limited to AVX2 with
-XX:UseAVX=2.
ARM64 CPUs are not affected, according to Calif. VulnCheck, cited by Help Net Security, says CPUs without AVX-512 VBMI and BW fall back to a decode path that does not contain the defect.
Applications Calif says it exploited without a login under default settings: Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate. With a login: Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker. Calif also demonstrated code execution in sample Apache Struts and Spring Boot applications and says its lists are incomplete.
Technical details
NVD records a CVSS 3.1 base score of 8.1 (high) with the vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H: network reachable, no privileges, no user interaction, but high attack complexity. Oracle describes the component as the compiler and the weakness as an out-of-bounds write that can cause denial of service or code execution.
The difficulty is real. There is no universal exploit; each target needs its own memory layout and timing, and some attacks are sensitive to network latency. A proxy that waits for complete requests, as nginx does by default, blocks some attacks but not all. A failed attempt can crash the JVM, and an attacker can often retry. Crashing an affected JVM is trivial, VulnCheck found, and repeated requests can keep a service down.
Fix status differs by vendor. Amazon has fixed its Corretto builds, while Red Hat was still preparing fixes for its own builds at the time of reporting. Keycloak has published temporary mitigations until patched container images are available, and notes that its x86-64 images tagged 26.8.2-1 and 26.8.2-2 bundle an affected OpenJDK 21.0.13 build.
Why this matters
Analysis: For most environments the realistic near-term risk is denial of service against internet-facing Java services on AVX-512 capable hardware, which includes many cloud instance types. Remote code execution is demonstrated by the researchers but needs per-application tuning, so it is a lower-volume threat until public exploit code appears. Identity providers, CI servers and artifact repositories deserve the earliest attention because compromise there has outsized consequences.
Treat this as a patch-within-days item for exposed systems, and move it to hours if exploitation is reported.
Detection and hunting ideas
- Look for JVM crashes or unexplained restarts on Java services, especially following requests with unusually long, malformed Base64 values in Authorization headers, SAML parameters or tokens.
- Alert on repeated authentication requests from one source that precede a crash, since failed attempts can crash Java and be retried.
- Inspect the abnormal process activity of Java service accounts after any crash, such as new child processes.
How to fix Java4Shell: what to do
- Inventory Java runtimes, including those bundled inside applications and container images, and note which hosts expose
avx512vbmi. Keycloak suggests:grep -m1 '^flags' /proc/cpuinfo | grep -qw avx512vbmi && echo 'AVX-512 VBMI available'. No output means the CPU does not expose the feature. - Apply the Oracle or OpenJDK update, or your distribution’s patched build, and restart the services. Prioritise internet-facing identity, CI and repository servers.
- Where a vendor build is not yet patched, such as Red Hat at the time of reporting, follow that vendor’s interim guidance. Keycloak’s guidance includes limiting the JVM to AVX2 with
-XX:UseAVX=2. - Rebuild container images that bundle an affected OpenJDK, since the image tag alone does not tell you whether you are exposed.
- Keep reverse proxies that buffer complete requests in front of Java services as a partial hurdle, not a fix.
- Watch for public exploit code and for any vendor or CISA update on exploitation, and brief your incident response team.
Related coverage
Sources
- NVD: CVE-2026-114938
- The Hacker News: Java4Shell enables pre-auth RCE
- The Hacker News: CISA urges immediate patching
- Help Net Security: Java4Shell exploitation is tricky
