Quick answers
- Is CVE-2026-66053 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-66053 being exploited in the wild.
- How severe is CVE-2026-66053?
- Medium severity, with a CVSS score of 5.9, published 27 July 2026.
- Which products and versions are affected?
- Apache Thrift < 0.24.0; Apache Software Foundation Thrift Python Bindings before 0.24.0; thrift (PyPI) ECOSYSTEM:introduced=0,fixed=0.24.0.
- Is there a fix for CVE-2026-66053?
- Yes. thrift (PyPI): upgrade to 0.24.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-66053 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-66053?
- Check whether you run Apache Thrift, Apache Software Foundation Thrift Python Bindings or thrift (PyPI) 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
- thrift (PyPI): upgrade to 0.24.0 or later
pip install "thrift>=0.24.0"
Technical details
The vulnerability is a certificate host validation bypass (CWE-297) in the Apache Thrift Python bindings' SSL/TLS implementation. The vulnerable component fails to verify that the server's presented certificate hostname matches the intended connection target, allowing a network-based attacker to conduct man-in-the-middle attacks. The attack requires network access to intercept traffic but does not require authentication, user interaction, or elevated privileges. An attacker can eavesdrop on encrypted communications and potentially modify data in transit. The vulnerability affects Apache Thrift versions prior to 0.24.0, which includes the fix. Users should upgrade to version 0.24.0 or later.
Affected products
- Apache Thrift < 0.24.0
Identifiers
- CVE-2026-66053
- GHSA-hwrj-9rr4-24xh
- PYSEC-2026-3927
Timeline
- 2026-07-27: disclosed: Vulnerability disclosed and published to GitHub Advisory Database
- 2026-07-27: patched: Fix released in Apache Thrift version 0.24.0