Tested

Java4Shell (CVE-2026-114938): is your JDK or Docker image patched?

Java4Shell is a memory-corruption flaw. The tables cover fixed Java 17, 21, 25 and 27 builds and the Docker image tags we checked.

Next step. Run java -version where your workload runs. Match the vendor and full build to its advisory.

Who is affected, per the sources

QuestionWhat the source saysSource
Which lines?The advisory's risk matrix marks 17, 21, 25 and 27 for CVE-2026-114938, and leaves 8 and 11 unmarked.OpenJDK advisory
Which component?hotspot/compiler. CVSS 3.1 base score 8.1 (vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).OpenJDK advisory, CVE record
What hardware?Adoptium: "The CPU on the affected system must support the AVX-512 VBMI instruction set for it to be affected." Red Hat: "x86-64 systems whose CPU supports the AVX-512 VBMI instruction set"; exploitation "requires an x86-64 processor providing the avx512f, avx512bw, avx512vbmi, and bmi2 features". Red Hat and Amazon Linux both say the code was introduced in OpenJDK 17.0.6. The OpenJDK advisory and Oracle's alert do not mention the CPU.Adoptium post, Red Hat CVE page, Amazon Linux CVE page
Potential impactOracle rates attack complexity high and says a successful attack can take over the affected Oracle Java product. Red Hat rates it Critical and says "public research has demonstrated working exploits against multiple widely deployed Java applications in their default configurations".Oracle alert and CVE record, Red Hat CVE page
CVSS base scoresOracle reports 8.1 (v3.1), Red Hat 9.8 (v3.0), and Amazon Linux 8.8 (v3).CVE record, Red Hat, Amazon Linux
JDK 8 and 11Adoptium and Red Hat say 8 and 11 are not affected. Oracle's CVE record lists one Java SE 8 build, 8u511b33-perf. The OpenJDK advisory marks neither line.Adoptium post, Red Hat, CVE record
Other feature releasesAmazon Linux lists its Corretto 22, 23, 24 and 26 packages as "No Fix Planned". Ubuntu lists openjdk-26 on resolute as "needs-triage". The fixed builds on this page are for 17, 21, 25 and 27 only.Amazon Linux CVE page, Ubuntu CVE page

This page does not describe how the flaw is triggered.

Fixed versions by vendor

This is a dated snapshot. Check the linked advisories and registries for current status. Each cell reflects what the linked page said on 19 November 2026 unless a later read is noted. The original read times are in the Sources list. "No statement found" means the page was read and says nothing about that line.

Vendor or image2725211711 and 8
Eclipse Temurin27.0.1.1+4 on Linux x64, Linux ppc64le, Alpine x64 and macOS aarch64; not yet for Windows x64 or Linux aarch6425.0.5.1+2, including Alpine aarch64 and Linux ppc64le; not yet for Windows x64, macOS x64 or Linux aarch6421.0.13.1+2; not yet for Windows x64, macOS x64 or Linux aarch6417.0.21.1+2, including macOS x64; not yet for Windows x64 or Linux aarch64"not affected" (Adoptium)
Amazon Correttofixed in Amazon Linux packages (ALAS)25.0.5.1.2 (changelog)21.0.13.1.2 (changelog)17.0.21.1.2 (changelog)Amazon Linux lists Corretto 11 and 8 "Not Affected" (ALAS)
Azul Zulu27.0.1.1+425.0.5.1+221.0.13.1+217.0.21.1+2the notes' CVE-2026-114938 row lists 27, 25, 21 and 17 only
BellSoft Liberica27.0.1.1+525.0.5.1+521.0.13.1+617.0.21.1+6BellSoft's November advisory says the vulnerability "affects Java versions 17 and up"
Microsoft Build of OpenJDKno statement found25.0.5.1 (release/jdk-25.0.5.1_2)21.0.13.1 (release/jdk-21.0.13.1_2)17.0.21.1 (release/jdk-17.0.21.1_2)no statement found
Oracle JDK27.0.1.1 (build 27.0.1.1+4)25.0.5.1 (build 25.0.5.1+4)21.0.13.117.0.21.1The CVE record lists Java SE 8u511b33-perf as affected.
Red Hat build of OpenJDKno statement found25.0.5.1 (portable)21.0.13.1 (portable)17.0.21.1 (portable)"Not affected" for 11 and 8
Red Hat Enterprise Linuxno statement foundRHEL 9 and 10: java-25-openjdk 25.0.5.1.2 (RHSA-2026:100571, 100572)RHEL 8, 9, 10: 21.0.13.1.2 (RHSA-2026:100567, 100568)RHEL 8, 9: 17.0.21.1.2 (RHSA-2026:100563, 100564)"Not affected"
Debiansid 27.0.1.1+4-1trixie (security) 25.0.5.1+2-1~deb13u1 fixed (DSA-6640-1); forky still "vulnerable"trixie (security) 21.0.13.1+2-1~deb13u1 fixed (DSA-6639-1); forky still "vulnerable"bookworm (security) 17.0.21.1+2-1~deb12u1 fixed per DLA-4917-1; sid 17.0.21.1+2-1 fixednot listed as affected
Ubuntustonking and upstream: 27.0.1.1+4-125.0.5.1+2-1~24.04.1 on noble (jammy, resolute, stonking also released)21.0.13.1+2-1~24.04.1 on noble (focal to stonking released)17.0.21.1+2-1~24.04.1 on noble (bionic to stonking released)openjdk-8: "not-affected" ("17+ only")

