Time-of-check Time-of-use (TOCTOU) Affecting trino-plugin-exchange-hdfs package, versions <482-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.11% (2nd 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-TRINOPLUGINEXCHANGEHDFS-18284048
  • published24 Jul 2026
  • disclosed29 Jul 2026

Introduced: 24 Jul 2026

NewCVE-2026-56822  (opens in a new tab)
CWE-367  (opens in a new tab)

How to fix?

Upgrade Minimos:latest trino-plugin-exchange-hdfs to version 482-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream trino-plugin-exchange-hdfs package and not the trino-plugin-exchange-hdfs 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 versions 4.1.136.Final and 4.2.16.Final, the OcspServerCertificateValidator forwards the SslHandshakeCompletionEvent before the asynchronous OCSP validation completes. This allows the client's downstream handlers to send sensitive application data (e.g., HTTP requests) to a revoked server before the channel is closed by the OCSP check. n io.netty.handler.ssl.ocsp.OcspServerCertificateValidator#userEventTriggered, when an SslHandshakeCompletionEvent is received, the validator immediately calls ctx.fireUserEventTriggered(evt). It then initiates an asynchronous OCSP query using OcspClient.query. Because the handshake completion event is forwarded immediately, downstream handlers in the client's pipeline are notified that the TLS handshake is successful. They may then begin reading and processing incoming application data or sending outgoing data. If the OCSP response later indicates the server's certificate is REVOKED, the validator closes the channel, but by this time, the client may have already leaked sensitive data to a revoked server or processed malicious responses from it. This issue has been fixed in versions 4.1.136.Final and 4.2.16.Final.