Quick answers
- Is CVE-2026-83663 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-83663 being exploited in the wild.
- How severe is CVE-2026-83663?
- Informational severity, published 2 October 2026.
- Which products and versions are affected?
- Apache Thrift before 0.25.0.
- Is there a fix for CVE-2026-83663?
- Yes: fixed in 0.25.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-83663 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-83663?
- Check whether you run Apache Thrift at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 0.25.0
Technical details
The Go TFramedTransport and THeaderTransport implementations recursively call the Read method when a frame yields no payload bytes, with no limit on recursion depth. An attacker can send a peer a 4-byte frame with declared size zero (TFramedTransport) or an 18-byte header block that fills the frame (THeaderTransport) to trigger stack exhaustion, resulting in a fatal error that recover() cannot catch. This is a network-accessible denial of service affecting all applications using the vulnerable Go transports.
Affected products
- Apache Thrift before 0.25.0
Timeline
- 2026-10-02: disclosed