bump tomcat-embed-core to 10.1.55 (Dependabot CVE batch)#9
Merged
Conversation
Spring Boot 3.5.14 brings tomcat-embed-core 10.1.54, which is on the Dependabot security report with 21 open alerts (4 Critical, 3 High, 1 Low — repeated across all three modules): - HTTP/2 request headers not validated - Digest authenticator authenticates any unknown user - Security constraints not correctly applied - Unbounded read in WebDAV LOCK and PROPFIND handling - LockOutRealm treats user names as case-sensitive - WebSocket authentication header exposure - AJP secret compared in non-constant time Override Spring Boot's managed <tomcat.version> property to 10.1.55 in the root pom, the patch release in the same 10.1.x line that addresses this batch. Verified via `mvn dependency:tree` that all three modules now resolve org.apache.tomcat.embed:tomcat-embed-core:10.1.55. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
|
Coverage Impact This PR will not change total coverage. 🚦 See full report on Qlty Cloud »🛟 Help
|
vzakharchenko
added a commit
that referenced
this pull request
May 19, 2026
Snyk's scan of the sample reactor (sample-core, forge-connect, forge-container) surfaced 8 transitive CVEs that the library-side tomcat bump in #9 did not touch — the sample has its own spring-boot-starter-parent and is built independently. - Override <tomcat.version>10.1.55</tomcat.version> in the sample's parent pom; closes the same CVE batch on sample-core that #9 already resolved for the bridge modules (HTTP/2 header validation, DIGEST authenticator wildcard match, WebDAV LOCK/PROPFIND unbounded read, LockOutRealm case sensitivity, WebSocket header exposure, AJP non-constant time, security-constraint mapping). - Pin org.apache.commons:commons-lang3 to 3.18.0 in the parent's <dependencyManagement>. liquibase-core 4.31.1 (pulled by the Connect JPA starter) drags in 3.17.0, which carries CVE-2025-48924 (Uncontrolled Recursion in ClassUtils.getClass). 3.18.0 is the patch. Verified `mvn dependency:tree` on each sample module resolves tomcat-embed-core:10.1.55 and commons-lang3:3.18.0 (the latter only where liquibase is on the path — forge-container excludes JPA and so has no commons-lang3 transitive at all). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Spring Boot 3.5.14 brings tomcat-embed-core 10.1.54, which is on the Dependabot security report with 21 open alerts (4 Critical, 3 High, 1 Low — repeated across all three modules):
Override Spring Boot's managed <tomcat.version> property to 10.1.55 in the root pom, the patch release in the same 10.1.x line that addresses this batch. Verified via
mvn dependency:treethat all three modules now resolve org.apache.tomcat.embed:tomcat-embed-core:10.1.55.