FreeRDP before 3.29.0 (affected versions <= 3.28.0) contains an improper certificate hostname validation vulnerability. (CVE-2026-67293)
FreeRDP before 3.29.0 (affected versions <= 3.28.0) contains an improper certificate hostname validation vulnerability. The TLS hostname matcher (tls_match_hostname() in libfreerdp/crypto/tls.c) treats a wildcard pattern such as *.example.com as matching any hostname ending in .example.com, so it incorrectly accepts a wildcard certificate for multi-label subdomains like a.b.example.com (which OpenSSL's X509_check_host() rejects). This weakens TLS server authentication under wildcard-certificate conditions.
AI Analysis
Technical Summary
FreeRDP before version 3.29.0 has a vulnerability in its TLS hostname matcher (tls_match_hostname() in libfreerdp/crypto/tls.c) where wildcard certificates such as *.example.com are incorrectly accepted for multi-label subdomains like a.b.example.com. This behavior deviates from the expected validation performed by OpenSSL's X509_check_host(), thereby weakening TLS server authentication under wildcard-certificate conditions. The vulnerability is identified as CWE-295 and has a CVSS 3.1 base score of 4.2, indicating a low severity impact on confidentiality and integrity with no impact on availability.
Potential Impact
The vulnerability allows improper validation of TLS server certificates when wildcard certificates are used, potentially enabling an attacker to impersonate TLS servers for multi-label subdomains. This weakens the assurance of server identity during TLS connections, which could lead to limited confidentiality and integrity impacts. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrade FreeRDP to version 3.29.0 or later, where this improper certificate hostname validation vulnerability is fixed. Patch status is confirmed by the version boundary in the description. No other mitigation steps are indicated.
FreeRDP before 3.29.0 (affected versions <= 3.28.0) contains an improper certificate hostname validation vulnerability. (CVE-2026-67293)
Description
FreeRDP before 3.29.0 (affected versions <= 3.28.0) contains an improper certificate hostname validation vulnerability. The TLS hostname matcher (tls_match_hostname() in libfreerdp/crypto/tls.c) treats a wildcard pattern such as *.example.com as matching any hostname ending in .example.com, so it incorrectly accepts a wildcard certificate for multi-label subdomains like a.b.example.com (which OpenSSL's X509_check_host() rejects). This weakens TLS server authentication under wildcard-certificate conditions.
CVSS v3.1
Score 4.2medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
FreeRDP before version 3.29.0 has a vulnerability in its TLS hostname matcher (tls_match_hostname() in libfreerdp/crypto/tls.c) where wildcard certificates such as *.example.com are incorrectly accepted for multi-label subdomains like a.b.example.com. This behavior deviates from the expected validation performed by OpenSSL's X509_check_host(), thereby weakening TLS server authentication under wildcard-certificate conditions. The vulnerability is identified as CWE-295 and has a CVSS 3.1 base score of 4.2, indicating a low severity impact on confidentiality and integrity with no impact on availability.
Potential Impact
The vulnerability allows improper validation of TLS server certificates when wildcard certificates are used, potentially enabling an attacker to impersonate TLS servers for multi-label subdomains. This weakens the assurance of server identity during TLS connections, which could lead to limited confidentiality and integrity impacts. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrade FreeRDP to version 3.29.0 or later, where this improper certificate hostname validation vulnerability is fixed. Patch status is confirmed by the version boundary in the description. No other mitigation steps are indicated.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-wc6m-wggm-hjr8
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-67293"]
- Database Specific Severity
- CRITICAL
- Cvss Version
- 3.1
Threat ID: 6a6e6298bf32cb7a344f9d1f
Added to database: 08/01/2026, 21:18:16 UTC
Last enriched: 08/01/2026, 21:24:15 UTC
Last updated: 09/15/2026, 22:01:36 UTC
Views: 54
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.