Skip to content
Java4Shell Checker

Which Java versions are affected

CVE-2026-114938 is an out-of-bounds write in OpenJDK’s optimized Base64 decoder, on the x86-64 AVX-512 VBMI path. The ranges below are the ones we could verify on 18 November 2026. They are not a guess at every vendor’s package number.

Version boundaries retrieved 18 November 2026 from the OpenJDK advisory and from Datadog’s citation of Oracle.
LineAffected rangeFirst fixed buildOpenJDK wording
8Not marked for this CVE—8u512 is named for other fixes in the same advisory
11Not marked for this CVE—11.0.33 is named for other fixes in the same advisory
1717.0.6 through versions before 17.0.21.117.0.21.1+417.0.21.0.3 and earlier
21All Java 21 versions before 21.0.13.121.0.13.1+421.0.13.0.3 and earlier
25All Java 25 versions before 25.0.5.125.0.5.1+425.0.5.0.3 and earlier
27All Java 27 versions before 27.0.1.127.0.1.1+427.0.1.0.3 and earlier
Other feature releasesNot in the verified tableNo verified fixed releaseNot listed

Two ways of writing the same boundary

The OpenJDK advisory says the affected versions are 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3, and earlier. That sentence also names 11.0.33 and 8u512, but the risk matrix does not put a mark in the JDK 8 or JDK 11 column for CVE-2026-114938. Those two lines are in the advisory because it fixes other issues as well.

Datadog, citing Oracle, names the first fixed builds as 17.0.21.1+4, 21.0.13.1+4, 25.0.5.1+4, and 27.0.1.1+4. Oracle’s Java SE release list, checked the same day, shows 17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1 as current downloads.

This checker treats a build as patched only when it is at or after the Datadog/Oracle release. 17.0.21.0.3 sorts before 17.0.21.1, so it stays in the affected range. A fifth component higher than 3, with the patch component still 0, is still below 17.0.21.1 and is not called patched. If your vendor uses a package number that does not follow either style, do not force it into this table. Read that vendor’s advisory.

How to read java -version

Use the quoted version and the (build …) string. A Temurin line such as Temurin-17.0.13+11 and a Corretto line such as Corretto-17.0.13.11.1 are the same JDK update, 17.0.13, with a vendor suffix. The extra Corretto digits are not Oracle’s patch level.

On Java 8 the last line often says build 25.401-b10. That is the HotSpot engine build, not Java 25. The version in quotes, 1.8.0_401, is the one that matters.

CPU and architecture

The bug is in an x86-64 decoder that uses AVX-512 VBMI. ARM64 and aarch64 do not run that path. Neither do ppc64le, s390x, or riscv64. A 32-bit x86 JVM is also outside the 64-bit path the advisories describe.

If the CPU flags include avx512vbmi or avx512_vbmi, the processor has the instruction set. If a flags list is present and those tokens are absent, the vulnerable path is not available. avx512vbmi2 is a different flag. This page does not infer VBMI from a processor marketing name.

Vendor builds

Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK, BellSoft Liberica, SAP Machine, Oracle Java SE, GraalVM, and the Red Hat build of OpenJDK are built from OpenJDK. A version that is clearly before the fixed release should be treated as in range. A version that is clearly at or after it is treated as patched, with a reminder to confirm the vendor actually shipped that fix.

Red Hat’s bulletin RHSB-2026-018 was still marked ongoing when we read it on 18 November 2026. Distribution packages on Ubuntu, Debian, and Alpine can display an upstream version while the package revision lags. Eclipse OpenJ9 and IBM Semeru are a different JVM. This checker does not map them onto the HotSpot table.

One research write-up says Oracle listed a special Java 8 build, 8u511b33-perf. The OpenJDK matrix does not mark ordinary JDK 8. If your version string is that perf build, the checker stops and points you at Oracle instead of calling it safe.

Scores also differ, and this page does not pick one. OpenJDK prints CVSS v3.1 8.1. Datadog and the Calif write-up print CVSS v4.0 9.2. CISA and Red Hat describe the impact as critical. The version reading does not depend on the score.

What a version string cannot show

A patched number on your shell does not mean every JVM on the machine is patched. Services often ship their own runtime. A version in range also does not, by itself, say that a given application decodes untrusted data with the JDK decoder. The advisories describe that condition. This site does not test it, and it does not contact your hosts.

Check a java -version paste

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.