Allocation of Resources Without Limits or Throttling 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 Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-GOLANG-GITHUBCOMAPACHETHRIFTLIBGOTHRIFT-20510275
- published5 Oct 2026
- disclosed2 Oct 2026
- creditHo1aAs
Introduced: 2 Oct 2026
NewCVE-2026-83663 Â (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 Allocation of Resources Without Limits or Throttling in TFramedTransport.Read() in lib/go/thrift/framed_transport.go and THeaderTransport.Read() in lib/go/thrift/header_transport.go, each of which responds to a buffered frame yielding no payload bytes by reading the next frame and calling itself again rather than looping, so nothing bounds the depth. An attacker can terminate the process by sending a stream of frames that carry no payload, costing 4 bytes each in TFramedTransport as a declared size of zero and 18 bytes each in THeaderTransport as a header block that fills the frame, until the Go stack limit is reached as a fatal error that recover() cannot intercept, so a server that otherwise contains per connection panics dies in full. This requires only that the application use the Go bindings with either transport, with no configuration or authentication step in the way, and a single connection suffices, since each stack frame costs the attacker a handful of bytes.