Medium [CVE-2026-67289] HTTP Proxy Request Injection via Redirection
This medium-severity Red Hat Linux advisory covers CVE-2026-67289 affecting Red Hat Enterprise Linux 10.0 Extended Update Support, Red Hat Enterprise Linux 7 Extended Lifecycle Support, Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
FreeRDP before 3.29.0 (affected versions <= 3.28.0) does not validate CRLF and control characters in the server-controlled RDP redirection TargetNetAddress field.
This value is copied into the client's ServerHostname and, when the client connects through an HTTP proxy, is written directly into the proxy CONNECT request line and Host header by http_proxy_connect() without filtering.
A malicious or compromised RDP server can send a crafted redirection PDU containing embedded control characters to inject arbitrary headers/requests into the HTTP proxy CONNECT request. A flaw was found in FreeRDP.
This injection could allow an attacker to manipulate the proxy's behavior or bypass certain network security policies. Moderate: This client-side vulnerability in FreeRDP allows for HTTP proxy request injection.
Exploitation requires a FreeRDP client to be configured to use an HTTP proxy and to connect to a malicious or compromised RDP server, which then sends a crafted redirection PDU. This limits the attack surface to specific client configurations and interactions with untrusted RDP endpoints.
Red Hat severity: Moderate — CVSS 5 (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L). Weakness: CWE-93.
- < 3.29.0
- < 3.28.0
Official advisory · high-confidence parse· fetched 26 days ago·verify at source
- freerdp-2:3.10.3-12.el10_2.8
- freerdp-2:3.10.3-3.el10_0.11
- freerdp-0:2.1.1-5.el7_9.11
- freerdp-2:2.11.7-11.el8_10
- freerdp-2:2.2.0-14.el8_4.2
- freerdp-2:2.2.0-7.el8_6.11
- freerdp-2:2.2.0-12.el8_8.10
- freerdp-2:2.11.7-7.el9_8.5
- freerdp-2:2.4.1-6.el9_2.11
- freerdp-2:2.11.2-1.el9_4.10
- freerdp-2:2.11.7-1.el9_6.12
- RHSA-2026:54486
- RHSA-2026:58711
- RHSA-2026:62401
- RHSA-2026:54485
- RHSA-2026:60173
- RHSA-2026:61250
- RHSA-2026:61251
- RHSA-2026:54487
- RHSA-2026:58712
- RHSA-2026:58710
- RHSA-2026:58713
Official advisory · high-confidence parse· fetched 26 days ago·verify at source
Mitigation checklist
- To mitigate this issue, FreeRDP clients should avoid connecting to untrusted RDP servers when configured to use an HTTP proxy. Alternatively, if connecting to potentially untrusted RDP servers, disable the HTTP proxy configuration for FreeRDP.
Official advisory · high-confidence parse· fetched 26 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.