Algorithmic Complexity Affecting trino-plugin-kafka-event-listener package, versions <482-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.35% (28th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-TRINOPLUGINKAFKAEVENTLISTENER-19665534
  • published10 Sept 2026
  • disclosed19 Aug 2026

Introduced: 19 Aug 2026

NewCVE-2026-75596  (opens in a new tab)
CWE-407  (opens in a new tab)

How to fix?

Upgrade Minimos:latest trino-plugin-kafka-event-listener to version 482-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream trino-plugin-kafka-event-listener package and not the trino-plugin-kafka-event-listener package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

Netty is an asynchronous, event-driven network application framework. Prior to 4.1.137.Final and 4.2.17.Final, the default io.netty.handler.ssl.SniHandler constructors use the pre-handshake ClientHello aggregation path in handler/src/main/java/io/netty/handler/ssl/SslClientHelloHandler.java at io.netty.handler.ssl.SslClientHelloHandler#decode, where handshakeBuffer.clear() and writeBytes() recopy all previously received body bytes for every additional TLS record. An unauthenticated remote peer can advertise a large ClientHello and deliver its body in thousands of tiny records, causing quadratic CPU work on the event loop before the TLS handshake completes and degrading TLS handling for other clients. This issue is fixed in versions 4.1.137.Final and 4.2.17.Final.