This page tracks the Debian fix status. The vulnerability itself is described on the main CVE page. View CVE-2026-72746 →
This advisory has been withdrawn (2026-08-13).
Categories
DEBIAN-CVE-2026-72746

Vulnerability in freerdp3 (DEBIAN-CVE-2026-72746)

Summary

Vulnerability in freerdp3 (DEBIAN-CVE-2026-72746). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.30.0+dfsg-1 or later.

Original description

The description as published by the source.

FreeRDP before 3.30.0 contains a server-side authentication bypass in the RDSTLS handshake. When a server is configured with RdstlsSecurity = TRUE, the handshake dispatches inbound PDUs based solely on the attacker-supplied wire pduType without verifying that the received PDU is the one required at the current step. Because the rdpRdstls object is calloc-zeroed, its resultCode defaults to 0 (RDSTLS_RESULT_SUCCESS). An unauthenticated remote client can send a Capabilities PDU instead of the required Authentication Request PDU; rdstls_process_capabilities() returns success without ever setting resultCode, so the server responds with an AUTHRSP carrying resultCode SUCCESS and treats the session as authenticated without evaluating any password, redirection GUID, or auto-reconnect cookie. This affects the released FreeRDP 3.x series (e.g., 3.27.1) and master HEAD; at the time of the advisory no patched version was available.

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 DEBIAN-CVE-2026-72746 has been found in freerdp3.
Risk of unauthorized operations or information disclosure.
What to do: upgrade freerdp3 to 3.30.0+dfsg-1 or later.
If unsure, ask your IT team or search "freerdp3 DEBIAN-CVE-2026-72746" on the vendor's site.

DEBIAN-CVE-2026-72746 (freerdp3)
Patched: 3.30.0+dfsg-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 freerdp3.

📍 Affected scope

Check the vendor advisory for the affected versions of freerdp3.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.30.0+dfsg-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 'freerdp3' . 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. 1
    Identify exposure identify
    grep -r 'freerdp3' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で freerdp3 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade freerdp3 to 3.30.0+dfsg-1

    ステージング環境で 3.30.0+dfsg-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Debian:13 freerdp3
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Debian:14 freerdp3
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.30.0+dfsg-1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details