Repository navigation
Build on a JDK with the eMudhra fix; note it for customers - #36
Merged
Merged
Conversation
The client trusts the JDK's bundled cacerts, so customers need a JDK build with the eMudhra fix. Part of PLA-176.
Temurin has no fixed build yet; Oracle 25.0.5.0.2 is the first free one. Switch the pom to maven.compiler.release 17 so the bytecode target and API surface stay Java 17. Also document the blocked.certs and revocation-check workarounds for customers. Part of PLA-176.
sharanmoore
changed the title
sharanmoore
marked this pull request as ready for review
October 22, 2026 10:58
setup-java v4 is deprecated and warns on every run.
stevewithey
approved these changes
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.
Part of PLA-176 (eMudhra intermediate CA compromise).
Why
JDKs ship their own
cacerts, so a JVM keeps trusting the compromised eMudhra intermediates until the JDK itself is updated. That covers both our CI and release builds (Maven Central / Sonatype traffic, with deploy credentials) and customers' apps.What
download.oracle.com/java/25/latesthas the same checksum as the25.0.5.0.2archive.source/target 17→maven.compiler.release 17. The bytecode target stays Java 17, so customers on 17 and 21 are unaffected.releasealso checks that the code only uses Java 17 APIs, whichsource/targetdoesn't do on a newer JDK. CI no longer runs the tests on a JDK 17 runtime. We accepted that trade-off.HttpClientwith no custom TLS config, so customers get the fix by updating their JDK. The note lists the fixed builds for 17+ and Oracle'sblocked.certs/ revocation-check workarounds for customers whose vendor hasn't shipped yet.Version wording
The OpenJDK advisory lists 17.0.21, 21.0.13, 25.0.5 and 27.0.1 as affected. The fixed builds are the four-part ones (
17.0.21.0.2etc.). So the note says "up to and including 17.0.21", not "17.0.21 or later".