Skip to content

fix: bump netty-handler to 4.1.137.Final for CVE-2026-62243 #307

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.

Sign up for GitHub

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

Open
heatherzh01 wants to merge 2 commits into
base: main
Choose a base branch
from
Open

fix: bump netty-handler to 4.1.137.Final for CVE-2026-62243 #307

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
19a24fc
pin netty-handler to 4.1.137.Final for CVE-2026-62243 (TLS hostname v…
heatherzh01 Sep 3, 2026
e083f99
docs: document netty-bom pin rationale and removal tracking
heatherzh01 Sep 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,26 @@

<dependencyManagement>
<dependencies>
<!--
CVE-2026-62243: Netty TLS hostname verification bypass on the
SslProvider.OPENSSL client path (fixed in netty 4.1.137.Final).
Quarkus 3.36.2's quarkus-bom manages netty 4.1.135.Final, which is
vulnerable, so this netty-bom is imported BEFORE quarkus-bom to force
all io.netty artifacts to 4.1.137.Final (first-declared import BOM wins).

TEMPORARY: remove this import once the platform's quarkus.platform.version
manages netty-handler >= 4.1.137.Final; leaving it pinned would silently
cap netty below any newer version Quarkus ships and could re-expose us to
future CVEs. Removal tracked by: TC-6098
(https://redhat.atlassian.net/browse/TC-6098).
-->
<dependency>
<groupId>io.netty</groupId>
<artifactId>netty-bom</artifactId>
<version>4.1.137.Final</version>
<type>pom</type>
<scope>import</scope>
</dependency>
<dependency>
<groupId>${quarkus.platform.group-id}</groupId>
<artifactId>${quarkus.platform.artifact-id}</artifactId>
Expand Down