dbcve.org
RustdeskApplication

CVE-2026-30793

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

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
Cross-Site Request Forgery (CSRF) vulnerability in rustdesk-client RustDesk Client rustdesk-client on Windows, MacOS, Linux, iOS, Android (Flutter URI scheme handler, FFI bridge modules) allows Privilege Escalation. This vulnerability is associated with program files flutter/lib/common.Dart, src/flutter_ffi.Rs and program routines URI handler for rustdesk://password/, bind.MainSetPermanentPassword(). This issue affects RustDesk Client: through 1.4.5.

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 · high confidence

A CSRF vulnerability in RustDesk Client's Flutter URI scheme handler (rustdesk://password/) enables unauthenticated attackers to invoke the MainSetPermanentPassword() function via the FFI bridge, allowing privilege escalation by setting or changing the user's password without proper session validation.

MitigationApply vendor-supplied patch when available; until then, restrict access to the application, disable URI handler registration if possible, and monitor for suspicious rustdesk:// URI invocations.

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
RustdeskApplication
Affected:<= 1.4.5

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 RustDesk client is installed
    On Windows, check Program Files or Add/Remove Programs for 'RustDesk'. On Linux, run 'which rustdesk' or check for rustdesk in package manager. On macOS, check /Applications for RustDesk.app.
    Affected if RustDesk is installed on the system
  2. Identify the installed RustDesk version
    Run 'rustdesk --version' from command line, or on Windows right-click rustdesk.exe and view Properties > Details for the version number. Check the About section within the RustDesk client interface.
    Affected if The installed version is 1.4.5 or lower (any version up to and including 1.4.5)
  3. Check if RustDesk server/relay services are running
    On Windows, open Services or Task Manager and look for 'rustdesk' processes. On Linux, run 'ps aux | grep rustdesk' to check for running rustdesk-s, rustdesk-relay, or rustdesk-p2p processes.
    Affected if RustDesk services are running and accessible on the network (these services accept the vulnerable URI handler connections)
  4. Verify URI scheme handler configuration
    Check if the rustdesk:// URI scheme is registered as a handler. On Windows, search registry for 'rustdesk' under HKCU\Software\Classes or HKLM\Software\Classes. Look for entries under .rustdesk or rustdesk:// protocol handler.
    Affected if The rustdesk:// URI scheme is registered and accessible to local or remote applications

The environment is affected if RustDesk version 1.4.5 or lower is installed and the rustdesk:// URI scheme handler is active and accessible.

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 a release after 1.4.5
Interim mitigation

Apply vendor-supplied patch when available; until then, restrict access to the application, disable URI handler registration if possible, and monitor for suspicious rustdesk:// URI invocations.

Recommended fix Moderate confidence

RustDesk Client version 1.4.6 or later

  1. 1. Identify the current installed version of RustDesk Client by checking the application or its installation directory
  2. 2. Navigate to the official RustDesk GitHub releases page or official download page
  3. 3. Download the latest stable release version newer than 1.4.5
  4. 4. Uninstall the current RustDesk Client version
  5. 5. Install the newly downloaded version
  6. 6. Verify the installation was successful and confirm the version number
Caveat Review release notes for any configuration or feature changes between 1.4.5 and the target upgrade version

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

Fix this in Rustdesk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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