FreeRDP from 3.0.0-beta1 before 3.32.0 fails to enforce cumulative or absolute size limits when reassembling RDPDR channel fragments in the proxy. Attackers can send a FIRST fragment followed by continuation fragments without LAST, growing per-session heap streams proportional to traffic and exhausting proxy memory.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-m7g5-gw57-cwcr 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-23 20:29
- StatusUndergoing Analysis → AnalyzedNVD modified 2026-10-23 20:29
- StatusReceived → Undergoing AnalysisNVD modified 2026-10-15 15:54
- First seenCVSS 8.2NVD modified 2026-10-14 23:17
Affected (CPE criteria) 1
cpe:2.3:a:freerdp:freerdp:*:*:*:*:*:*:*:*
References 2
- https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-m7g5-gw57-cwcr Exploit, Vendor Advisory
- https://www.vulncheck.com/advisories/freerdp-before-3.32.0-unbounded-memory-retention-via-rdpdr-proxy Third Party Advisory