Repository navigation
fix: bump Zulu to 11.0.33 / 21.0.13 for eMudhra blocklist (CVE-2026-91403) - #56
Merged
Merged
Conversation
Azul's out-of-cycle release of 2026-10-21 adds the compromised eMudhra intermediates to blocked.certs. azul/zulu-openjdk-debian has no tag with the fix yet, so fetch the Zulu CA build from cdn.azul.com, pinned by SHA-256 for amd64 and arm64. java.version now holds the Zulu build name. A build step fails if the fixed blocklist is missing from the jlinked JRE. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
aaron-steinfeld
marked this pull request as ready for review
October 24, 2026 13:19
ravisingal
approved these changes
Oct 24, 2026
1 of 2 tasks
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.
Alternative to #55: bump to the fixed Zulu instead of deleting CA roots from the keystores.
Azul's out-of-cycle release of 2026-10-21 adds the compromised eMudhra intermediates to
blocked.certs.azul/zulu-openjdk-debianhas no tag with the fix yet (latest are 21.0.12.1 and 11.0.32.1), so this fetches the Zulu CA build fromcdn.azul.com, pinned by SHA-256.java.versionnow holds the Zulu build name (zulu21.54.107-ca-jdk21.0.13,zulu11.92.109-ca-jdk11.0.33). The workflows pass it through asJAVA_VERSIONunchanged.jrestage is nowdebian:bookworm-slimplus the verified tarball (amd64 and arm64 hashes). jlink copiesblocked.certsfrom the JDK it runs, so it has to be the fixed one.blocked.certs.azul/zulu-openjdk-debianonce a tag with the fix is published.Bumping later means updating
java.versionand the two checksums in each Dockerfile together. A mismatch fails the build.Tested by building java-11 and java-21 for linux/amd64 (under QEMU) and linux/arm64. All four builds pass, and the images report 11.0.33 (Zulu 11.92+109-CA) and 21.0.13 (Zulu 21.54+107-CA). The Trivy scan and publish workflow were not run locally.
🤖 Generated with Claude Code