CVE-2026-30783
Rustdesk ≤ 1.4.5
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2026-30783 is a high-severity Client-Side Enforcement of Server-Side Security (CWE-602) vulnerability in Rustdesk Rustdesk. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 31th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-25 (Reference Monitor) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-30783 is a Privilege Abuse vulnerability in the RustDesk Client (rustdesk-client), affecting the software on Windows, macOS, Linux, iOS, Android, and WebClient platforms. The issue resides in the client signaling, API sync loop, and config management modules, specifically associated with source files src/rendezvous_mediator.rs, src/hbbs_http/sync.rs, and program routines handling the API sync loop and api-server config. It impacts RustDesk Client versions through 1.4.5 and carries a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), linked to CWE-602 (Client-Side Enforcement of Server-Side Security) and CWE-841 (Improper Enforcement of Behavioral Workflow).
The vulnerability enables exploitation by unauthenticated attackers over the network with low attack complexity and no user interaction required. Successful exploitation allows high-impact disruption to confidentiality, integrity, and availability, potentially leading to full system compromise via privilege abuse on affected clients.
Advisories and documentation on mitigations, including patches, are detailed in the following references: https://docs.google.com/document/d/e/2PACX-1vSds6jjpd38oO_yIAyd1HYtKNUuea-I-ozAPpGhYI7QgAU-QGJ7D8a4rOZVj1vmiUXV1EcdRHf9aZAW/pub, https://rustdesk.com/docs/en/client/, and https://www.vulsec.org/.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-9831
Vulnerability Data
A vulnerability in rustdesk-client RustDesk Client rustdesk-client on Windows, MacOS, Linux, iOS, Android, WebClient (Client signaling, API sync loop, config management modules) allows Privilege Abuse. This vulnerability is associated with program files src/rendezvous_mediator.Rs, src/hbbs_http/sync.Rs and program routines API sync loop,…
more
api-server config handling. This issue affects RustDesk Client: through 1.4.5.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V10.7.1V2.2.2V8.3.1V10.4.1
Mitigating Controls (NIST 800-53 r5) AI
Requires a tamper-proof, always-invoked reference monitor that cannot be bypassed by client-side logic.
Enforces all access decisions on the server according to policy rather than trusting client-supplied enforcement.
Enforces information-flow rules at the server boundary instead of delegating them to the client.
Re-authentication requirements can be placed at critical workflow steps to ensure the actor has performed prior behaviors.
Monitors and controls all external and key internal interfaces so that server-side policy cannot be off-loaded to clients.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent design flaws that place server security enforcement on the client.
Proper policy-based enforcement of authorizations implies server-side controls rather than client-only checks.
Hardened configuration baselines can embed required workflow ordering rules.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure architecture principles discourage client-side trust but do not directly address this weakness.
Security testing can detect client-side enforcement but is not the primary mitigation.
Information access restriction is undermined when the client is trusted to enforce it.
Secure development lifecycle mandates server-side validation and prevents reliance on client enforcement.
Application security requirements explicitly call for server-side enforcement of security mechanisms.
Secure coding standards require server-side checks and reject client-only enforcement.