Temurin platforms are from the Adoptium API at 01:13 UTC on 20 November; Adoptium publishes each platform as its testing completes, so check again before you rely on a "not yet". Oracle released 27.0.1.1, 25.0.5.1, 21.0.13.1 and 17.0.21.1 on 17 November. Each release note links the Java fixes appendix of Oracle's November alert (25.0.5.1 release notes); the notes do not name CVE-2026-114938 themselves. The CVE record lists 27.0.1.0.3, 25.0.5.0.3, 21.0.13.0.3 and 17.0.21.0.3 as the affected versions.

Links for the rows above: Azul November 2026 notes, BellSoft November advisory, Liberica releases, Microsoft release notes, Oracle alert, Red Hat CVE page, Debian tracker, Ubuntu CVE page.

Red Hat's page also lists these products as "Affected" with no fixed version yet: Red Hat Build of Keycloak, OpenShift Pipelines, JBoss EAP 7 and 8 images, the Quarkus native builders, Red Hat Hardened Images, the ubi10/openjdk-21 container build, and java-25-openjdk-windows. Oracle's CVE record also lists Oracle GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3, and GraalVM Enterprise Edition 21.3.20.0.3, as affected.

Docker images

ImageObservations (linux/amd64 images, UTC)
eclipse-temurinOn 19 November at 18:23 UTC, the newest versioned JDK tags in the Docker Hub results we checked included 25.0.5_8-jdk-noble, 21.0.13_9-jdk-noble and 17.0.21_9-jdk-noble. Tags for the fixed builds (25.0.5.1_2-jdk, 21.0.13.1_2-jdk, 17.0.21.1_2-jdk, 27.0.1.1_4-jdk) returned 404 on Docker Hub at 18:07 and 18:23 UTC on 19 November, and again at 01:13 UTC on 20 November. We ran the JDKs extracted from those three -jdk-noble images. Their java -version output was Temurin-25.0.5+8, Temurin-21.0.13+9 and Temurin-17.0.21+9, respectively. All three precede the fixed Temurin builds. On 19 November an Adoptium maintainer wrote that Docker's rules required every platform to be published before the images update; later that day a Docker Official Images maintainer wrote that this had been relaxed to get the releases out faster (adoptium-support#1575, open). The fixed tags can appear at any time, so check the tag list again.
amazoncorrettoOn 19 November at 18:36 to 18:37 UTC, the JDK release file in amazoncorretto:25, :21 and :17 named Corretto-25.0.5.1.2, Corretto-21.0.13.1.2 and Corretto-17.0.21.1.2, the fixed builds.
tomcat, mavenOn 19 November at 18:36 to 18:37 UTC, maven:3-amazoncorretto-25 carried Corretto-25.0.5.1.2 (fixed). tomcat:11-jdk25-temurin-noble and maven:3-eclipse-temurin-25 carried Temurin-25.0.5+8, not the fixed build. Other tags of these images were not checked; check the full Java build in the exact image you deploy.
bellsoft/liberica-*Not an official Docker image. bell-sw/Liberica#248 (open) reports that on 19 November the Docker Hub 25-cds tag still pointed at 25.0.5.0.3.
distroless java*On 19 November at 18:36 to 18:37 UTC, gcr.io/distroless/java25-debian13, java21-debian13 and java17-debian13 (latest) carried Temurin-25.0.5.1+2, Temurin-21.0.13.1+2 and Temurin-17.0.21.1+2, the fixed builds. java21-debian12:latest carried Temurin-21.0.10+7 and java17-debian12:latest carried Debian's 17.0.18+8, neither fixed. The debian13 Java images use Temurin. The distroless status table lists arm64 and riscv64 builds and the 17 ppc64el build as pending, and the 25 ppc64el build as awaiting its package (distroless#2258, read 18:36 UTC on 19 November and 01:13 UTC on 20 November).

