Memory Allocation with Excessive Size Value Affecting github.com/apache/thrift/lib/go/thrift package, versions <0.25.0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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 applicationsSnyk Learn
Learn about Memory Allocation with Excessive Size Value vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-GOLANG-GITHUBCOMAPACHETHRIFTLIBGOTHRIFT-21717091
- published26 Oct 2026
- disclosed2 Oct 2026
- creditAdam Korczynski
Introduced: 2 Oct 2026
NewCVE-2026-63772 Â (opens in a new tab)How to fix?
Upgrade github.com/apache/thrift/lib/go/thrift to version 0.25.0 or higher.
Overview
github.com/apache/thrift/lib/go/thrift is a Go implementation of the Apache Thrift library.
Affected versions of this package are vulnerable to Memory Allocation with Excessive Size Value via list, set, and map decoding in its Go protocol readers and generated decoders. An unauthenticated remote attacker can send a message declaring a very large container element count that the available payload cannot support; the generated decoder reserves memory for that count before decoding the elements, exhausting memory and crashing the server.
Notes
- At the protocol-header validation step, the declared count is still bounded by
TConfiguration.MaxMessageSize; it need not fit in the actual payload, but a lower configured limit reduces the maximum count the decoder will use for its allocation.