Java4Shell: affected versions and fixes

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.

Affected systems

The flaw is in an accelerated decoder: a faster way Java processes Base64 text. The documented attack needs all three conditions below, with that shortcut enabled. [1] [4]

Runtime

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 →
Hardware

Certain Intel or AMD processors

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 →
Input

Attacker-supplied data reaches Java

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 ↗
Java 8 / 11: Standard OpenJDK 8 and 11 are not marked affected by this CVE. Oracle Java 8 Enterprise Performance Pack and Azul Prime (formerly Zing) are exceptions. Oracle lists 8u511b33-perf as affected; Prime has affected Java 8 and 11 builds. Prime fixes → [2] [3] [10]
Which applications have been demonstrated?

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 ↗

Vendor patches

Match the vendor and full build. Oracle’s version numbers do not apply to every distribution.

Confirmed fixed builds

Oracle & Temurin · checked 16:41 UTC

Swipe or scroll the table to compare vendors.

Java4Shell fixed builds by Java vendor and release line
Java lineOracle Java SEEclipse Temurin
1717.0.21.1+4 ↗17.0.21.1+2 ↓
2121.0.13.1+4 ↗21.0.13.1+2 ↓
2525.0.5.1+4 ↗25.0.5.1+2 ↓
2727.0.1.1+4 ↗27.0.1.1+4 ↓

Temurin: check your platform and delivery channel

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.

Which affected Oracle builds are listed?

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 →

Azul Prime / Zing: check its own release number

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.

Prime fix notice ↗ · Prime release notes ↗

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 →

Restart and verify

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.

Inspection commands and mitigation verification

Check the actual running JVM

jcmd <PID> VM.version

Replace <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 ↗

Identify an installed Java executable

java -version

Run the actual service’s Java executable, inside its container if applicable. Your shell’s default Java may be different.

Inspect Linux CPU flags

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 ↗

Verify the restarted JVM

jcmd <PID> VM.flags -all

Replace <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 ↗

Alternative flag: x86-64 only

-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 ↗

Optional: track your response in this browser

0 of 4 steps checked

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 →

How the attack works

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 →

The affected decoder writes beyond the output boundary into neighbouring memory.

Conceptual diagram. Blocks are not byte counts or a map of a particular application.

Affected: the write escapes its buffer

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.

Patched: the edge case is handled safely

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 →

Workaround: bypass the affected decoder

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 →

Why the unpatched path fails

  1. Text reaches Java

    An app decodes untrusted Base64, sometimes before it checks a login. Java reserves space for the decoded result.

  2. The final write is miscalculated

    A malformed ending can make the accelerated decoder calculate a negative length. Its write mask then permits a full block.

  3. Neighbouring memory is overwritten

    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.

Questions and current limits

Is it being exploited in the wild?

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 ↗

Why do severity scores differ?

Calif reports 9.2 under CVSS 4.0. Oracle and OpenJDK report 8.1 under CVSS 3.1. These use different scoring versions and assessments; neither score determines your application’s exposure. Calif ↗ Oracle ↗

Is this Log4Shell? Will updating Log4j fix it?

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 ↗

Do containers, a login page or a proxy make me safe?

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 ↗

Optional tools

Use the checker to interpret diagnostic output, or adapt a prompt for your own follow-up work.

Check your Java outputGet a build assessment and a specific next step

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.

Get output from a running service

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.

1. Find your service’s Java process

jcmd -l

The 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.

2. Read only the details this checker needs

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.

Need help gathering evidence? Customise an AI prompt →

Customisable AI prompts

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.

Disclosure and patch timeline

Public disclosures and vendor release notices. Times are shown only when stated by the source; other same-day events are not ordered by time.

  1. Temurin rollout remains in progress

    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 ↗

  2. Advisory updated

    Keycloak gives server and Operator guidance

    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 ↗

  3. Temurin announces fixed builds

    Adoptium publishes the fixed versions, with downloads appearing as platform testing completes. Packages and container images need their own availability checks. Announcement ↗

  4. Azul releases Core and Prime fixes

    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 ↗

  5. Public disclosure and research demonstrations

    Calif describes Java4Shell, its hardware requirements and application-specific attacks. Disclosure ↗

  6. 13:00 Pacific

    Oracle’s patch release

    Calif gives this release time; Oracle’s release notes confirm the date. OpenJDK publishes its vulnerability advisory. Release time ↗ Fixed builds ↗

  7. Time not specified

    Amazon Linux lists Corretto fixes

    Its CVE tracker records fixed packages in supported channels. Package tracker ↗

Sources and review notes

Technical claims use original research and vendor documents. Community discussion informs the questions this guide answers.

  1. 01Calif · original researchAttack conditions, demonstrations, mitigation and reported patch time ↗
  2. 02OpenJDK · 17 November advisoryCVE-specific affected release lines and CVSS 3.1 score ↗
  3. 03Oracle · November security updateAffected Oracle and GraalVM builds, including Java 8 Performance Pack ↗
  4. 04Red Hat · Java4Shell bulletinHardware scope, mitigations and product update guidance ↗
  5. 05Oracle · Java 27 release notesJava 27 fixed build and release date; other Java lines linked in the version table ↗
  6. 06Amazon Linux · CVE package trackerCorretto package status and advisory links by OS channel ↗
  7. 07Azul · CVE and fixed-version matrixZulu build numbers by Java line and update stream ↗
  8. 08Oracle · runtime diagnostics manualjcmd process requirements and VM.version and VM.flags inspection ↗
  9. 09Adoptium · Temurin patch guidanceVendor-specific fixed builds and publication progress; reviewed 16:41 UTC ↗
  10. 10Azul Prime · November CVE fixesProduct-specific fixes, including the Java 8 and 11 exception ↗
  11. 11Keycloak · product advisoryServer and Operator mitigation, image status and update time ↗
  12. 12OpenJDK · decoder fixEarly handling of short final fragments in the accelerated decoder ↗

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.

Guide updates

Substantive changes to this guide, with their supporting sources. Subscribe by RSS ↗

Azul Prime exception and vendor events added

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 ↗

Temurin fixed builds added

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 ↗

Initial vendor and response review

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 →