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-85088 Overview
CVE-2026-85088 is an improper certificate validation flaw [CWE-295] affecting the C++ and D libraries of Apache Thrift. The default access manager installed by TSSLSocketFactory in C++ and the accessManager property in D compares the peer certificate against the connected host name incorrectly. When subjectAltName dNSName entries are present but none match, the implementation falls through to the certificate Common Name instead of rejecting the certificate. This violates RFC 6125 section 6.4.4 and RFC 9525 section 2, which prohibit consulting the Common Name when a dNSName subjectAltName is present. The flaw affects the C++ library from 0.7.0 through 0.24.0 and the D library from 0.9.0 through 0.24.0.
Critical Impact
A network-positioned attacker holding a certificate chained to a trusted CA with a matching Common Name can impersonate arbitrary Thrift servers, breaking the confidentiality and integrity guarantees of TLS.
Affected Products
- Apache Thrift C++ library versions 0.7.0 through 0.24.0
- Apache Thrift D library versions 0.9.0 through 0.24.0
- Applications relying on the default TSSLSocketFactory access manager for peer certificate verification
Discovery Timeline
- 2026-10-02 - CVE-2026-85088 published to NVD
- 2026-10-02 - Last updated in NVD database
Technical Details for CVE-2026-85088
Vulnerability Analysis
The vulnerability resides in the default client-side access manager that Apache Thrift installs for TLS connections. During the TLS handshake, the access manager iterates through the peer certificate's subjectAltName dNSName entries and compares each against the host name the client intended to connect to. A non-matching entry returns a "skip" result rather than a rejection. After exhausting all subjectAltName entries, the implementation consults the Common Name as a fallback.
RFC 6125 and the more recent RFC 9525 explicitly require that the Common Name must not be consulted when any dNSName subjectAltName is present. The Thrift implementation violates this requirement. As a result, a certificate carrying subjectAltName entries for foo.example.com and a Common Name of bar.example.com is accepted when the client connects to bar.example.com. This weakens the trust binding between the identity the client requested and the identity actually presented.
Root Cause
The root cause is incorrect handshake logic in the default access manager implementation. The "skip" semantics for non-matching subjectAltName entries allow the verification routine to continue walking the certificate rather than terminating with a rejection once dNSName entries are known to be present.
Attack Vector
Exploitation requires an attacker positioned on the network path between a Thrift client and server. The attacker must present a certificate that chains to a certificate authority in the client's trust store and whose Common Name matches the host name the client is connecting to. Public certificate authorities stopped issuing on Common Name alone many years ago, so the practical exposure is largely limited to environments relying on private or enterprise public-key infrastructure (PKI) where internal CAs may still issue certificates with meaningful Common Names.
An attacker meeting these conditions can perform a man-in-the-middle attack against TLS-protected Thrift RPC traffic, intercepting and modifying method invocations and responses.
Detection Methods for CVE-2026-85088
Indicators of Compromise
- Unexpected TLS session establishment between Thrift clients and hosts that are not the intended RPC endpoints
- Peer certificates presented to Thrift clients where the Common Name does not appear in any subjectAltName dNSName entry
- Internal PKI certificate issuance events for Common Names that duplicate production service host names
Detection Strategies
- Inventory applications linking against Apache Thrift C++ or D libraries at versions between 0.7.0/0.9.0 and 0.24.0 using software composition analysis
- Capture TLS handshakes on Thrift RPC ports and inspect server certificate subjectAltName and Common Name fields for mismatches
- Correlate internal CA issuance logs with observed certificates presented on the network to identify suspicious issuance
Monitoring Recommendations
- Enable certificate transparency monitoring for internal PKI if supported, and alert on issuance of certificates whose Common Name matches production service identities
- Log client-side TLS verification outcomes in Thrift-based services and alert on peer certificates whose matched identity came from the Common Name rather than a subjectAltName
- Monitor outbound Thrift RPC flows for unexpected destination IP addresses or ASNs that deviate from documented service maps
How to Mitigate CVE-2026-85088
Immediate Actions Required
- Upgrade all Apache Thrift C++ and D library deployments to version 0.25.0
- Audit internal certificate authority policies to prohibit issuance of certificates where the Common Name is not also listed in subjectAltName
- Review existing internal certificates for Common Name values that do not appear in the subjectAltName field and reissue as needed
Patch Information
Apache has released Apache Thrift 0.25.0, which corrects the access manager behavior to reject certificates per RFC 6125 and RFC 9525 when subjectAltName dNSName entries are present and non-matching. Details are available in the Apache Mailing List Thread 1 and Apache Mailing List Thread 2.
Workarounds
- Replace the default TSSLSocketFactory access manager with a custom implementation that strictly follows RFC 9525 host name verification semantics
- Restrict trusted CA bundles used by Thrift clients to only those CAs that issue certificates with correct subjectAltName entries
- Deploy mutual TLS and pin expected server certificates or public keys to limit the scope of acceptable peer certificates
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

