On this page (7 sections)
On 9 November 2026 Ubuntu published USN-9007-1, a security notice for FreeRDP, the open source RDP client library and tools. The notice says multiple security issues were fixed and that an attacker could possibly use them to obtain sensitive information, crash FreeRDP (denial of service), or execute arbitrary code.
If you run Ubuntu 24.04 LTS, 26.04 LTS or 26.10 on workstations, jump hosts or admin servers that connect to Windows machines over RDP, this update is worth applying soon. The notice does not give severity scores or per-issue details, so this article sticks to what Ubuntu has confirmed and focuses on how to check and fix your systems.
What Ubuntu has confirmed
The notice describes the problems only in general terms: FreeRDP contained multiple security issues, and the possible outcomes are information disclosure, a crash leading to denial of service, or arbitrary code execution. It does not say which CVE maps to which outcome, whether any of them need a malicious server or user interaction, or whether any are being exploited.
Ubuntu also notes that this update uses a new upstream FreeRDP release, so it includes additional bug fixes beyond the security patches. In general, a standard system update makes all the necessary changes.
Fixed package versions
Ubuntu lists these fixed versions per release. All three releases get FreeRDP 3.32.2 with an Ubuntu-specific suffix.
| Ubuntu release | Packages | Fixed version |
|---|---|---|
| 26.10 | freerdp-wayland, freerdp-x11, freerdp3-wayland, freerdp3-x11, libfreerdp3-3 | 3.32.2+dfsg-0ubuntu0.26.10.1 |
| 26.04 LTS | freerdp-wayland, freerdp-x11, freerdp3-wayland, freerdp3-x11, libfreerdp3-3 | 3.32.2+dfsg-0ubuntu0.26.04.1 |
| 24.04 LTS | freerdp3-wayland, freerdp3-x11, libfreerdp3-3 | 3.32.2+dfsg-0ubuntu0.24.04.1 |
Who is realistically exposed
The notice describes the freerdp3 package as an RDP client for Windows Terminal Services. That makes the most likely exposure any Ubuntu machine where a user or a script connects out to RDP servers using FreeRDP-based tools, or desktop remote-access apps that use the library.
Typical examples include admin workstations, support desktops, jump boxes used to reach Windows servers, and automation that opens RDP sessions. Servers that never run an RDP client are unlikely to have these packages installed, but it takes seconds to confirm. Because a library package such as libfreerdp3-3 can be installed as a dependency of other software, check for it even if you never installed FreeRDP on purpose.
The notice does not state whether exploitation requires connecting to a hostile or compromised RDP server. Until that is clear, a sensible assumption is that connecting to untrusted RDP hosts raises your risk.
How to check your systems
This read-only command lists installed FreeRDP-related packages and their versions on Ubuntu. Run it on each host; any version older than the fixed version for your release in the table above needs updating.
dpkg -l | grep -i freerdpTo see which version apt would install and whether your system already has it, query the policy for the library package. Compare the Installed and Candidate lines with the fixed version for your release.
apt-cache policy libfreerdp3-3To find out what depends on the library on a given machine, this read-only query lists installed packages that require it, which helps you spot desktop apps that use FreeRDP behind the scenes.
apt-cache rdepends --installed libfreerdp3-3What to do now
- Find every Ubuntu 24.04 LTS, 26.04 LTS and 26.10 host with FreeRDP packages installed, using the dpkg query above.
- Refresh package lists and upgrade the FreeRDP packages to the fixed version for your release.
- Close and reopen any running FreeRDP client sessions or remote-access apps so they load the updated library.
- Re-run the version check and confirm the installed version matches the table (3.32.2+dfsg-0ubuntu0.<release>.1).
- Until patched, avoid connecting to RDP servers you do not trust from unpatched machines.
- If a host does not need an RDP client at all, consider removing the package through your normal change process.
- Keep these hosts in your regular patch cycle so later Ubuntu notices for FreeRDP are applied quickly.
On Ubuntu, a standard update picks up the fix. The command below refreshes package lists and upgrades only the named packages; adjust the names to those present on your release (the 24.04 LTS list has no freerdp-x11 or freerdp-wayland packages). Afterwards, run the version check again.
sudo apt update
sudo apt install --only-upgrade libfreerdp3-3 freerdp3-x11 freerdp3-waylandIf you prefer to apply all pending updates, a full upgrade also works and matches the general approach Ubuntu describes.
sudo apt update && sudo apt upgradeMonitoring and follow-up
Because the notice lacks per-issue details, watch for updates to the CVE records and for upstream FreeRDP advisories that may add severity scores and attack conditions. If any of them turn out to be exploited in the wild, you will want to know quickly which hosts still run old versions, so keep an inventory of where FreeRDP is installed.
Also review which machines can reach RDP servers and from where. Restricting outbound RDP to known, managed servers reduces the chance that a client ever talks to a hostile host. For your own public-facing sites and servers, a regular security scan and certificate and DNS monitoring help you spot unexpected changes, though they do not replace patching client software like this.
For broader patching habits on small teams, see our guide on small business website security. More Ubuntu and Debian security notices are covered in the Webforta security blog.
What we do not know yet
- Which individual CVE causes information disclosure, a crash or code execution.
- CVSS scores or any official severity rating.
- Whether any of the issues are exploited in the wild.
- Whether exploitation needs a malicious RDP server, a crafted file or other user interaction.
- The full list of CVE identifiers, since the available text of the notice shows only a portion.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
