Linux · 
Rocky Linux · Security advisory · August 13, 2026
Rocky Linux · Security advisory · August 13, 2026RLSA-2026:54486: freerdp security update
RLSA-2026:54486, released August 13, 2026, fixes 6 CVEs in freerdp (version 2:3.10.3-12.el10_2.8). None of them is reported as exploited. Patch Radar priority: High.
High
CVEs closed
6
None rated Critical
Exploited
0
None reported
Highest CVSS
9.1
Base score, 0 to 10
Highest EPSS
0.0091
60th percentile
Priority of the 6 CVEs
Patch now 0
Urgent 0
High 6
Routine 0
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| freerdp | rocky 10 | 2:3.10.3-12.el10_2.8 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| High | CVE-2026-64620 | freerdp3-shadow-x11: FreeRDP before 3.28.0 (affected <=3.27.1) contains a heap-based buffer overflow in crypto_rsa_common() (libfreerdp... | 9.1 | 0.0091 | None reported |
| High | CVE-2026-67289 | freerdp: FreeRDP is a free implementation of the Remote Desktop Protocol (RDP), released under the Apache license | 8.1 | 0.0043 | None reported |
| High | CVE-2026-67299 | freerdp3: FreeRDP before 3.29.0 contains a client-side heap use-after-free in the async update message proxy for WINDOW_ICON_OR... | 8.1 | 0.0040 | None reported |
| High | CVE-2026-64621 | freerdp3: FreeRDP before 3.28.0 (affected 3.x through 3.27.1) contains a double-free vulnerability in freerdp_client_rdp_file_a... | 8.1 | 0.0036 | None reported |
| High | CVE-2026-68580 | freerdp3: FreeRDP before 3.29.0 contains integer overflow vulnerabilities in the audio input redirection channel (audin) across... | 8.1 | 0.0030 | None reported |
| High | CVE-2026-64624 | freerdp3-shadow-x11: FreeRDP before 3.28.0 treats lines beginning with forward slash in RDP files as raw command-line options, exposing th... | 8.1 | 0.0018 | None reported |
Showing 1 to 6 of 6
1
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.