Integer Overflow or Wraparound Affecting thrift package, versions [0,]


Severity

Recommended
0.0
high
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
1.1% (63rd 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 Learn

Learn about Integer Overflow or Wraparound vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CONAN-THRIFT-18389066
  • published29 Jul 2026
  • disclosed27 Jul 2026
  • creditJavid Khan, Ghaith Abdulreda

Introduced: 27 Jul 2026

NewCVE-2026-55969  (opens in a new tab)
CWE-190  (opens in a new tab)

How to fix?

A fix was pushed into the master branch but not yet published.

Overview

Affected versions of this package are vulnerable to Integer Overflow or Wraparound in the zlib transport message-size tracking. An attacker can bypass the configured maxMessageSize/remainingmessagesize limits by sending a highly compressible message and forcing repeated decompressed reads, so the transports fail to decrement the consumed-message byte count correctly. This allows oversized messages to be accepted rather than rejected, breaking message-size enforcement in applications that rely on these transports to enforce input limits.

Notes

  • In the C++ binding, the vulnerable path is the TZlibTransport read loop used with a configured TConfiguration message-size cap; the undercount only shows up when the same compressed message is decompressed across repeated read() calls, so streams that fit in one call are less likely to expose it.
  • In the c_glib binding, the issue is tied to the transport’s remainingmessagesize accounting on ThriftZlibTransport; deployments that never set that per-transport limit are outside the affected enforcement path.

CVSS Base Scores

version 4.0
version 3.1