An unpatched Java release
Unpatched OpenJDK 17.0.6 onwards, including 21, 25 and 27. Vendor products with backported decoder code can differ; see the Java 8/11 exceptions below.
Check versions →Java4Shell (CVE-2026-114938) is a flaw in Java’s decoder for Base64, a common way to represent data as text. In an affected application, specially crafted input can expose information, cause a crash or let an attacker run code. [1]
Core advisories reviewed . Check vendor notices for newer releases.
Unpatched OpenJDK 17.0.6 onwards, including 21, 25 and 27. Vendor products with backported decoder code can differ; see the Java 8/11 exceptions below.
Check versions →The shortcut needs x86-64 with AVX-512 VBMI. Native ARM64 Java is outside this hardware scope. Use the processor features available to the service itself, including inside a virtual machine.
Inspect CPU flags →Login credentials, tokens and uploads may be decoded before a user signs in. A login screen alone is not protection. Java clients can also process hostile server data.
Researcher examples ↗8u511b33-perf as affected; Prime has affected Java 8 and 11 builds. Prime fixes → [2] [3] [10]Calif reports pre-login code execution in: Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate. It also reports post-login attacks against Kafka Broker, Solr, Elasticsearch, Gerrit and Spinnaker.
This is a researcher test list, not a complete product/version matrix. A product name alone does not determine exposure. Check its runtime, hardware and vendor advisory. Read the demonstrations ↗
Match the vendor and full build. Oracle’s version numbers do not apply to every distribution.
Swipe or scroll the table to compare vendors.
| Java line | Oracle Java SE | Eclipse Temurin |
|---|---|---|
| 17 | 17.0.21.1+4 ↗ | 17.0.21.1+2 ↓ |
| 21 | 21.0.13.1+4 ↗ | 21.0.13.1+2 ↓ |
| 25 | 25.0.5.1+4 ↗ | 25.0.5.1+2 ↓ |
| 27 | 27.0.1.1+4 ↗ | 27.0.1.1+4 ↓ |
Adoptium has announced fixed builds; release publication is in progress. Packages are updated alongside the binaries; container images follow completion of a Java line’s binaries. A fixed version number does not mean every platform’s download is ready.
Read Adoptium’s announcement ↗ · Check downloads ↗ · Platform release tracker ↗
Oracle Java 8 Enterprise Performance Pack: the fixed release is 8u513-perf. Standard OpenJDK 8 and 11, including Temurin, are outside the published affected release lines. GraalVM users should follow Oracle’s product advisory.
Oracle lists 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3 and 8u511b33-perf. These are its listed supported builds, not the full historical affected range. Earlier builds may also be affected. Oracle source →
Prime is separate from Azul Zulu. Its affected builds include Java 8 and 11. Azul lists Stable releases 26.08.110.0 and 26.02.510.0 with the fix; match your supported release stream rather than comparing their numbers with ordinary JDK builds.
The vendor and product notices below were checked at 16:41 UTC. Other distribution channels retain the earlier review noted below.
Unsupported intermediate Java releases need vendor review or migration to a supported fixed release. For bundled Java, update through the application vendor. Draft a vendor enquiry →
Installing a Java update does not replace the Java already running inside an application. Restart every affected instance, or deploy new containers, then confirm the running version. For bundled Java, use the application vendor’s supported update path.
jcmd <PID> VM.versionReplace <PID> with the Java process ID. Use an available JDK tool with permission to inspect that process, in its execution environment. Record the full vendor/build. jcmd manual ↗
java -versionRun the actual service’s Java executable, inside its container if applicable. Your shell’s default Java may be different.
grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'Calif’s check requires all four flags. A failed command is inconclusive. Check each execution environment; a cloud family name alone is insufficient. Source ↗
jcmd <PID> VM.flags -allReplace <PID> with the service’s Java process ID. With an available JDK tool and appropriate process permissions, check that UseBASE64Intrinsics = false. Otherwise use your vendor’s runtime diagnostics. jcmd reference ↗
-XX:UseAVX=2 disables AVX-512 more broadly. Do not apply it to ARM JVMs: they may fail to start. Red Hat recommends the narrower Base64 flag. ↗
A proxy or WAF rule is not a universal substitute for fixing the runtime. Avoid running crash-triggering proof-of-concept tests on production. Exploit limitations ↗
Progress lasts only for this visit unless you choose to remember it. Untick that option or clear the checklist to delete saved progress. Progress is not saved without JavaScript. This checklist does not verify your systems. Vendor mitigation guidance ↗
Using an app rather than operating a service? Read the app-user steps →
An affected decoder can write past the memory reserved for its output. Compare the faulty path with a patched runtime or the temporary workaround.
Shown here: untrusted Base64 reaches an affected runtime on matching x86-64 hardware. Check the full conditions →
Conceptual diagram. Blocks are not byte counts or a map of a particular application.
Memory corruption can cause a crash or expose data. Code execution needs further application-specific conditions; an overwrite does not automatically give an attacker control.
The OpenJDK fix checks short final fragments before the faulty calculation and leaves them to ordinary Java handling. The harmful write is avoided. Find your vendor’s fixed build →
With UseBASE64Intrinsics = false active in the running service, ordinary decoding remains available and the affected accelerated path is not used. Keep the permanent patch planned. Apply and verify the workaround →
An app decodes untrusted Base64, sometimes before it checks a login. Java reserves space for the decoded result.
A malformed ending can make the accelerated decoder calculate a negative length. Its write mask then permits a full block.
The write can cross the result buffer’s boundary. Java may reject the input afterwards, but the memory damage has already happened.
Based on Calif’s analysis, the OpenJDK fix and Red Hat’s mitigation guidance.
Calif has demonstrated remote code execution. The sources reviewed for this guide do not establish real-world exploitation activity. That uncertainty is not a reason to delay mitigation. A research demonstration, a public proof of concept and a confirmed incident are different kinds of evidence. Research evidence ↗
No. Java4Shell concerns the Java runtime’s Base64 implementation. A Log4j update does not replace the affected JVM. Follow your Java or application vendor’s fix for CVE-2026-114938. OpenJDK advisory ↗
A container can still use an affected JVM and expose the host’s CPU features. Data may be decoded before authentication. Calif says request buffering stops some demonstrated chains, but not all. Assess the running service and patch its runtime. Red Hat ↗ Calif’s limitations ↗
Use the checker to interpret diagnostic output, or adapt a prompt for your own follow-up work.
Paste Java version or diagnostic output. The checker identifies the build, reads any CPU and JVM settings, and compares them with the published guidance.
Use output from the service’s own host, VM or container. Text is processed in this tab; it is not uploaded or saved.
Run these commands where the service runs, including inside its container, as the user that owns the Java process. They read settings; they do not change the service.
jcmd -lThe number before your application’s name is its process ID. For a container, list processes inside that container. If jcmd is unavailable, paste the service’s java -version output for a first check, or use your vendor’s diagnostics.
Enter the process ID to prepare the command.
Paste the results into the same box above and check again. Add output for the same process; clear the box before checking another service. The command filters properties so you do not need to share full logs or environment settings.
Six templates help you review a service, plan an update or prepare a message. Edit the details before copying; verify the advice against vendor evidence.
Public disclosures and vendor release notices. Times are shown only when stated by the source; other same-day events are not ordered by time.
Adoptium’s release-status update reports more platform builds awaiting completion. Check the tracker for actual availability; the estimated completion window is not a release confirmation. Status update ↗
Its notice explains separate mitigation for the server and Operator JVMs. It cannot yet recommend a specific fixed Keycloak image. The time shown is the advisory’s update time. Keycloak advisory ↗
Adoptium publishes the fixed versions, with downloads appearing as platform testing completes. Packages and container images need their own availability checks. Announcement ↗
November updates address Java4Shell. Prime’s fixed Stable releases are 26.08.110.0 and 26.02.510.0, including its Java 8 and 11 lines. Core notes ↗ Prime notes ↗
Calif describes Java4Shell, its hardware requirements and application-specific attacks. Disclosure ↗
Calif gives this release time; Oracle’s release notes confirm the date. OpenJDK publishes its vulnerability advisory. Release time ↗ Fixed builds ↗
Its CVE tracker records fixed packages in supported channels. Package tracker ↗
Technical claims use original research and vendor documents. Community discussion informs the questions this guide answers.
Published by After Dinner Software; independent of the researchers and Java vendors. This guide summarises the linked primary sources and keeps confirmed fixes separate from unresolved vendor status. Core scope and the Oracle, Temurin, Red Hat, Amazon Linux, Azul, Keycloak and Atlassian notices were rechecked at 16:41 UTC. Microsoft, Liberica and SapMachine links retain their earlier 10:30 UTC review qualification. This is a dated snapshot. Verify the current notice for your exact build before acting.
Substantive changes to this guide, with their supporting sources. Subscribe by RSS ↗
Added Prime’s affected Java 8/11 lines and separate Stable fixes. Updated the response sheet, AI prompts and checker to preserve that distinction. Added Keycloak product guidance and the dated Azul and Temurin release events.
Azul Prime fix notice ↗Added Temurin’s announced fixed builds alongside Oracle’s. Temurin uses +2 for Java 17, 21 and 25, while Oracle uses +4. Availability still depends on platform and delivery channel. Core exposure and mitigation advice was rechecked.
Adoptium guidance ↗Checked the exposure conditions, Oracle fixes and Java 8 Performance Pack exception. Added running-process verification, vendor channels and the limits of the researcher demonstrations.
Research and vendor sources →