External risk intelligence

RustDesk Client CSRF Vulnerability Allows Privilege Escalation.

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-30793

The vulnerability involves a client-side application (RustDesk Client) and specific local URI scheme handlers. Exploitation requires user interaction with a malicious link or local configuration triggers within the client application itself, rather than direct exposure of a public-facing network service or internet gateway.

Cross-site Request Forgery

Rustdesk

1.4.5 and earlier

Halo Surface Signal: 1 out of 5 — much less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A Cross-Site Request Forgery vulnerability exists in the RustDesk Client across multiple operating systems, which could potentially allow for privilege escalation. This issue is related to how the client handles specific URI schemes and FFI bridge modules.

  • Flaw allows unauthorized actions within the app.
  • High severity; impacts user trust and data integrity.
  • Confirm exposure; focus on user interaction and local triggers.

Attack Path

How an attacker could exploit the issue

An attacker could trick a user into clicking a malicious link, which then interacts with the RustDesk client's URI scheme handler. This interaction could potentially allow the attacker to escalate privileges on the user's system by manipulating specific program routines within the client.

  • Requires user interaction with a link.
  • Triggers via URI scheme handler.
  • Leads to privilege escalation risk.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an attacker to escalate privileges within the RustDesk client application. This may occur when a user interacts with a specially crafted URI link. When supported by the advisory, this could affect program files and potentially lead to unauthorized actions on the user's system.

  • Program files and data.
  • Via crafted URI or local triggers.
  • Unauthorized actions on the system.

Operational Fix

Recommended remediation, mitigation, and detection steps

The RustDesk client's URI scheme handler and FFI bridge modules are susceptible to privilege escalation via CSRF. Identifying all deployments of the RustDesk client, confirming their accessibility, and determining business criticality is the immediate first step. Subsequently, accountability for remediation needs to be established, followed by a risk-based remediation plan.

  • Own issue: Application or platform team.
  • Verify first: Client reachability and criticality.
  • Action: Plan remediation based on risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the RustDesk Client software?

RustDesk Client is a cross-platform remote desktop application used to access and manage computers remotely. It supports major operating systems, including Windows, macOS, Linux, iOS, and Android. The application utilizes a Flutter URI scheme handler and FFI bridge modules to facilitate communication between its interface and core system functions, which are the components involved in this vulnerability.

What does this CSRF vulnerability mean for CVE-2026-30793?

This vulnerability is a Cross-Site Request Forgery (CWE-352) paired with improper authorization (CWE-285). In simple terms, it means the application can be tricked into performing actions without the user's consent. Because the flaw exists within the URI handler and password setting routines, an unauthorized request could allow an attacker to escalate privileges or modify security settings within the client itself.

How is this vulnerability triggered?

The flaw is typically triggered when a user interacts with a specially crafted link—often delivered through a web browser—that invokes the application's URI scheme handler (e.g., rustdesk://). It does not trigger through normal, intended use of the application. The vulnerability requires a specific sequence of interaction with these URI handlers or bridge modules; simply having the application installed or running in the background does not inherently trigger the bug.

Why does Halo Surface Signal categorize this risk as unlikely?

Halo Surface Signal notes that this vulnerability involves client-side software rather than a public-facing network service. Because it requires a user to interact with a malicious link or a specific local trigger, it is not a direct attack against an internet gateway. Therefore, while the severity is high, the practical likelihood of exploitation depends heavily on user behavior and external triggers rather than automated network scanning.

What should I do if I use the RustDesk Client?

Your first step is to locate all systems within your environment where the RustDesk Client is installed to understand your footprint. Once identified, evaluate the criticality of those specific machines. Since the risk involves manipulated links, emphasize user awareness regarding clicking untrusted web links. Coordinate with your application or IT team to track updates or guidance provided by the software vendor for versions beyond 1.4.5.

References