Management evasion via orphaned API channel
Published Mar 5, 2026 · Updated Mar 5, 2026
Client-side policy enforcement in RustDesk Client 1.4.8 and earlier allows local users to evade central management by changing its API server. The client reads api-server from RustDesk2.toml, while independent signaling and relay remain active after the API sync loop stops receiving strategy and ACL updates. Local access to an unlocked, non-custom client configuration is required; peer authentication still gates sessions, and the flaw grants no device access.
Summary
What happened
Client-side policy enforcement in RustDesk Client 1.4.8 and earlier allows local users to evade central management by changing its API server. The client reads api-server from RustDesk2.toml, while independent signaling and relay remain active after the API sync loop stops receiving strategy and ACL updates. Local access to an unlocked, non-custom client configuration is required; peer authentication still gates sessions, and the flaw grants no device access.
The record
- CVE
- CVE-2026-30783
- Published
- Mar 5, 2026
- Updated
- Mar 5, 2026
- Vendor
- RustDesk
- Product
- RustDesk
- Classifications
- CWE-602, CWE-841, CAPEC-122, T1562.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 5, 2026CVE publishedPublication date reported by the CVE source.
- Mar 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.4.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- RustDesk API-channel orphaning proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo