dbcve.org
FreerdpApplication

CVE-2026-25952

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-25
Fix available
A fix is available. Upgrade to 3.23.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to version 3.23.0, `xf_SetWindowMinMaxInfo` dereferences a freed `xfAppWindow` pointer because `xf_rail_get_window` in `xf_rail_server_min_max_info` returns an unprotected pointer from the `railWindows` hash table, and the main thread can concurrently delete the window (via a window delete order) while the RAIL channel thread is still using the pointer. Version 3.23.0 fixes the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Use-after-free vulnerability in FreeRDP's RAIL module where `xf_rail_get_window` returns an unprotected pointer from the `railWindows` hash table. The main thread can concurrently delete the window via a window delete order while the RAIL channel thread is still using the pointer in `xf_SetWindowMinMaxInfo`, leading to a race condition and use-after-free.

MitigationUpgrade FreeRDP to version 3.23.0 or later which fixes the race condition by properly synchronizing window pointer access between threads. If immediate upgrade is not feasible, minimize exposure by restricting RDP connections to trusted sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FreerdpApplication
Affected:< 3.23.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if FreeRDP is installed
    Run 'freerdp-version' or check for freerdp binaries in /usr/bin/ or /usr/local/bin/. Also check for libfreerdp libraries in /usr/lib/
    Affected if No FreeRDP installation found means not affected by this specific vulnerability
  2. Determine FreeRDP version
    Run 'freerdp-version' or check package manager (dpkg -l freerdp, rpm -qi freerdp, or similar). Compare the version number to the affected range: < 3.23.0
    Affected if Installed version is less than 3.23.0 - user is in affected version range
  3. Verify RAIL module is loaded or used
    Inspect RDP session parameters for RAIL/remote app usage (look for /app flag, remote application mode, or RAIL-related channel flags in connection logs). Check if libfreerdp-rail.so or similar RAIL module exists in the system
    Affected if RAIL module is loaded or remote application features are in use - the vulnerable code path is exercised
  4. Confirm concurrent window operations can occur
    Review RDP session logs or network captures for 'rail' channel activity and window management operations (window create, delete, min/max info). The race condition requires the RAIL channel thread and main thread to act on the same window simultaneously
    Affected if RAIL channel is active with concurrent window delete orders and SetWindowMinMaxInfo requests - conditions for the race condition exist

User is affected if FreeRDP version is below 3.23.0 AND the RAIL/remote application feature is being used, allowing the race condition between window deletion and window info requests to trigger the use-after-free.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.23.0 or later
Fixed in 3.23.0
Vendor patch github.com →
Interim mitigation

Upgrade FreeRDP to version 3.23.0 or later which fixes the race condition by properly synchronizing window pointer access between threads. If immediate upgrade is not feasible, minimize exposure by restricting RDP connections to trusted sources.

Recommended fix High confidence

FreeRDP 3.23.0

  1. Check current FreeRDP version installed (e.g., freerdp-version, dpkg -l freerdp, or rpm -qi freerdp)
  2. Upgrade FreeRDP to version 3.23.0 or later using the package manager or build from source (e.g., git clone https://github.com/FreeRDP/FreeRDP.git && cd FreeRDP && git checkout 3.23.0 and rebuild)
  3. Verify the upgrade was successful by checking the version again

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Freerdp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,248.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25952 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-25952 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data