CVE-2026-67293
FreeRDP wildcard TLS hostname validation allows authentication bypass.
Is CVE-2026-67293 being exploited?
Not confirmed. CVE-2026-67293 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.17% probability of exploitation in the next 30 days.
How severe is CVE-2026-67293?
CVE-2026-67293 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-67293?
Yes. A fix has been recorded for CVE-2026-67293. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67293 affect?
CVE-2026-67293 affects FreeRDP <= 3.28.0, RDP clients using FreeRDP, Linux thin clients, Embedded devices using FreeRDP. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67293?
Upgrade FreeRDP to >=3.29.0 and enforce strict hostname verification.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Allows MITM or malicious servers to impersonate RDP servers via wildcard certs for multi-label subdomains, enabling session interception/modification.
Immediate action required
- affected< 3.29.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.