CVE-2026-30785
Crypto Weakness in Rustdesk ≤ 1.4.5
Raw vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/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-30785 is a high-severity Storing Passwords in a Recoverable Format (CWE-257) vulnerability in Rustdesk Rustdesk. Its CVSS base score is 8.2 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Group Policy Preferences (T1552.006); ranked at the 0.3th 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 IA-5 (Authenticator Management) and SA-11 (Developer Testing and Evaluation) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-9833
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.8.3V15.3.6V11.4.2V11.4.4
Mitigating Controls (NIST 800-53 r5) AI
IA-5 requires proper management of authenticators including storage of passwords only in non-recoverable (hashed) form, directly stopping the weakness from existing.
Developer testing and evaluation can discover nonce reuse through static analysis, fuzzing, or known-answer tests.
Cryptographic protection mandates selection and use of approved algorithms whose parameters can include sufficient work factors for password hashing.
Engineering principles include correct use of cryptographic primitives such as unique nonces per key.
Protection of information at rest requires cryptographic safeguards on stored password hashes, reducing exposure to offline cracking.
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.
Protecting data-at-rest with cryptographic hashes directly prevents recoverable password storage.
Secure SDLC practices directly prevent nonce/key reuse errors in cryptographic implementations.
Authentication policies may reference password handling but do not address storage or computational cost of hashes.
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.
Directly requires secure handling and protection of authentication information, preventing storage in recoverable formats.
Mandates secure authentication mechanisms that preclude recoverable password storage.
Mandates proper cryptographic key and nonce management, directly preventing nonce/key-pair reuse.
Security testing can detect nonce reuse, yet the control addresses many other issues beyond this CWE.
Secure SDLC includes requirements that reduce the likelihood of introducing recoverable password storage.
Application security requirements explicitly call for safeguards against unsafe object attribute manipulation.