FreeRDP 3.11.0 before 3.32.0 does not validate that AVC444 and AVC444v2 region widths are even before YUV444 conversion, so an odd width reaches an assertion and aborts the client. A malicious or compromised RDP server can terminate a connected FreeRDP client after RDPGFX AVC444 negotiation by sending an in-bounds region rectangle with an odd width.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-97pf-pwp3-2wrv Exploit, Vendor Advisory
- https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-97pf-pwp3-2wrv Exploit, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 4
- Cpes+1 CPE criteria (now 1)NVD modified 2026-10-21 15:02
- StatusUndergoing Analysis → AnalyzedNVD modified 2026-10-21 15:02
- StatusAwaiting Analysis → Undergoing AnalysisNVD modified 2026-10-18 12:17
- First seenCVSS 7.1NVD modified 2026-10-14 20:10
Affected (CPE criteria) 1
cpe:2.3:a:freerdp:freerdp:*:*:*:*:*:*:*:*
References 3
- https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-97pf-pwp3-2wrv Exploit, Vendor Advisory
- https://www.vulncheck.com/advisories/freerdp-3.11.0-before-3.32.0-reachable-assertion-via-avc444-odd-region-width Third Party Advisory
- https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-97pf-pwp3-2wrv Exploit, Vendor Advisory