Uncontrolled Recursion vulnerability in Apache Thrift.
This issue affects Apache Thrift: before 0.23.0.
Users are recommended to upgrade to version 0.23.0, which fixes the issue.
Security readout for executives and security teams
Plain-English summary
Apache Thrift versions before 0.23.0 can recurse until a process stack overflows, causing service interruption. The public record rates this high because it is network reachable, low complexity, needs no authentication or user interaction, and affects availability rather than data confidentiality or integrity.
Executive priority
Treat this as a high-priority availability risk for systems relying on Apache Thrift. It is not described as data theft or privilege escalation, but unauthenticated remote service disruption can still affect business operations.
Technical view
CVE-2026-41606 is an uncontrolled recursion issue in Apache Thrift c_glib dispatch, mapped to CWE-606 and CWE-674. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, indicating unauthenticated remote denial-of-service potential. Apache says versions before 0.23.0 are affected and 0.23.0 fixes it.
Likely exposure
Exposure is most likely where applications or services use Apache Thrift before 0.23.0, particularly C GLib dispatch code. Downstream exposure may depend on vendor packaging, including Red Hat advisories listed in the source bundle.
Exploitation context
The provided sources do not report active exploitation, and KEV status is false. The risk comes from the CVSS profile: remote, low-complexity, unauthenticated availability impact. Public trigger details are limited in the supplied bundle.
Researcher notes
Evidence identifies uncontrolled recursion in c_glib dispatch but does not include trigger mechanics. Avoid assuming broader language bindings or products without dependency evidence. Focus validation on version provenance, generated C GLib usage, and vendor-fixed package mapping.
Mitigation direction
Upgrade Apache Thrift to version 0.23.0 or later.
Apply relevant downstream vendor fixes from Red Hat or other package providers.
Prioritize internet-facing or unauthenticated Thrift services first.
Check vendor advisories for product-specific backports or mitigations.
Validation and detection
Inventory applications and packages using Apache Thrift.
Confirm deployed Apache Thrift versions are 0.23.0 or fixed vendor builds.
Identify services using Thrift C GLib dispatch paths.
Review service monitoring for unexplained crashes or restart loops.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-606: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-606 · source CWE mapping
Unchecked Input for Loop Condition
Unchecked Input for Loop Condition represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Uncontrolled Recursion represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.