UID2-7850: Upgrade netty-handler to fix CVE-2026-75595 - #48
Merged
Conversation
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
BehnamMozafari
approved these changes
Sep 11, 2026
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
2 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.
What
Bumps the existing
netty.versiondependency-management override (introduced in UID2-7278, last bumped in UID2-7571/7572/7573/7574) from4.1.136.Finalto4.1.137.Final. This carriesnetty-handlerand the other pinnedio.netty:*artifacts (netty-codec-http,netty-codec-http2,netty-bom) up to the fixed version — no new override added.Why
CVE-2026-75595 in
io.netty:netty-handler(CRITICAL). Installed version4.1.136.Finalis vulnerable; fixed in4.2.17.Finalor4.1.137.Final. This PR takes the minimal same-minor-line fix (4.1.137.Final) rather than the 4.2.x line, consistent with the existing override's baseline.This library pulls Netty in transitively via the Azure SDK's default Reactor-Netty HTTP client, which is used for real calls to Azure AD and Key Vault — so the vulnerable code path is reachable, not just present on the classpath.
Jira: https://thetradedesk.atlassian.net/browse/UID2-7850
Testing
No Java/Maven toolchain was available in the environment used to make this change, so
mvn compileand the unit test suite were not run here. This is a single-line version-property bump in an already-existing override (same shape as the prior UID2-7571-7574 fix), and CI will run the full build/test suite on the PR.