External risk intelligence

RustDesk Client URI Scheme Handler Authorization Bypass.

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-30797

The vulnerability involves client-side URI scheme handling and configuration import modules within the RustDesk desktop and mobile client software. While the client facilitates remote access, this specific attack surface requires a man-in-the-middle context to manipulate application messages during configuration imports or URI handling, which is not a common or direct public-internet-facing service endpoint.

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

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been identified in the RustDesk client software, affecting its handling of application API messages through a Man-in-the-Middle attack. This issue could allow for manipulation of application messages when importing configurations or using the URI handler, impacting users across multiple operating systems. The primary concern at this time is to confirm if this specific software is in use within our environment.

  • Software allows message manipulation via attacks.
  • Leadership should know about remote access risks.
  • Confirm relevance and exposure to this software.

Attack Path

How an attacker could exploit the issue

An attacker could intercept network traffic to manipulate application messages when a user imports configuration settings or uses a URI to launch the RustDesk client. This allows them to potentially control application actions.

  • Requires man-in-the-middle access.
  • Triggered by URI handling or config import.
  • Enables application API message manipulation.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an attacker to manipulate application messages when importing configurations or through the URI handler. This may expose sensitive information or alter service behavior under specific man-in-the-middle conditions.

  • Sensitive application configuration data at risk.
  • Exposure via man-in-the-middle attack.
  • May lead to unauthorized message manipulation.

Operational Fix

Recommended remediation, mitigation, and detection steps

The primary responsibility for addressing this vulnerability lies with teams managing the RustDesk client deployments, likely Application Owners or IT Infrastructure teams responsible for endpoint management. The first practical step is to identify all systems running the affected RustDesk client versions, confirm their exposure and criticality, and then coordinate remediation efforts, possibly involving vendor communication for updates or patches.

  • Identify affected RustDesk client installations.
  • Verify exposure and business criticality of deployments.
  • Plan remediation with vendor engagement.

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 used for?

RustDesk is a cross-platform remote desktop application that allows users to access and control computers or mobile devices remotely. It is available on Windows, macOS, Linux, iOS, and Android. Users rely on it to provide technical support, manage remote infrastructure, or access their own machines from different locations.

What does this vulnerability mean for RustDesk users?

This flaw relates to missing authorization (CWE-862) and exposed dangerous method or function (CWE-749). In plain English, the software fails to verify who is sending commands to its configuration and URI handlers. An attacker can exploit this to send unauthorized messages, potentially tricking the application into changing settings or performing actions without the user's permission.

How is this CVE-2026-30797 vulnerability triggered?

The vulnerability is triggered when the application processes a configuration import or a URI scheme command. It requires an attacker to successfully position themselves as a man-in-the-middle to intercept and alter these messages. Simply using the software in normal conditions without an adversary actively intercepting network traffic does not trigger this issue.

Is this vulnerability a major risk if I use RustDesk?

According to Halo Surface Signal, this risk is currently classified as 'Unlikely.' While the software is used for remote access, this specific attack requires an adversary to be in a man-in-the-middle position to manipulate messages during specific configuration or URI-based actions. It is not an inherent vulnerability of a direct, always-on public-facing network service.

What are the first steps to take regarding this threat?

Start by identifying every system in your environment where the RustDesk client is installed, specifically looking for versions 1.4.5 and earlier. Once identified, evaluate how critical those deployments are to your operations. Coordinate with your IT or application management teams to monitor official vendor communications for updates and prepare for necessary software patching.

References