FreeRDP before 3.32.2 Use-After-Free via DRDYNVC Tracker Race
Only FreeRDP before 3.32.2 running freerdp-proxy with the static drdynvc channel intercepted is affected. The fix is in FreeRDP 3.32.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 3.32.2
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected: FreeRDP before 3.32.2 (freerdp-proxy DRDYNVC tracker) proxy must be configured to intercept the static drdynvc channel an authenticated front session with active dynamic-channel data is required a default proxy without an intercepting module or Intercept=drdynvc does not reach the affected route
- Exploitation15/40CISA rates a proof of concept as public
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity8.2/10CVSS 8.2
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
CVE-2026-121961 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.2 (high) and affects FreeRDP; fixed in 3.32.2.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 35/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 3.32.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
The freerdp-proxy component of FreeRDP, the open-source Remote Desktop Protocol library, can be crashed by a malicious target server that the proxy connects to, with no login or user action needed. Exploiting a race in its DRDYNVC channel handling could let an attacker crash the proxy process, causing a denial of service.
Read the original description
FreeRDP before 3.32.2 contains a use-after-free vulnerability in the freerdp-proxy DRDYNVC tracker when intercepting the drdynvc channel. A malicious target server can repeatedly send CREATE_REQUEST_PDU for an active channel id, racing front DATA handling to free a borrowed context and crash the proxy process.
What to do
Check whether your setup matches what the bug needs.
Affected: FreeRDP before 3.32.2 (freerdp-proxy DRDYNVC tracker) proxy must be configured to intercept the static drdynvc channel an authenticated front session with active dynamic-channel data is required a default proxy without an intercepting module or Intercept=drdynvc does not reach the affected routeUpgrade to a fixed version: 3.32.2.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- FreeRDP FreeRDP
fixed in 3.32.2
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121961
Is CVE-2026-121961 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A use-after-free in the freerdp-proxy DRDYNVC tracker can be reached through a race. The demonstrated impact is a crash of the proxy process, which is a denial of service. No code execution, controlled replacement or information disclosure was demonstrated.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-121961?
FreeRDP: before 3.32.2.Source: cve.now feed data
Am I affected, and how do I check?
FreeRDP versions before 3.32.2 are affected, but only when freerdp-proxy is configured to intercept the static drdynvc channel, either through an intercepting module or an explicit Intercept=drdynvc setting. A default proxy with all features on, and without either of these, does not reach the affected route. The attack also requires an authenticated front session with active dynamic-channel data. To check, confirm the installed FreeRDP version and review the proxy configuration for an intercepting module or Intercept=drdynvc.Source: vulncheck.com, github.com
How do I fix CVE-2026-121961?
Upgrade FreeRDP to 3.32.2 or later, which contains the fix. No workaround is listed in the facts.Source: vulncheck.com, github.com