Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-85087 Overview
CVE-2026-85087 is an improper certificate validation vulnerability [CWE-295] in the Apache Thrift Python bindings. The flaw affects all versions of Apache Thrift prior to 0.25.0. The library returns an incorrect status code during TLS certificate validation, which can cause client code to treat invalid certificates as trusted. Attackers positioned on the network can leverage this behavior to intercept or tamper with Thrift RPC traffic. The Apache Software Foundation recommends upgrading to Apache Thrift 0.25.0 to remediate the issue.
Critical Impact
An attacker performing a man-in-the-middle attack can intercept Apache Thrift Python client traffic by presenting a certificate that should be rejected but is accepted due to incorrect status code handling.
Affected Products
- Apache Thrift Python bindings — all versions before 0.25.0
- Applications embedding the Apache Thrift Python client libraries for RPC communication
- Downstream distributions packaging vulnerable Apache Thrift releases
Discovery Timeline
- 2026-10-02 - CVE-2026-85087 published to NVD
- 2026-10-02 - Last updated in NVD database
Technical Details for CVE-2026-85087
Vulnerability Analysis
The vulnerability sits in the TLS certificate validation path of the Apache Thrift Python bindings. During the TLS handshake, the bindings return the wrong status code when a certificate verification error occurs. Calling code interprets this status as a successful validation and continues the connection using an untrusted peer certificate.
The weakness is classified under [CWE-295: Improper Certificate Validation]. It affects confidentiality and integrity of RPC messages exchanged over Thrift transports that rely on TSSLSocket or related TLS-enabled transports. Attackers do not need valid credentials, but exploitation requires a privileged network position and the ability to present a crafted certificate, which raises attack complexity.
Root Cause
The root cause is a mismatch between the certificate verification result and the status code returned by the Python bindings to callers. When validation fails for conditions such as hostname mismatch or an untrusted issuer, the function path does not propagate a failure signal. Client code therefore proceeds through the handshake and establishes an authenticated session with an attacker-controlled endpoint.
Attack Vector
Exploitation is network-based and requires an attacker to intercept traffic between a Thrift Python client and its intended server. The attacker presents an invalid or attacker-signed TLS certificate during the handshake. Because the bindings return a success status despite the validation error, the client completes the handshake and sends RPC payloads to the attacker. The attacker can then read, modify, or replay Thrift messages before forwarding them to the legitimate server. See the Apache Mailing List Discussion and the Apache Mailing List Thread for maintainer discussion of the issue.
Detection Methods for CVE-2026-85087
Indicators of Compromise
- Thrift Python clients completing TLS handshakes with certificates issued by unexpected or unknown certificate authorities.
- Unexpected RPC traffic patterns to hosts that do not match the pinned or expected server endpoints.
- Application logs showing successful Thrift calls despite certificate chain anomalies recorded by network inspection tools.
Detection Strategies
- Inventory Python environments for installed thrift package versions and flag any release earlier than 0.25.0.
- Use software composition analysis to identify applications bundling vulnerable Apache Thrift Python bindings.
- Capture TLS metadata at egress points and correlate server certificate fingerprints against an allowlist of expected Thrift service certificates.
Monitoring Recommendations
- Monitor outbound connections from services known to use Thrift Python bindings for new or unexpected destination IPs and ports.
- Alert on TLS sessions where the presented certificate does not chain to a trusted internal certificate authority.
- Track process-level network telemetry to detect Thrift clients negotiating TLS with hosts outside documented service inventories.
How to Mitigate CVE-2026-85087
Immediate Actions Required
- Upgrade Apache Thrift Python bindings to version 0.25.0 or later across all affected applications.
- Rebuild and redeploy container images and virtual environments that pin older thrift releases.
- Rotate any credentials or secrets that were transmitted through Thrift RPC calls over untrusted networks.
Patch Information
The Apache Software Foundation fixed the issue in Apache Thrift 0.25.0. The release corrects the certificate validation path so that failed verifications return an error status to callers. Review the Apache Mailing List Discussion for the maintainer announcement and upgrade guidance.
Workarounds
- Restrict Thrift Python client traffic to trusted network segments such as service meshes with mutual TLS enforced at the proxy layer.
- Terminate TLS at a hardened reverse proxy that performs certificate validation before forwarding plaintext Thrift traffic over a loopback or protected channel.
- Implement certificate pinning or allowlisting in application code to reject unexpected server certificates independent of the bindings' status code.
# Configuration example
pip install --upgrade "thrift>=0.25.0"
pip show thrift | grep -i version
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

