-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump to Vert.x 4.5.13 and Netty 4.1.118.Final #46194
Conversation
See https://github.com/vert-x3/wiki/wiki/4.5.13-Release-Notes Fixes the following CVEs: - CVE-2025-24970 - CVE-2025-25193
Hi @jponge Can it be backported to 3.15, and 3.8 ? |
I need to have a look, it depends on what the Netty versions are here as Netty has been quite brittle wrt native compilation in their minor upgrades. |
3.15 looks easy to do, but I will open a PR instead of just tagging with a backport label (/cc @gsmet) Next I'll look at 3.8 |
Update: I was on the wrong reference branch for 3.15, so I need to restart the investigations for 3.15 |
Status for workflow
|
Will this be also included in next 3.18 ? |
Yes, that's the purpose of the |
@jponge are we using the native SSL engine by default? I.e. are we practically exposed to this CVE? |
I am not sure what they mean in the CVE by "native" SSL engine, but just looking at the code in Netty that fixes it, I would say we are using it |
3.8 is more complicated, because meanwhile Netty has had internal refactorings that break native compilation. I might need to also bump Vert.x and backport fixes here. |
@jponge what I usually recommend is to go through the existing Netty upgrade pull requests. |
/cc @sberyozkin @jmartisk for awareness. |
Backports: |
Thanks @jponge for also providing fixes for 3.15 and 3.8 branches |
See https://github.com/vert-x3/wiki/wiki/4.5.13-Release-Notes
Fixes the following CVEs: