LiveActive security incident?Get immediate response
CVE Record

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.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

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.
Prepared
Confidence
high
Sources
5

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-66402 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9VulnCheck
9.3CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NVulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

9.3Critical
CVSS 4.0 vector shape for CVE-2026-66402Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
FreeRDPFreeRDP0, 3.29.0unaffected
Weakness

CWE details

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.