[3.15] Bump to Netty 4.1.118.Final #46199
Merged
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
Fixes the following CVEs: - CVE-2025-24970 - CVE-2025-25193 There is no need to bump Vert.x + Mutiny bindings, the CVEs are fixed at the Netty level.
|
/cc @aloubyansky (3.15), @gastaldi (3.15), @gsmet (3.15), @jmartisk (3.15), @rsvoboda (3.15) |
quarkus-bot
bot
changed the title
quarkus-bot
bot
added
area/dependencies
aloubyansky
approved these changes
Feb 11, 2025
gastaldi
approved these changes
Feb 11, 2025
This was referenced Feb 11, 2025
Status for workflow
|
|
@geoand @aloubyansky Will this be part of the Quarkus 3.15.4 payload? And when can we expect it? Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
Fixes the following CVEs:
There is no need to bump Vert.x + Mutiny bindings, the CVEs are fixed at the Netty level.
I also added a separate commit to fix compilation issues for
integration-tests/rest-client-reactive-stork