Skip to content

bump forced netty to 4.1.135.Final to clear four new dependabot alerts#7

Merged
pzverkov merged 1 commit into
mainfrom
update/netty-4.1.135
Jun 12, 2026
Merged

bump forced netty to 4.1.135.Final to clear four new dependabot alerts#7
pzverkov merged 1 commit into
mainfrom
update/netty-4.1.135

Conversation

@pzverkov

Copy link
Copy Markdown
Member

Four new netty advisories landed after 0.1.1 (all against netty <= 4.1.134.Final, patched in 4.1.135.Final, the latest stable 4.1.x):

  • #33 high - netty-handler: SNI handler pre-allocates up to 16 MiB from nine attacker bytes
  • #32 high - netty-handler: IPv6 subnet filter bypass via incorrect comparator masking
  • #35 medium - netty-codec-http2: ByteBuf ref-count leak in DelegatingDecompressorFrameListener
  • #34 medium - netty-codec-http2: advertised MAX_CONCURRENT_STREAMS not enforced

Bumps the 11 forced netty coordinates 4.1.133.Final -> 4.1.135.Final so the dependency-submission graph reports patched versions and Dependabot auto-closes them on merge to main.

netty is a build/test-tooling transitive only (android unified test platform / grpc-netty), never in the shipped AAR or app runtime. Verified: all netty resolves to 4.1.135.Final and assembleRelease passes.

4.1.133 -> 4.1.135.Final clears alerts #32-#35: netty-handler SNI 16 MiB pre-allocation and IPv6 subnet filter bypass (both high), and netty-codec-http2 ByteBuf ref-count leak and unenforced MAX_CONCURRENT_STREAMS (medium). 4.1.135.Final is the latest stable 4.1.x. netty reaches the graph via the android unified test platform tooling only, not the shipped aar.
@pzverkov pzverkov merged commit a2c60ac into main Jun 12, 2026
4 checks passed
@pzverkov pzverkov deleted the update/netty-4.1.135 branch June 12, 2026 10:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant