Skip to content
Java4Shell Checker

CVE-2026-114938

Java4Shell Checker

Paste the output of java -version. This page compares that text with the published ranges for Java4Shell. It runs in your browser. It does not connect to your servers.

Not affiliated with Oracle or OpenJDK.

Required for a result. Paste the full command output, not just the first line if you have it.

From lscpu, /proc/cpuinfo, or the command used to start the JVM. This can show that a CPU lacks AVX-512 VBMI, or that a workaround flag is already set.

The check runs in this browser. The paste is not uploaded. Ctrl+Enter or Cmd+Enter also runs it. Unofficial tool: a result can be wrong, and it is not a scan of your systems.

Official next steps

Upgrade to a fixed build from your Java vendor. Datadog, citing Oracle, names these first fixed builds: 17.0.21.1+4, 21.0.13.1+4, 25.0.5.1+4, 27.0.1.1+4. Oracle’s download list shows the same versions without the +4 suffix. Restart the process after you replace the runtime. Check images and applications that ship a private JRE. The java on your shell path may not be the one the service uses.

If you cannot upgrade yet, the vendor advisories describe two temporary JVM flags. -XX:-UseBASE64Intrinsics disables the accelerated Base64 intrinsic and is the narrower option. On x86-64 only, -XX:UseAVX=2 (or a lower AVX level) keeps the JVM off AVX-512. Do not add UseAVX=2 on ARM64. The JVM does not recognize it there and may fail to start. Restart after you change the flags. Remove the workaround after you are on a fixed build if you do not want it left behind.

CISA also asks organizations to inventory bundled JDKs and to apply the vendor patch. This page cannot do that inventory for you. See which versions the advisories name.

How a reading is chosen

  1. JDK 8, JDK 11, anything before 17, and OpenJDK 17 builds before 17.0.6 are outside this CVE.
  2. A version at or after the fixed release for 17, 21, 25, or 27 is treated as patched. When the number is exactly that release and a +build is present, the build must be 4 or higher. That is the first fixed build Datadog names.
  3. ARM64, other non-x86-64 architectures, and 32-bit x86 are outside the path the advisories describe.
  4. A CPU flag list without avx512vbmi or avx512_vbmi is outside the path. avx512vbmi2 does not count.
  5. Otherwise an in-range version is likely affected, unless the paste clearly includes -XX:-UseBASE64Intrinsics or UseAVX set to 2 or lower.
  6. Feature releases outside that table, early-access builds, OpenJ9, and the special Java 8 perf string stay on “need more information”.

OpenJDK writes the affected boundary as 17.0.21.0.3 (and the same pattern on the other lines). Datadog writes the first fixed release as 17.0.21.1+4. A five-component .0.x build is not treated as the fix. The version page records that difference.

Questions

Is this a Java4Shell test or a scanner?

No. The only input is text you paste: java -version, and optionally CPU flags or the JVM command line. The reading happens in your browser. This site does not open a connection to a host, URL, or IP you type, and it cannot tell you whether a running service would accept a malicious request.

A version in the affected range is a reason to patch that runtime. It is not proof that a particular application is exposed.

Am I affected?

You are in the range described by the advisories when the runtime is OpenJDK 17.0.6 or later on the 17, 21, 25, or 27 lines, before the fixed build for that line, on an x86-64 CPU with AVX-512 VBMI, and the JVM was not started with a vendor workaround flag. ARM64 is outside that path. JDK 8 and JDK 11 are not in the OpenJDK risk-matrix column for this CVE.

Paste java -version for a reading of that build. Check the java that the process actually uses, including a JRE bundled in an application or a container image.

Which Java versions does this cover?

The verified table is JDK 8 and 11 (not marked for this CVE), JDK 17 from 17.0.6 until 17.0.21.1, and the 21, 25, and 27 lines until 21.0.13.1, 25.0.5.1, and 27.0.1.1. OpenJDK writes those same boundaries with an extra component, for example 17.0.21.0.3.

Read the version table

Does ARM64 or aarch64 need a workaround?

No. The vulnerable decoder is the x86-64 AVX-512 VBMI path. Do not add -XX:UseAVX=2 on ARM64. That option is not recognized there, and the JVM can fail to start.

What is AVX-512 VBMI?

It is a CPU instruction set the HotSpot Base64 decoder can use on some x86-64 processors. If your flags include avx512vbmi or avx512_vbmi, the CPU has that set. If a flags list is present and those tokens are absent, this check treats the CPU as outside the vulnerable path. The token avx512vbmi2 is a different flag and does not count.

Advisories mention processor families such as Intel Ice Lake and AMD Zen 4. This tool does not guess from a processor name. Paste the flags.

Which workaround flags do the vendors document?

-XX:-UseBASE64Intrinsics turns off the accelerated Base64 intrinsic. It is the narrower option. On x86-64 only, -XX:UseAVX=2, or a lower AVX level, keeps the JVM off AVX-512. Restart the process after you add a flag. These are temporary. The fix is a patched build.

What about Temurin, Corretto, Zulu, Red Hat, or a JDK inside an app?

Those builds come from OpenJDK and can be affected. Their package numbers do not always match Oracle’s. If the paste is clearly before the fixed release, treat it as in range and read that vendor’s advisory for the package you should install. If the number does not map cleanly, this page says so instead of guessing.

Red Hat’s bulletin was still marked ongoing on the day we read it. Confirm the errata for your RHEL or OpenJDK package.

Does the text I paste get uploaded?

No. The check runs in your browser. The paste is not sent to this site.

Is this an official Oracle or OpenJDK tool?

No. Java4Shell Checker is not affiliated with Oracle, OpenJDK, CISA, Red Hat, or Datadog. A result can be wrong. It is not a substitute for an inventory of every runtime you run, and it is not a substitute for the vendor advisory. There is no warranty.

Sources

Retrieved 18 November 2026. If a vendor page has moved since then, follow the latest advisory from that vendor.

  1. OpenJDK Vulnerability Advisory: 2026/11/17 (opens in a new tab)

    Published 17 November 2026. Risk matrix for CVE-2026-114938 and the five-component version list.

  2. CISA alert: Critical Java vulnerability (opens in a new tab)

    Released 17 November 2026. Asks organizations to inventory JDKs, including bundled runtimes, and to apply vendor patches.

  3. Datadog Security Labs: Java4Shell (opens in a new tab)

    Published 17 November 2026. Names the first fixed builds and the two temporary JVM flags.

  4. Red Hat RHSB-2026-018 (opens in a new tab)

    Updated 17 November 2026. Still marked ongoing when we read it. Describes x86-64 with AVX-512 VBMI, and the same two flags.

  5. Calif.io: Java4Shell (opens in a new tab)

    Research write-up, not a vendor and not a standards body. It is the public note that uses the Java4Shell name. The write-up is technical. This site does not reproduce it. Version decisions follow OpenJDK and Datadog’s citation of Oracle.

  6. Oracle security alerts index (opens in a new tab)

    Checked 18 November 2026. Lists Critical Security Patch Update – November 2026, revision 1, dated 17 November 2026. CISA points readers there for Oracle’s patch guidance.

  7. Oracle Java SE latest releases (opens in a new tab)

    Checked 18 November 2026. Lists current downloads Java SE 17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1.