Skip to content

fix: bump netty from 4.1.127 to 4.1.135 to remediate CVE-2026-44249 and CVE-2026-45416#927

Open
nikagra wants to merge 1 commit into
scylladb:scylla-3.xfrom
nikagra:fix/cve-2026-44249-bump-netty-3x
Open

fix: bump netty from 4.1.127 to 4.1.135 to remediate CVE-2026-44249 and CVE-2026-45416#927
nikagra wants to merge 1 commit into
scylladb:scylla-3.xfrom
nikagra:fix/cve-2026-44249-bump-netty-3x

Conversation

@nikagra

@nikagra nikagra commented Jun 16, 2026

Copy link
Copy Markdown

Summary

Bumps netty.version from 4.1.127.Final to 4.1.135.Final in the scylla-3.x branch to remediate:

  • CVE-2026-44249 (CVSS 8.1): IpSubnetFilterRule.compareTo() performs an incorrect masking operation, allowing attackers to bypass IPv6 subnet ACL rules with valid public IP addresses.

  • CVE-2026-45416 (CVSS 7.5): SslClientHelloHandler.decode() eagerly allocates up to 16 MiB of unpooled memory when maxClientHelloLength=0 (the SniHandler default). A crafted TLS ClientHello can trigger memory exhaustion (DoS).

This also covers CVE-2026-42583 (CVSS 7.5, fixed in 4.1.131.Final): HTTP Response Splitting via HttpObjectEncoder.

Context

This is the same fix pattern applied in PR #925 for the scylla-4.x branch (which bumped netty from 4.1.127 to 4.1.135). The scylla-3.x branch (scylla-driver-parent:3.11.5.x) has the same vulnerable netty version and requires the same bump.

Changes

# pom.xml
-<netty.version>4.1.127.Final</netty.version>
+<netty.version>4.1.135.Final</netty.version>

CVE-2026-45416

Bumps netty.version to 4.1.135.Final to fix:
- CVE-2026-44249 (CVSS 8.1): IPv6 subnet ACL bypass
- CVE-2026-45416 (CVSS 7.5): TLS ClientHello memory exhaustion DoS

This also covers CVE-2026-42583 (CVSS 7.5, fixed in 4.1.131.Final).
@coderabbitai

coderabbitai Bot commented Jun 16, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@nikagra, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 43 minutes and 25 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 995c5d8a-b86f-4046-b66c-f5e97b8bfbf5

📥 Commits

Reviewing files that changed from the base of the PR and between 95962cb and d53289e.

📒 Files selected for processing (1)
  • pom.xml

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

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