Repository navigation
fix(security): mitigate CVE-2026-91403 across JDK images - #15
Merged
Merged
Conversation
Apply the upstream CVE-2026-91403 certificate blocklist mitigation across JDK 8, 11, 17, 21 and 25 while preserving existing entries. Update available Temurin patch bases and check all 48 certificate encodings during image builds.
This was referenced Oct 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CVE-2026-91403 requires distrusting compromised eMudhra intermediate CAs; updating the OS trust store or ordinary Temurin CPU version alone does not close the issue. Append all 48 fingerprints from OpenJDK 22bc735, preserving existing entries and using the effective Java 8/11+ security-file path. Update the embedded
java.base.jmodblocklist too, sojlinkgenerated runtimes retain the same protection.Update available amd64/arm64 Noble bases to 8u504, 11.0.32.1, 17.0.20.1, 21.0.12.1 and 25.0.4.1. Keep JDK 21 as latest. Temurin 25 omits JMODs and its runtime-image linker rejects a modified blocklist, so restore the matching official 25.0.4.1+1 JMODs with pinned per-architecture SHA-256 before updating their blocklist. This preserves default
jlinkbehavior and integrity checks; JDK 25 images include the additional module archive files. Pull Temurin from Docker Hub and add PR builds without publication.Validation: Java 8-compatible compilation and workflow syntax checks passed. Against the existing Java 21 image, PKIX accepted all 48 encodings before the patch and rejected all 48 afterward; ISRG Root X1 remained accepted. Merge preservation, idempotence and invalid-algorithm checks passed. Newly generated Java 21 and exact Java 25.0.4.1+1
jlinkruntimes also rejected all 48 encodings while accepting ISRG Root X1. Each image build reruns these checks; the full two-architecture CI matrix is required before publication. The initial run proved both architectures for JDK 8/11/17/21; a new complete run checks the JDK 25 packaging correction.Publish this first, then Maven and Gradle, then Node, then web-tools. Downstream updates must wait for the upstream GHCR manifests to be available.