Live › vulnerability › CVE-2026-114047
Go to dashboardFreeRDP's proxy accepts any target TLS certificate when no verification module is configured. A network attacker who intercepts the proxy's outbound connection can impersonate the RDP target and receive the proxied session data.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Teams running the FreeRDP proxy between clients and RDP targets from version 2.0.0 up to but not including 3.32.0 are exposed, especially where no verification module is configured. The risk depends on an attacker being positioned on the network path between the proxy and the RDP target. Teams not using the FreeRDP proxy, or running 3.32.0 or later, can skip it.
No product ranges from the sources yet.
xfreerdp --version or the packaged version of FreeRDP (proxy component) on hosts that run the FreeRDP proxy.3.32.0 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
FreeRDP from 2.0.0 before 3.32.0 contains an improper certificate validation vulnerability in its proxy that accepts untrusted target TLS certificates when no verification module is configured. Network-positioned attackers can intercept the proxy's outbound connection and present a self-signed, wrong-hostname certificate to impersonate the RDP target and receive proxied session data.
This page as .md · .json · in your agent: get_signal("CVE-2026-114047")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.