CVE-2026-30797: RustDesk Client · Missing Authorization
Affects RustDesk ClientSource CVE Database V5
Not known to be exploited · CVSS 9.3 Critical.
Data as of 30 Oct 2026, 11:52 UTC
Contested
Critical score, yet low EPSS after six months- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 5 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| rustdesk-clientRustDesk Client | Affected
| Fixed in– |
GitHubrustdesk-clientpkg:github/rustdesk-clientOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2026-30797, organizations should take the following specific actions: 1) Monitor RustDesk Client vendor communications closely and apply security patches immediately once released to address the missing authorization flaw. 2) Until patches are available, restrict network access to RustDesk Client endpoints by implementing strict firewall rules and network segmentation to limit exposure to untrusted networks. 3) Employ TLS interception detection and enforce strict certificate validation to reduce the risk of man-in-the-middle attacks that enable API message manipulation. 4) Educate users to avoid clicking on untrusted or unsolicited URI links that trigger configuration imports, and implement endpoint security controls to monitor and block suspicious URI scheme invocations. 5) Consider deploying endpoint detection and response (EDR) solutions capable of identifying anomalous behavior related to configuration changes or API message manipulation within RustDesk Client processes. 6) Review and harden configuration import workflows to ensure only authorized and validated configurations are accepted. 7) Where feasible, use network-level VPNs or zero-trust access models to secure remote desktop communications beyond the RustDesk client itself. These targeted mitigations go beyond generic advice by focusing on the specific attack vector and the unique aspects of the vulnerability.
Description
Missing Authorization vulnerability in rustdesk-client RustDesk Client rustdesk-client on Windows, MacOS, Linux, iOS, Android (Flutter URI scheme handler, config import modules) allows Application API Message Manipulation via Man-in-the-Middle. This vulnerability is associated with program files flutter/lib/common.Dart and program routines importConfig() via URI handler. This issue affects RustDesk Client: through 1.4.5.