Skip to content
VulniPulse
Medium6.9Apache Software Foundation

CVE-2026-85088: Improper Validation of Certificate with Host Mismatch in the C++ and D libraries of Apache Thrift

This Apache advisory covers CVE-2026-85088 in Apache Thrift.

Open the Apache advisory

Key facts

Vendor rating
Medium, CVSS 6.9
CVSS vector
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:U · base score 6.9, scored by apacheAttack vector: network. Attack complexity: high. Attack requirements: present. Privileges required: none. User interaction: none. Confidentiality impact on the vulnerable system: high. Integrity impact on the vulnerable system: high. Availability impact on the vulnerable system: none. Confidentiality impact on subsequent systems: none. Integrity impact on subsequent systems: none. Availability impact on subsequent systems: none.
Weakness
  • CWE-295 Improper certificate validation
  • CWE-297 Improper validation of certificate with host mismatch
EPSS
0.17% chance of exploitation in the next 30 days (6th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: no. Technical impact: total. CISA, .
CISA KEV
Not listed (catalogue checked )
Affected
0.7.0 through 0.24.0; 0.9.0 through 0.24.0.
Fixed in
0.25.0
Source published
Source revised
Listed by VulniPulse

Compiled by VulniPulse from the linked sources. How records are collected and checked.

Affected products & platforms

Apache Software FoundationApache Thrift

Description

Improper Validation of Certificate with Host Mismatch in the C++ and D libraries of Apache Thrift.

Both libraries install a default access manager for client sockets — TSSLSocketFactory does so in C++, and the accessManager property does so in D — which compares the peer certificate against the host

name that was connected to. That comparison walks the subjectAltName dNSName entries first and consults the certificate Common Name afterwards.

A name that does not match yields a "skip" result rather than

a rejection, so a certificate whose subjectAltName entries are all present and all non-matching falls through to the Common Name, which can then satisfy the check.

RFC 6125 section 6.4.4, and RFC 9525 section 2, require that the Common Name is not consulted when a dNSName subjectAltName is present. A certificate carrying subjectAltName entries for one name and a

Common Name for another is therefore accepted for a connection to the second name.

Exploitation requires an attacker positioned on the network path who holds a certificate that chains to a certificate authority in the client's trust store and whose Common Name matches the connected host

Public certificate authorities have not issued on Common Name alone for many years, so this is principally a concern for deployments using a private or enterprise public-key infrastructure.

Text from the source record.

Affected versions
  • 0.7.0 through 0.24.0
  • 0.9.0 through 0.24.0.

Official advisory · high-confidence parse· fetched ·verify at source

How to fix CVE-2026-85088

Upgrade to a fixed release named by Apache:

  • 0.25.0

Vendor guidance

  • Both libraries install a default access manager for client sockets — TSSLSocketFactory does so in C++, and the accessManager property does so in D — which compares the peer certificate against the host name that was connected to.
  • Users should upgrade to 0.25.0.

CVE-2026-85088 in other vendors' advisories

  • Red Hat: CVE-2026-85088, high severity, fixed in 0.25.0, thrift-main-0.25.0-0.1.hum1, RHSA-2026:74369

Compare every advisory for CVE-2026-85088

Apache Software Foundation advisories, October 2026All Apache Software Foundation advisories

Get an email when Apache publishes the next one.

See Apache's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Apache