fix(deps): bump netty-handler 4.1.136 → 4.1.137 for CVE-2026-75595 - #42217
Conversation
CVE-2026-75595 is an SNI routing bypass in SslClientHelloHandler#decode that lets a fragmented TLS ClientHello fall back to the default SslContext, potentially bypassing per-SNI mTLS. Fixed in netty 4.1.137.Final. This resolves the CVE in server.jar and all plugin JARs (awsLambda, dynamo, firestore, mysql). Ref: GHSA-c4c3-7fpv-j4q5
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Essentials Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. WalkthroughThe server Maven configuration updates the managed Netty version from ChangesNetty dependency update
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: Merge Risk: ⚪ Minimal · up to This patch-level Netty security update changes no application configuration or public behavior, and no current merge-readiness risks remain. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Netty climbs one version high Comment |
|
/build-deploy-preview skip-tests=true |
|
Deploying Your Preview: https://github.com/appsmithorg/appsmith/actions/runs/34457196191. |
|
Deploy-Preview-URL: https://ce-42217.dp.appsmith.com |
Description
Bumps
io.netty:netty-handlerfrom 4.1.136.Final to 4.1.137.Final tofix CVE-2026-75595
(GHSA-c4c3-7fpv-j4q5).
What is CVE-2026-75595?
A fragmented TLS ClientHello whose handshake header spans records triggers an
IndexOutOfBoundsExceptioninSslClientHelloHandler#decode, causing Netty tofall back to the default
SslContextinstead of the SNI-specific one. Indeployments relying solely on per-SNI mTLS selection, this lets an
unauthenticated client bypass the mTLS requirement.
Practical exploitability in Appsmith: Very low. TLS termination happens at
Caddy, not inside the Java server. Appsmith does not use Netty's
SslClientHelloHandlerfor SNI-based mTLS routing. The bump removes the scannerfinding.
What this fixes (5 of 6 scanner findings):
server.jar(BOOT-INF/lib/netty-handler)awsLambdaPlugin-v2.4.jardynamoPlugin-v2.4.jarfirestorePlugin-v2.4.jarmysqlPlugin-v2.4.jarNot covered here:
/opt/keycloak/lib/…/netty-handler-4.1.136.Final.jar—Keycloak is EE-only (not present in CE base.dockerfile). That fix will be a
separate EE-only change (Keycloak version bump or JAR overlay).
Regression risk: Minimal. This is a patch bump (136→137) within the 4.1.x
series. The fix touches only the TLS ClientHello parser
(
SslClientHelloHandler#decode). No HTTP, codec, or transport API changes.Spring Boot 3.5.16 is compatible.
Impact on existing instances
Automation
/ok-to-test tags="@tag.All"
🔍 Cypress test results
Communication
Should the DevRel and Marketing teams inform users about this change?
Tip
🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/34449300280
Commit: ba35b62
Cypress dashboard.
Tags:
@tag.AllSpec:
Thu, 10 Sep 2026 08:36:02 UTC
Summary by CodeRabbit