Skip to content
VulniPulse
Sign in
Advisory severityHigh8.7Apache Software Foundation

High [CVE-2026-83663] Uncontrolled Recursion vulnerability in Apache Thrift go bindings

This high-severity Apache Software Foundation advisory covers CVE-2026-83663 affecting Apache Thrift.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-83663 Source published Source updated

VulniPulse record published Record updated

CVE-2026-83663
Affected products & platforms
Apache Software FoundationUnclassified
Open source advisory

Android app · Google Play

Monitor future Apache Software Foundation CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery
Get CVE alertsSee app features

Summary

Uncontrolled Recursion vulnerability in Apache Thrift go bindings.

Both Go transports satisfy a read out of a buffered frame and, when that frame yields no payload bytes, read the next frame and call `Read` again instead of looping. A peer produces such a frame for 4 bytes in `TFramedTransport` (a declared size of zero) or 18 bytes in `THeaderTransport` (a header block that fills the frame), so nothing bounds the depth.

The Go stack limit is reached as a `fatal error`, which `recover()` cannot catch, so the whole process dies.

This issue affects Apache Thrift: before 0.25.0.

Users are recommended to upgrade to version 0.25.0, which fixes the issue.

Affected versions
  • Apache Thrift before 0.25.0

Official advisory · high-confidence parse· fetched 4 days ago·verify at source

Fixed versions
  • 0.25.0

Official advisory · high-confidence parse· fetched 4 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • The Go stack limit is reached as a `fatal error`, which `recover()` cannot catch, so the whole process dies.
  • Users are recommended to upgrade to version 0.25.0, which fixes the issue.
Temporary workarounds
  • A peer produces such a frame for 4 bytes in `TFramedTransport` (a declared size of zero) or 18 bytes in `THeaderTransport` (a header block that fills the frame), so nothing bounds the depth.

Official advisory · high-confidence parse· fetched 4 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.