FPTWaze
Home โ€บ News

Docker Hardened Images ship fixes for Java4Shell and NGINX HTTP/2

ยท FPTWaze news desk

Docker Hardened Images have fixed Java runtimes for Java4Shell and fixed NGINX images for two HTTP/2 flaws. Some Java builds still await a fix.

Docker Hardened Images ship fixes for Java4Shell and NGINX HTTP/2

Docker Hardened Images (DHI) now include fixed Java runtimes for Java4Shell, a memory-corruption bug in the Java runtime, and fixed NGINX images for two HTTP/2 flaws. Fixed Java images are available from Amazon Corretto, SapMachine and Azul Zulu. Eclipse Temurin, which many DHI application images use, is still waiting for its fixed build.

Java4Shell (CVE-2026-114938) can let an attacker with no credentials run code inside a Java application. Java 17.0.6 and later are affected, including Java 21, 25, 26 and 27, from every OpenJDK vendor. The bug is reachable only when the JVM runs on an x86-64 CPU with AVX-512 VBMI, so the same image may be exposed on one host and not on another. ARM64 hosts are not affected.

Until an image runs a fixed build, start Java with the flag -XX:-UseBASE64Intrinsics and confirm that it reached every JVM in the container. Check the Java build with java -version. A tag or a rebuild date does not show which Java build is inside an image. Java 8 and 11 are not affected by this CVE.

The NGINX flaws, tracked as CVE-2026-123007 and CVE-2026-123633, can crash a worker process. Both need HTTP/2 enabled on the server. The DHI NGINX images were rebuilt on NGINX 1.30.7 and 1.31.9. Pull the image again, or move any tag pinned to an older version to one of those versions, and redeploy.

After you pull the new images, redeploy and confirm the running Java version. A node may keep an old image under the same tag, so deploy by digest or set the pull policy to Always for this rollout.

Source: Docker Blog โ†—. This summary is prepared automatically from the official source and may contain mistakes; the source is authoritative.

Docker Desktop: Build and run containers on your desktop.