HIGH 7.6

CVE-2026-58056: RustDesk Authorization Bypass via Uncleared Capability Flags

RustDesk contains an authorization bypass vulnerability where a user granted only file-transfer permissions can exploit insufficient access controls to perform unauthorized actions including keyboard input, mouse control, and screen capture. The vulnerability exists because the application checks individual feature permissions rather than validating that the requester's session type authorizes the requested action. When a file-transfer session is established, the application fails to clear capability flags, leaving them accessible for abuse by an attacker with limited legitimate access.

Source data · NVD / CISA · public domain

CVSS
3.1 · 7.6 HIGH · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L
Weaknesses (CWE)
CWE-863
Affected products
0 configuration(s)
Published / Modified
2026-06-28 / 2026-07-18

NVD description (verbatim)

RustDesk gates incoming control messages on per-capability flags rather than on the session's authorized connection type, and a file-transfer session does not clear those flags. A peer holding only a valid FileTransfer authorization can inject keyboard and mouse input and reach the unguarded screenshot and display-capture handlers, acting outside its granted scope.

2 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-58056 is an authorization bypass flaw in RustDesk stemming from improper separation of concerns between session-level authorization and per-capability permission checks. The vulnerability is rooted in CWE-863 (Incorrect Authorization). The application gates incoming control messages against individual capability flags without first validating the connection type under which those capabilities should be permitted. Specifically, a peer holding a valid FileTransfer authorization can craft or inject control messages to exercise keyboard input, mouse movement, screenshot capture, and display-capture functions. The root cause is the failure to clear or reset capability flags when transitioning into a file-transfer-only session, allowing persistence of capabilities beyond the intended scope.

Business impact

An authenticated insider or compromised account with only file-transfer privileges can silently monitor user activity, inject keystrokes for credential harvesting or malicious commands, and exfiltrate screen content without the victim's awareness. In multi-user or shared-device environments, this enables lateral movement and espionage. The damage is heightened because file-transfer access is often granted more liberally than full remote-control access, expanding the attack surface. Organizations relying on RustDesk for secure remote support or file synchronization may face undetected compromise of sensitive systems.

Affected systems

RustDesk is affected by this authorization bypass. The vendor and product list in the source record is empty; confirm the affected versions against the RustDesk security advisory, as the scope of affected releases is not specified in the provided data.

Exploitability

The vulnerability requires network access and valid authentication (CWE-863 vector: PR:L), meaning an attacker must possess a legitimate RustDesk account with at least file-transfer permissions. No user interaction is required to trigger the attack (UI:N). The CVSS 3.1 score of 7.6 (HIGH) reflects the combination of low access complexity (AC:L) and significant impact: low confidentiality loss (screen capture), high integrity risk (keyboard/mouse injection), and low availability impact. Exploitation is straightforward once authorized, as the attacker simply sends control messages that the application fails to properly gate.

Remediation

Apply a patched version of RustDesk that properly validates session authorization type before permitting capability-gated actions, and ensures capability flags are reset or scoped to the current session's authorized connection type. Verify the specific patch version against the official RustDesk advisory. Until patching is possible, restrict file-transfer-only permissions to trusted users, monitor for anomalous keyboard/mouse/screenshot activity on sessions labeled as file-transfer-only, and use network segmentation to limit RustDesk access to sensitive systems.

Patch guidance

Consult the RustDesk project's official security advisory for the specific patched version that resolves the capability-flag isolation issue. Apply the patch to all RustDesk instances, particularly those in production environments handling sensitive data or connected to critical systems. Verify the patch in a test environment before full rollout. Track the patch release date and ensure deployment across all managed endpoints within a defined maintenance window.

Detection guidance

Monitor RustDesk logs and network telemetry for file-transfer sessions that subsequently perform keyboard input, mouse movement, screenshot, or display-capture operations. Implement alerts on unexpected capability usage from sessions authorized only for file transfer. Use endpoint detection and response (EDR) tools to flag suspicious input injection or screen-capture activity correlated with RustDesk process execution. Review RustDesk session logs for authorization mismatches between the declared session type and the capabilities exercised.

Why prioritize this

This vulnerability merits immediate attention because it enables silent persistence and espionage by compromised or malicious insiders with low privilege levels. The combination of wide applicability (any RustDesk deployment), ease of exploitation (no special tools, only network access and valid credentials), and high business impact (undetected screen monitoring and keystroke injection) make it a preferred vector for attackers seeking to escalate or maintain access in multi-user environments. The HIGH CVSS score and the real-world likelihood of file-transfer-only accounts being issued to contractors or low-trust users elevate risk.

Risk score, explained

The CVSS 3.1 score of 7.6 (HIGH) is driven by: (1) network-accessible attack vector (AV:N); (2) low barriers to exploitation once authenticated (AC:L, PR:L, UI:N); (3) no requirement for user interaction; (4) significant integrity impact from keyboard and mouse injection (I:H) enabling command execution or credential theft; (5) confidentiality loss from unguarded screenshot and display-capture handlers (C:L); and (6) minor availability risk from potential DoS via injected input (A:L). The score does not account for the gating of exploitability to authenticated users, which limits but does not eliminate risk in shared or compromised-credential scenarios.

Frequently asked questions

Can this vulnerability be exploited without authentication?

No. The attacker must hold a valid RustDesk account with at least file-transfer permissions. However, in organizations with loose credential hygiene or shared accounts, this is a realistic constraint rather than a true barrier.

What capabilities can an attacker abuse beyond file transfer?

An attacker can inject keyboard and mouse input, capture screenshots, and invoke display-capture handlers. These actions enable credential harvesting, command injection, and espionage without the victim's knowledge or consent.

Why does clearing capability flags matter if the attacker already has file-transfer access?

Session-level authorization should enforce that file-transfer sessions are restricted to file operations. By failing to clear or reset capability flags, RustDesk leaves latent capabilities in memory that the attacker can invoke. Proper design would scope each capability to the session type and disable others entirely.

Is this vulnerability in the Known Exploited Vulnerabilities (KEV) catalog?

No. As of the provided data, this vulnerability has not been added to the CISA KEV catalog, meaning there is no confirmed evidence of active exploitation in the wild. However, the low barrier to exploitation means security teams should not delay patching based on KEV status alone.

This analysis is based on the CVE record and publicly available information as of the publication date. The vendor product list in the source data is incomplete; consult the official RustDesk security advisory for confirmed affected versions and patch availability. This document does not constitute formal vulnerability assessment or legal advice. Organizations must verify patch applicability and test in their own environments before deployment. SEC.co makes no warranty regarding the accuracy or completeness of this summary and recommends independent verification of all remediation steps with vendor guidance. Source: NVD (public-domain), retrieved 2026-08-06. Analysis generated by SEC.co (claude-haiku-4-5).