CVE-2026-66402: FreeRDP before 3.29.0 TLS Certificate Identity Validation Bypass
FreeRDP before 3.29.0 (affected versions <= 3.28.0) contains multiple TLS certificate identity validation weaknesses in tls_verify_certificate(), tls_match_hostname(), and x509_utils_get_dns_names(). Because FreeRDP performs custom Common Name and DNS SAN string matching instead of using OpenSSL's length-aware identity validation APIs, it (1) truncates DNS SAN values at embedded NUL bytes (accepting e.g. 'victim.example\0.attacker.example' as 'victim.example'), (2) accepts a matching Common Name even when non-matching DNS SAN entries are present, and (3) accepts IP-literal targets via DNS/CN matching without comparing iPAddress SANs. Under a trusted or misissued certificate chain, an attacker positioned to present such a certificate can bypass server identity verification, weakening TLS server authentication.
Security readout for executives and security teams
Plain-English summary
FreeRDP through 3.28.0 can mistake a malicious server certificate for one belonging to the intended RDP server. An attacker able to present a specially structured certificate under a trusted or misissued chain could impersonate that server, potentially exposing remote-session confidentiality and integrity.
Executive priority
Treat remediation as urgent where vulnerable FreeRDP clients access privileged or sensitive systems. Schedule rapid inventory and upgrade, while recognizing that exploitation requires additional certificate and connection-control conditions. No active exploitation is established by the supplied evidence.
Technical view
Custom certificate-name matching mishandles embedded NUL bytes in DNS SANs, permits Common Name matches despite conflicting DNS SANs, and validates IP-literal targets through DNS or Common Name matching rather than iPAddress SANs. These weaknesses bypass TLS server identity verification. FreeRDP 3.29.0 contains the referenced patch.
Likely exposure
Exposure is limited to deployments using FreeRDP versions through 3.28.0. Successful abuse also requires an attacker to present a crafted certificate chaining to a trusted or misissued certificate authority, typically while intercepting or redirecting the connection. The source bundle does not quantify deployment prevalence.
Exploitation context
The CVSS score is 9.8, but the source bundle does not establish active exploitation, and the CVE is not listed as KEV. Exploitation depends on certificate presentation and network positioning or redirection; the evidence does not support treating compromise as automatic for every vulnerable installation.
Researcher notes
The core defect is CWE-295 caused by custom, non-length-aware identity comparison instead of appropriate OpenSSL validation APIs. Assessment should cover all three paths: embedded-NUL DNS SAN handling, SAN precedence over Common Name, and IP-address SAN matching. Avoid interpreting the critical CVSS score as proof of exploitation.
Mitigation direction
Upgrade FreeRDP to version 3.29.0 or later.
Check vendor guidance and downstream package advisories for distribution-specific update instructions.
Prioritize systems carrying sensitive RDP sessions or operating across untrusted networks.
Investigate unexpected certificate warnings, endpoint changes, or RDP connection redirections.
Validation and detection
Inventory installed and embedded FreeRDP versions, including downstream packages and bundled applications.
Confirm no deployed FreeRDP version is 3.28.0 or earlier.
Verify installed packages incorporate the referenced patch commit when version numbering differs.
Review certificate and RDP connection telemetry for unexplained server identity changes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-295: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-295 · source CWE mapping
Improper Certificate Validation
Improper Certificate Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.