CVE-2026-67294 Overview
CVE-2026-67294 is a certificate validation flaw in FreeRDP versions prior to 3.29.0. The vulnerability resides in the x509_utils_verify() function, which performs Extended Key Usage (EKU) checks on the server's TLS certificate during Remote Desktop Protocol (RDP) client authentication. When server-purpose verification (X509_PURPOSE_SSL_SERVER) fails, the code falls back to client-purpose and any-purpose verification. An attacker holding a trusted, hostname-matching certificate issued for clientAuth only can therefore impersonate an RDP server. The weakness is tracked under [CWE-295: Improper Certificate Validation].
Critical Impact
A clientAuth-only certificate issued by a trusted certificate authority can be accepted as a valid RDP server certificate, enabling man-in-the-middle attacks against FreeRDP clients.
Affected Products
- FreeRDP versions prior to 3.29.0
- Applications and distributions that embed the FreeRDP library for RDP client functionality
- Environments that rely on EKU separation between client and server certificates issued by the same CA
Discovery Timeline
- 2026-08-01 - CVE-2026-67294 published to the National Vulnerability Database (NVD)
- 2026-08-03 - Last updated in NVD database
Technical Details for CVE-2026-67294
Vulnerability Analysis
FreeRDP validates the server's TLS certificate through x509_utils_verify() in its cryptographic helper layer. The function is expected to enforce that the peer certificate carries the serverAuth EKU when verifying an RDP server. Instead, if verification against X509_PURPOSE_SSL_SERVER fails, the routine retries with X509_PURPOSE_SSL_CLIENT and then with an any-purpose check.
This fallback logic collapses the semantic distinction the EKU field is designed to enforce. Any certificate chained to a trusted CA and containing a hostname that matches the target RDP server passes verification, regardless of whether it was issued for client or server authentication. The flaw affects the confidentiality and integrity of the RDP session because it enables an adversary to terminate TLS and relay or inspect traffic.
Root Cause
The root cause is improper certificate purpose validation. The verification path treats client-purpose and any-purpose success as equivalent to server-purpose success. In enterprise environments where a single internal CA issues both client and server certificates, any principal with a clientAuth certificate becomes capable of masquerading as an RDP server.
Attack Vector
The attack is network-based and requires no authentication or user interaction. An adversary positioned to intercept RDP traffic, such as through Address Resolution Protocol (ARP) spoofing, Domain Name System (DNS) poisoning, or a rogue Wi-Fi access point, presents their clientAuth certificate to the FreeRDP client. Because the certificate chains to a trusted CA and matches the expected hostname, the client completes the TLS handshake and forwards credentials and session data to the attacker.
The vulnerability mechanism is described in detail in the FreeRDP GitHub Security Advisory GHSA-89c6-jjrw-96h4 and the VulnCheck Advisory. The upstream fix is provided in the FreeRDP commit f3b43471.
Detection Methods for CVE-2026-67294
Indicators of Compromise
- RDP sessions terminating at unexpected intermediate hosts or IP addresses inconsistent with published server inventories.
- TLS certificates presented to RDP clients that carry only the clientAuth EKU rather than serverAuth.
- Anomalous ARP or DNS records preceding RDP connection attempts from FreeRDP-based clients.
Detection Strategies
- Inspect network captures for TLS handshakes on TCP/3389 where the server certificate lacks the serverAuth EKU.
- Correlate FreeRDP client versions across the fleet with the fixed release baseline of 3.29.0.
- Baseline certificate authorities and EKUs used by known RDP servers, and alert on deviations observed by FreeRDP endpoints.
Monitoring Recommendations
- Log the certificate chain, subject, and EKUs presented during outbound RDP connections from Linux and cross-platform workstations.
- Monitor for FreeRDP process invocations connecting to hosts outside authorized RDP infrastructure.
- Track patch state of packages that bundle FreeRDP, including Remmina, Weston, and downstream Linux distribution builds.
How to Mitigate CVE-2026-67294
Immediate Actions Required
- Upgrade FreeRDP to version 3.29.0 or later across all systems that use the library directly or through downstream applications.
- Inventory internal CAs and confirm that any CA trusted by RDP clients does not issue clientAuth certificates to untrusted principals.
- Restrict RDP traffic to known server networks using firewall or Zero Trust segmentation policies.
Patch Information
The FreeRDP project addressed the flaw in version 3.29.0. The fix updates x509_utils_verify() to remove the fallback to client-purpose and any-purpose verification, ensuring only certificates valid for X509_PURPOSE_SSL_SERVER are accepted for server authentication. Refer to the upstream commit f3b43471 and the GHSA-89c6-jjrw-96h4 advisory for release details.
Workarounds
- Pin RDP server certificates in the FreeRDP known_hosts store so unexpected certificates prompt user confirmation.
- Issue RDP server certificates from a dedicated intermediate CA that never signs clientAuth-only certificates, and distrust general-purpose CAs on RDP clients.
- Tunnel RDP traffic through an authenticated Virtual Private Network (VPN) or RDP gateway to remove the man-in-the-middle position from the threat model.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
