chore: upgrade springboot to 3.3.11 to resolve CVE-2025-31650 #31810
Conversation
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
b834d4a to
f666d0e
Compare
f666d0e to
21e6c86
Compare
vitorwtavares
approved these changes
May 7, 2025
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
CVE-2025-31650 is resolved by bumping Apache Tomcat to 10.1.40. This is similar to what was done for 8.4.
Since that is a transitive dependency brought in by spring-boot-starter-web we'd need to bump that and bumping it to 3.3.11 seems to be doing the trick.
Checklist
Related issues
Relates to #31703