CVE-2026-30785: RustDesk Client · CWE-257
Affects RustDesk ClientSource CVE Database V5
Not known to be exploited · CVSS 8.2 High.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.08% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/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 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| rustdesk-clientRustDesk Client | Affected
| Fixed in– |
GitHubrustdesk, hbb_commonpkg:github/rustdesk, hbb_commonOther 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
Until an official patch is released, organizations should implement strict local access controls to limit who can execute or interact with RustDesk Client binaries. Employ application whitelisting and endpoint detection to monitor for suspicious activity involving the affected modules. Use strong OS-level user privilege separation and avoid running RustDesk Client with elevated privileges unnecessarily. Regularly audit and rotate any secrets or credentials managed by RustDesk Client to reduce exposure duration. Consider isolating RustDesk Client usage to dedicated, hardened endpoints with limited network access. Monitor logs for unusual access patterns or attempts to exploit prototype pollution or cryptographic weaknesses. Once patches become available, apply them promptly. Additionally, developers and security teams should review the password hashing algorithms and prototype handling logic in the affected source files to ensure they meet current cryptographic and secure coding standards, such as using memory-hard password hashing functions (e.g., Argon2) and safe prototype handling practices.
Description
Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution'), Use of Password Hash With Insufficient Computational Effort vulnerability in rustdesk-client RustDesk Client rustdesk, hbb_common on Windows, MacOS, Linux (Password security module, config encryption, machine UID modules) allows Retrieve Embedded Sensitive Data. This vulnerability is associated with program files hbb_common/src/password_security.Rs, hbb_common/src/config.Rs, hbb_common/src/lib.Rs (get_uuid), machine-uid/src/lib.Rs and program routines symmetric_crypt(), encrypt_str_or_original(), decrypt_str_or_original(), get_uuid(), get_machine_id(). This issue affects RustDesk Client: through 1.4.5.
References
- github.com/rustdesk/rustdesk/discussions/9229 (opens in a new tab)
- github.com/rustdesk/rustdesk/discussions/4979 (opens in a new tab)
- docs.google.com/document/d/e/2PACX-1vSds6jjpd38oO_yIAyd1HYtKNUuea-I-ozAPpGhYI7QgAU-QGJ7D8a4rOZVj1vmiUXV1EcdRHf9aZAW/pub (opens in a new tab)
- vulsec.org (opens in a new tab)