Vulnerability in freerdp (UBUNTU-CVE-2026-64621)

Summary

Vulnerability in freerdp (UBUNTU-CVE-2026-64621). Data can be tampered with by attackers. Mitigation: upgrade to 3.30.0+dfsg-0ubuntu0.24.04.1 or later.

Original description

The description as published by the source.

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.

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as UBUNTU-CVE-2026-64621 has been found in freerdp.
Data can be tampered with by attackers.
What to do: upgrade freerdp to 3.30.0+dfsg-0ubuntu0.24.04.1 or later.
If unsure, ask your IT team or search "freerdp UBUNTU-CVE-2026-64621" on the vendor's site.

UBUNTU-CVE-2026-64621 (freerdp)
Attack vector: local / unauthenticated
Patched: 3.30.0+dfsg-0ubuntu0.24.04.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in freerdp.

📍 Affected scope

Check the vendor advisory for the affected versions of freerdp.

🔥 Severity

Severity: ?. Data can be tampered with by attackers.

🔧 How to fix

Update to 3.30.0+dfsg-0ubuntu0.24.04.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'freerdp' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'freerdp' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で freerdp を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade freerdp to 3.30.0+dfsg-0ubuntu0.24.04.1
```
ステージング環境で 3.30.0+dfsg-0ubuntu0.24.04.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。