Repository navigation
fix(docker): update Java 25 for CVE-2026-114938 - #3356
Merged
Merged
Conversation
Contributor
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
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.
Description
The shared Tomcat builder pins a Java 25 build affected by CVE-2026-114938 (Java4Shell). Update it to Azul's November 2026 security release, Zulu 25.38.201 / OpenJDK 25.0.5.1+2, which fixes the vulnerable Base64 intrinsic.
Changes Made
AZUL_ZULU_VERSIONfrom25.38.109to25.38.201.JDK_VERSIONfrom25.0.5.0.3to25.0.5.1, matching Azul's archive filenames for both amd64 and arm64.How to Test
Build the Tomcat builder for amd64 and arm64 and verify that
java -versionreports Zulu 25.38 / OpenJDK 25.0.5.1+2. Exercise the standard and FIPS variants before publishing dependent application images.Validation completed: Azul's package API identifies the updated Java 25 build; both architecture-specific archive URLs return HTTP 200;
git diff --checkpasses. Container builds and runtime smoke tests were not run.Notes
Azul's advisory identifies this release as fixed.
Rebuild and publish the Tomcat builder, then rebuild dependent SEMOSS images and roll the affected workloads. Existing published images and running containers retain their bundled Java runtime until rebuilt and redeployed.