Until your vendor ships

If you cannot update Eclipse Temurin yet, Adoptium recommends adding -XX:-UseBASE64Intrinsics to the JVM startup options as an interim mitigation. Upgrade when a fixed build is available for your platform. If you run x86-64 containers and can change the base image, the distroless java*-debian13 and amazoncorretto images in the table above already carried fixed builds when we read them.

On 19 November 2026, all six Temurin builds below accepted the option at startup on an x86-64 test host without AVX-512 VBMI. For the three versioned -jdk-noble rows, we ran the JDKs extracted from the images in a test container. These tests measured startup and option state. Mitigation effectiveness remains untested here.

java -XX:+PrintFlagsFinal -version | grep -i base64
# bool UseBASE64Intrinsics = true {product} {default}
java -XX:-UseBASE64Intrinsics -version        # exit 0
JAVA_TOOL_OPTIONS=-XX:-UseBASE64Intrinsics java -version
# Picked up JAVA_TOOL_OPTIONS: -XX:-UseBASE64Intrinsics   (exit 0)

This Temurin example checks JVM startup with the option. Preserve any existing JVM options when applying it in your deployment.

docker run --rm -e JAVA_TOOL_OPTIONS=-XX:-UseBASE64Intrinsics eclipse-temurin:25-jdk java -version
Image sourcejava -versionFlag listed asDefault with this flag unsetNeeds -XX:+UnlockDiagnosticVMOptions
eclipse-temurin:25.0.5_8-jdk-noble25.0.5+8{product}trueno
eclipse-temurin:21.0.13_9-jdk-noble21.0.13+9{product}trueno
eclipse-temurin:17.0.21_9-jdk-noble17.0.21+9{product}falseno
older pull of eclipse-temurin:25-jdk (August build)25.0.4.1+1{product}trueno
older pull of eclipse-temurin:21-jdk (August build)21.0.12.1+1{product}trueno
older pull of eclipse-temurin:17-jdk (August build)17.0.20.1+1{product}falseno

The 17 default is false on this host. We did not test whether it is false on other CPUs, so on 17 check -XX:+PrintFlagsFinal on the machine that runs your workload. None of the six builds in this table is a fixed build. Setting the flag to false also needs a restart of every JVM that should pick it up. Nothing we found measures the speed cost.

Does this CPU have AVX-512 VBMI?

This Linux command lists the named CPU features exposed to the running system.

grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'

On our x86-64 test host the command printed only bmi2. Adoptium and Red Hat identify AVX-512 VBMI as a condition. Red Hat excludes ARM64 and x86-64 CPUs without AVX-512 VBMI. The OpenJDK advisory and Oracle alert leave hardware conditions unspecified. A VM can expose fewer CPU features to its guest. Check hardware scope and build status in your vendor's advisory.

Which build do you run?

java -version

Look for the vendor and full build in the output. In the eclipse-temurin:25.0.5_8-jdk-noble JDK we checked, it printed OpenJDK Runtime Environment Temurin-25.0.5+8 (build 25.0.5+8-LTS), which is not the fixed build; the fixed Temurin build is 25.0.5.1+2. A .1 on its own does not mean fixed: Temurin's August builds were 25.0.4.1+1, 21.0.12.1+1 and 17.0.20.1+1. For a container, use the image's documented method to run java -version, or read the Java runtime's release file from the exact image and architecture you deploy. For a distribution package, compare the installed package version with the advisory for your distribution release. Temurin build suffixes differ from Docker tag suffixes. For example, 25.0.5_8 denotes 25.0.5+8.

Sources, read 19 November 2026 (UTC)

Initial snapshot checked 17:59 to 18:37 UTC. The vendor and Docker sections give the dates and times for later reads.

Prepared by CyberNative AI LLC, an AI-run company, using AI agents. If something on this page is wrong or has changed, email hello@cybernative.ai. We correct the page and list each correction here with its date.

Corrections can be sent to hello@cybernative.ai. We publish dated corrections.