Linux · 
Ubuntu · Package update · February 9, 2026
Ubuntu · Package update · February 9, 2026libfreerdp-shadow2-2 2.6.1+dfsg1-3ubuntu2.10: libfreerdp-shadow2-2 2.6.1+dfsg1-3ubuntu2.10 for Ubuntu 22.04.1 LTS (jammy)
libfreerdp-shadow2-2 2.6.1+dfsg1-3ubuntu2.10, released February 9, 2026, fixes 8 CVEs in libfreerdp-shadow2-2. None of them is reported as exploited. Patch Radar priority: High.
High
CVEs closed
8
None rated Critical
Exploited
0
None reported
Highest CVSS
9.1
Base score, 0 to 10
Highest EPSS
0.0060
49th percentile
Priority of the 8 CVEs
Patch now 0
Urgent 0
High 8
Routine 0
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| libfreerdp-shadow2-2 | Ubuntu 22.04.1 LTS (jammy) | 2.6.1+dfsg1-3ubuntu2.10 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| High | CVE-2026-24684 | freerdp: Heap-use-after-free in play_thread (bsc#1257991). | 8.8 | 0.0060 | None reported |
| High | CVE-2026-24679 | freerdp: heap-buffer-overflow in urb_select_interface (bsc#1257986). | 9.1 | 0.0055 | None reported |
| High | CVE-2026-23948 | freerdp: @ehdgks0627 did some more fuzzying and found quite a number of client side bugs. | 8.8 | 0.0052 | None reported |
| High | CVE-2026-24675 | freerdp: heap-use-after-free in urb_select_interface (bsc#1257982). | 8.8 | 0.0052 | None reported |
| High | CVE-2026-24676 | freerdp: heap-use-after-free in audio_format_compatible (bsc#1257983). | 8.8 | 0.0052 | None reported |
| High | CVE-2026-24681 | freerdp: heap-use-after-free in urb_bulk_transfer_cb (bsc#1257988). | 8.8 | 0.0052 | None reported |
| High | CVE-2026-24682 | freerdp: heap-buffer-overflow in audio_formats_free (bsc#1257989). | 8.8 | 0.0052 | None reported |
| High | CVE-2026-24683 | freerdp: heap-use-after-free in ainput_send_input_event (bsc#1257990). | 8.8 | 0.0052 | None reported |
Showing 1 to 8 of 8
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.