CVE-2026-57158 in FreeRDP
FreeRDP is a free implementation of the Remote Desktop Protocol. From 3.21.0 before 3.28.0, FreeRDP clients using the GFX pipeline contain an incomplete fix for CVE-2026-23530 in planar_decompress_plane_rle_only in libfreerdp/codec/planar.c, allowing a malicious RDP server to...
Quick answer
FreeRDP should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- FreeRDP >=3.21.0 <3.28.0
Fixed versions
- FreeRDP 3.28.0 or later
How to fix it
Update FreeRDP. A malicious RDP peer can trigger memory bugs in old FreeRDP builds.
- Upgrade FreeRDP to FreeRDP 3.28.0 or later.
- Restart apps or services that load FreeRDP.
- Avoid connecting to untrusted RDP servers until patched.
- Update packaged clients on all desktops and servers.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Run xfreerdp /version or your package manager and confirm the fixed version.
- Scan again and confirm CVE-2026-57158 is gone.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-57158?
FreeRDP versions listed as affected should be reviewed: FreeRDP >=3.21.0 <3.28.0.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.