dbcve.org
FreerdpApplication

CVE-2026-64621

HIGH · 7.3 CVSS v3.1 Developing Published 2026-07-20
Fix available
A fix is available. Upgrade to 3.28.0 or later.
See remediation →
76/100
Remediation priority · High
No privileges 4 weeks old

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 before 3.28.0 (affected 3.x through 3.27.1) contains a double-free vulnerability in freerdp_client_rdp_file_apply_to_settings() (client/common/file.c) when parsing the selectedmonitors field of a .rdp connection file. The MonitorIds array is allocated through the settings object, and a raw non-owning pointer to it is freed on the strtoul error path without clearing settings->MonitorIds, leaving it dangling; at teardown freerdp_settings_free() frees the same buffer again. An attacker who convinces a victim to open a crafted .rdp file with oversized monitor tokens can trigger a size-controlled double-free in any FreeRDP CLI client (xfreerdp/sdl-freerdp/wlfreerdp) in the default configuration.

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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-03.

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.0.0, < 3.28.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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
High

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

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.28.0 or later
Fixed in 3.28.0
Recommended fix Moderate confidence

FreeRDP 3.28.0 or later (any release >= 3.28.0)

  1. 1. Identify the current FreeRDP installation version by running 'xfreerdp --version' or checking your package manager
  2. 2. Update your system's package list (e.g., 'sudo apt-get update' for Debian/Ubuntu, or 'sudo yum check-update' for RHEL/CentOS)
  3. 3. Install the fixed FreeRDP version. On Debian/Ubuntu: 'sudo apt-get install freerdp2-x11' or 'sudo apt-get install xfreerdp' depending on the package name. On RHEL/CentOS: 'sudo yum update freerdp'
  4. 4. Alternatively, compile from source: Clone the FreeRDP repository ('git clone https://github.com/FreeRDP/FreeRDP.git'), checkout version 3.28.0 or later ('git checkout 3.28.0'), and follow the build instructions in the README
  5. 5. Verify the fix by running 'xfreerdp --version' to confirm version 3.28.0 or newer is installed
  6. 6. Test that existing .rdp connection files still work correctly with the updated client
Caveat Major version upgrades in FreeRDP may introduce minor behavioral changes or deprecate older RDP features; test critical workflows after upgrading

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-64621 — 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-64621 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