FreeRDP 3.0.0 before 3.32.0 does not remove card handles when Emulate_SCardReleaseContext releases a smartcard-emulation context, so Emulate_SCardTransmit later looks up the deleted parent context and reaches a terminating WINPR_ASSERT. A malicious RDP server can crash a connecting client with smartcard emulation and redirection enabled by releasing a context, establishing another, and issuing SCardTransmit with the stale card handle.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-f526-rq4j-5ch8 Exploit, Vendor Advisory, Mitigation
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 3
- Cpes+1 CPE criteria (now 1)NVD modified 2026-10-26 20:11
- StatusAwaiting Analysis → AnalyzedNVD modified 2026-10-26 20:11
- First seenCVSS 7.1NVD modified 2026-10-13 20:39
Affected (CPE criteria) 1
cpe:2.3:a:freerdp:freerdp:*:*:*:*:*:*:*:*
References 2
- https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-f526-rq4j-5ch8 Exploit, Vendor Advisory, Mitigation
- https://www.vulncheck.com/advisories/freerdp-3.0.0-before-3.32.0-reachable-assertion-via-stale-smartcard-handle Third Party Advisory