Skip to content
Free since 2015. Built for the engineers who keep things running.

cat /articles/docker-patches-java4shell-and-the-nginx-http2-with-docker-hardened-images.md

Security

Docker patches Java4Shell and the NGINX HTTP/2 with Docker Hardened Images

Docker has published fixed images for the Java4Shell Base64 flaw and two NGINX HTTP/2 bugs, but Temurin-based images are still waiting on upstream fixes. Here is how to check exposure and set a temporary JVM flag.

Docker Feed19 Nov 2026 · 9 min read · summary

article --summary

The summary

This post explains that Java4Shell (CVE-2026-114938) is a memory-corruption bug in the HotSpot JVM's AVX-512 Base64 decoding routine, which can allow code execution when an attacker controls input to the decoder. It is only reachable on x86-64 hosts with AVX-512 VBMI, and affects Java 17.0.6 and later across vendors. Docker's Hardened Images already carry fixed Corretto, SapMachine and Zulu runtimes and rebuilt NGINX images, while Eclipse Temurin is still pending. Readers learn how to confirm their Java build version, check CPU flags on hosts and Kubernetes nodes, and verify whether a JVM is exposed. Until a fixed runtime is in use, the post recommends setting the -XX:-UseBASE64Intrinsics flag on every JVM and verifying it actually takes effect, since deployment scripts can override it. Java 26 is treated as unpatched, and the fixed runtime remains the only complete remedy.

Editorial note: This is a summary of an article first published by Docker Feed. The full piece is on their site.

Reading now

Topic
Security
Source
Docker Feed
Published
19 Nov 2026
Format
Curated summary

Have a take on this?

Write it up and submit it. It goes on the list once an editor approves it.

Submit an article

articles --latest

Latest articles

New from the blogs we follow and the community.

All articles

newsletter --weekly

DevOps Weekly, minus the noise.

The best reads, new jobs and upcoming events, in one email a week.