Docker Ships Fixed Hardened Images for Java4Shell on Three Runtimes, Patches Two NGINX HTTP/2 Flaws
Docker's Hardened Images catalog now carries fixed builds for the Java4Shell flaw on three OpenJDK runtimes and for two NGINX HTTP/2 bugs, while Eclipse Temurin remains unpatched.
Overview
Docker has started shipping rebuilt Docker Hardened Images that fix the “Java4Shell” Java runtime flaw and two unrelated NGINX HTTP/2 vulnerabilities, according to a Docker blog post. The update, posted November 19, closes a gap left open by the vulnerability’s initial disclosure two days earlier: which downstream Java builds had actually shipped a fix. As previously reported, the Herald covered the vulnerability itself, tracked as CVE-2026-114938, when it was disclosed and noted it was unclear which specific downstream JVM builds had shipped patched releases.
What We Know
OpenJDK and Oracle disclosed Java4Shell on November 17, and NGINX released fixes for two separate HTTP/2 flaws the next day, according to Docker. Docker says it began publishing fixed images for both issues in its Docker Hardened Images (DHI) catalog starting November 18.
Docker describes Java4Shell as “a memory-corruption bug in the Java runtime that can let an attacker with no credentials run code inside a Java application,” according to the same post. The root cause, per Docker, is in the HotSpot JVM’s hand-written, AVX-512-accelerated Base64 decoding routine, which “miscalculates a length when the input ends in unexpected padding and writes up to 62 bytes past the end of a buffer on the Java heap.” Docker says the flaw is reachable only on x86-64 processors that support AVX-512 VBMI instructions, meaning the same container image can be exposed on one host and not on another.
According to Docker, the researchers who found the bug, a firm called Calif, demonstrated pre-authentication code execution against default installations of Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate, and authenticated code execution against Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. Docker’s post adds that the researchers “note there is no universal exploit: each application needs its own, and they have not published those,” and that as of November 18 there were no public reports of exploitation in the wild.
On patch status, Docker’s own accounting shows the fix landing unevenly across the Java runtimes it bundles. Hardened Images for the Amazon Corretto, SapMachine and Azul Zulu runtimes are fixed, with Docker reporting that its published Corretto images report version strings such as 17.0.21.1.2 and 27.0.1.1.4, its SapMachine images report versions such as 21.0.13.1+2, and its Zulu images report versions such as 17.0.21.1+2. Eclipse Temurin, which Docker says many of its hardened application images rely on, was still waiting on upstream builds from the Eclipse Adoptium project as of November 18; Docker says Adoptium had published a fixed build for x86-64 Linux only, with three other version lines still in testing, and that its own Temurin-based images were still reporting unfixed version strings and remained vulnerable. Docker recommends starting Java with the -XX:-UseBASE64Intrinsics flag, which disables the vulnerable decoder, until a fixed build is in place. Docker also says Java 26 reached end of support in September 2026 and is not expected to receive a vendor fix for this flaw at all.
Separately, NGINX released fixes on November 18 for two memory-safety flaws in its HTTP/2 handling, tracked as CVE-2026-123007 and CVE-2026-123633, according to Docker. NGINX’s own security advisories page independently lists CVE-2026-123007 as a “Memory corruption in HTTP/2 flow control” issue of “major” severity, affecting versions 1.9.5 through 1.31.8, and CVE-2026-123633 as a “Use-after-free in HTTP/2” issue of “medium” severity, affecting versions 1.19.7 through 1.31.8; both are listed as fixed starting in versions 1.30.7 and 1.31.9. Docker says a crafted request exploiting either flaw can crash an NGINX worker process, and that where an attacker gets past the operating system’s memory protections, it can run code inside that worker — though both flaws require HTTP/2 to be enabled on the server. Docker’s Hardened Images for NGINX were rebuilt on the fixed 1.30.7 and 1.31.9 releases and published November 18, the same day as the upstream fix.
On the discovery of Java4Shell itself, Docker’s post relays a cost and time estimate from Calif: the firm “says it used AI to find this flaw in about an hour and that the whole effort cost less than $200 in tokens,” according to Docker.
What We Don’t Know
Docker’s post does not say when Eclipse Temurin’s remaining fixed builds — for the 17, 21 and 25 version lines — will complete testing and ship, only that they were still in progress as of November 18. Neither Docker’s post nor NGINX’s advisory page gives an exploitation status for the two NGINX HTTP/2 flaws independent of Docker’s own account.
Why It Matters
Because Java4Shell lives inside the JVM rather than in any single application, Docker’s runtime-by-runtime patch table gives operators a more concrete way to check exposure than the initial disclosure did: whether a given container is fixed now depends on which of Corretto, SapMachine, Zulu or Temurin it bundles, not just on which application it runs.