FreeRDP 3.0.0 before 3.32.0 allows HTTP header injection in its proxy because a lone LF in the target portion of a routing token (Cookie: msts=) is not rejected and is written by http_proxy_connect into the CONNECT request line and Host header. A remote unauthenticated RDP client connecting to a proxy using FixedTarget=false and an upstream HTTP proxy can alter HTTP request/header framing at that upstream proxy.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-87v8-2gwr-ww9j Exploit, Vendor Advisory
- https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-87v8-2gwr-ww9j 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:51
- StatusUndergoing Analysis → AnalyzedNVD modified 2026-10-23 20:51
- StatusReceived → Undergoing AnalysisNVD modified 2026-10-15 15:54
- First seenCVSS 6.3NVD modified 2026-10-14 23:17
Affected (CPE criteria) 1
cpe:2.3:a:freerdp:freerdp:*:*:*:*:*:*:*:*
References 3
- https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-87v8-2gwr-ww9j Exploit, Vendor Advisory
- https://www.vulncheck.com/advisories/freerdp-3.0.0-before-3.32.0-http-header-injection-via-proxy-routing-token Third Party Advisory
- https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-87v8-2gwr-ww9j Exploit, Vendor Advisory