CVE-2026-25997
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 · uneditedFreeRDP is a free implementation of the Remote Desktop Protocol. Prior to version 3.23.0, `xf_clipboard_format_equal` reads freed `lastSentFormats` memory because `xf_clipboard_formats_free` (called from the cliprdr channel thread during auto-reconnect) frees the array while the X11 event thread concurrently iterates it in `xf_clipboard_changed`, triggering a heap use after free. 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 confidenceHeap use-after-free vulnerability in FreeRDP's clipboard handling where a race condition exists between the cliprdr channel thread (which frees `lastSentFormats` via `xf_clipboard_formats_free` during auto-reconnect) and the X11 event thread (which iterates the same array in `xf_clipboard_changed` and reads freed memory in `xf_clipboard_format_equal`). This concurrent access without proper synchronization can lead to arbitrary code execution.
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< 3.23.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check FreeRDP versionRun `freerdp-version` or `xfreerdp --version` to display the installed FreeRDP version numberAffected if The reported version is less than 3.23.0 (e.g., 3.22.0, 3.0.x, 2.x)
-
Identify running FreeRDP processesRun `ps aux | grep -i freerdp` to list any active FreeRDP client processesAffected if FreeRDP processes are running and their version is below 3.23.0
-
Verify clipboard redirection is enabledInspect the connection command or configuration for the `/clipboard` or `-clipboard` parameter, or check if clipboard sync works in an active sessionAffected if Clipboard redirection is enabled (the default setting) and the FreeRDP version is vulnerable
-
Check for cliprdr channel usageReview session logs or connection parameters for evidence of the cliprdr (clipboard) channel being negotiated and activeAffected if The cliprdr channel is present in the session and the FreeRDP version is below 3.23.0
You are affected if you are running any FreeRDP version prior to 3.23.0 with clipboard synchronization enabled and the cliprdr channel in use, as this creates the race condition window for the use-after-free vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.23.0
Upgrade to FreeRDP version 3.23.0 or later. As an immediate workaround, consider disabling clipboard synchronization or restricting network exposure until the patch can be applied.
3.23.0
- Check current FreeRDP version using 'freerdp-version' or 'xfreerdp --version'
- Upgrade FreeRDP to version 3.23.0 or later via package manager (e.g., 'apt update && apt install freerdp' or equivalent) or rebuild from source
- Verify the upgrade was successful by checking the version again
- Restart any running FreeRDP sessions to ensure the patched version is loaded
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25997 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-25997 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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