CVE-2026-41605: Apache Thrift: Swift Compact Protocol integer overflow
Integer Overflow or Wraparound 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 contain an integer-overflow flaw in the Swift Compact Protocol. A remote, unauthenticated attacker may be able to cause serious confidentiality and availability impacts, although exploitation is rated high complexity. Organizations using affected Thrift components should upgrade promptly.
Executive priority
Prioritize remediation as high for internet-facing or untrusted-input services. The potential business consequences include data exposure, service disruption, and limited data modification. Upgrade during the nearest expedited maintenance window, while validating whether the affected protocol is actually reachable.
Technical view
CVE-2026-41605 is a CWE-190 integer overflow or wraparound in Apache Thrift's Swift Compact Protocol. CVSS 3.1 scores it 7.7: network-accessible, unauthenticated, requiring no user interaction, with high attack complexity, high confidentiality and availability impact, and low integrity impact. Versions before 0.23.0 are affected.
Likely exposure
Exposure is likely where Apache Thrift earlier than 0.23.0 is present and the affected Swift Compact Protocol is reachable through network-facing or upstream-controlled data. The sources do not identify specific applications, configurations, or request paths required to trigger the flaw, so asset-level reachability must be established locally.
Exploitation context
The supplied record is not listed in KEV, and the sources provide no evidence of active exploitation or public weaponization. The CVSS vector indicates remote, unauthenticated exploitation is possible but requires high attack complexity. Treat exposed affected services seriously without assuming exploitation has occurred.
Researcher notes
The public bundle establishes the weakness class, affected version boundary, fixed release, and CVSS characteristics, but does not describe the precise overflow location, triggering conditions, affected Swift APIs, or observed indicators. Testing should remain defensive and focus on dependency identification, protocol reachability, version verification, and post-upgrade regression coverage.
Mitigation direction
Upgrade Apache Thrift to version 0.23.0 or later.
Apply applicable Red Hat security errata for downstream packaged deployments.
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-190: 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.
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-190 · source CWE mapping
Integer Overflow or Wraparound
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.