CVE-2026-83663: Apache Thrift denial of service
This Apache advisory covers CVE-2026-83663 in Apache Thrift.
Key facts
- Vendor rating
- High, CVSS 8.7
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N· base score 8.7, scored by apacheAttack vector: network. Attack complexity: low. Attack requirements: none. Privileges required: none. User interaction: none. Confidentiality impact on the vulnerable system: none. Integrity impact on the vulnerable system: none. Availability impact on the vulnerable system: high. Confidentiality impact on subsequent systems: none. Integrity impact on subsequent systems: none. Availability impact on subsequent systems: none.- Weakness
- CWE-674 Uncontrolled Recursion
- EPSS
- 0.28% chance of exploitation in the next 30 days (20th percentile). FIRST EPSS, .
- CISA SSVC
- Exploitation: none observed. Automatable: yes. Technical impact: partial. CISA, .
- CISA KEV
- Not listed (catalogue checked )
- Affected
- Apache Thrift before 0.25.0
- Fixed in
- 0.25.0
- Source published
- Source revised
- Listed by VulniPulse
Compiled by VulniPulse from the linked sources. How records are collected and checked.
Affected products & platforms
Description
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.
Text from the source record.
- Apache Thrift before 0.25.0
Official advisory · high-confidence parse· fetched ·verify at source
How to fix CVE-2026-83663
Upgrade to the first fixed release for your version, shown in the table above.
Vendor guidance
- 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.
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.
CVE-2026-83663 in other vendors' advisories
- Red Hat: CVE-2026-83663, high severity, fixed in 0.25.0, cryostat/cryostat-storage-rhel9:4.2.0-28, rhoai/odh-feature-server-rhel9:1792685074 and 6 more
More Apache Software Foundation advisories
CVE-2026-63772Oct 2, 2026Allocation of Resources Without Limits or Throttling vulnerability in Apache Thrift goCVE-2026-66055Oct 2, 2026Allocation of Resources Without Limits or Throttling vulnerability in Apache Thrift C++CVE-2026-66081Oct 2, 2026Access of Uninitialized Pointer vulnerability in Apache Thrift c_glib bindingsCVE-2026-66837Oct 2, 2026Stack-based Buffer Overflow, Integer Overflow or Wraparound vulnerability in Apache ThriftCVE-2026-66858Oct 2, 2026The protocol skip routine in several Apache Thrift bindings did not apply the binding'sCVE-2026-66859Oct 2, 2026NULL Pointer Dereference, Use of Uninitialized Variable vulnerability in Apache Thrift
Apache Software Foundation advisories, October 2026All Apache Software Foundation advisories
Get an email when Apache publishes the next one.
See Apache's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.