Medium 4.0Published Oct 14, 2026

CVE-2026-110835FreeRDP 3.0.0 before 3.32.0 HTTP Header Injection via Proxy Routing Token

Updated under an hour ago (2026-10-19 06:30 UTC)

Does this affect you?

It affects FreeRDP. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for FreeRDP

Exploited in the last 30 days

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.

CVSS: 4.0 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N
Weakness (CWE): CWE-93
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: VulnCheck
NVD analysis: Undergoing Analysis
Record last updated: Oct 18, 2026
First seen by InfoSec Signals: Oct 14, 2026

Affected products

Affected products

FreeRDP FreeRDP freerdp:freerdp (from the name)	from 3.0.0 before 3.32.0; 3.32.0 not affected	CNA record

References

https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-87v8-2gwr-ww9jvendor-advisory
https://www.vulncheck.com/advisories/freerdp-3.0.0-before-3.32.0-http-header-injection-via-proxy-routing-tokenthird-party-advisory

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.