# CVE-2026-30785: RustDesk Encrypts Local Passwords with World-Readable Machine ID and Fixed Zero Nonce (XSalsa20-Poly1305)

> Attackers can decrypt local passwords using a world-readable machine ID and fixed nonce, exposing sensitive credentials in RustDesk Client.

- **Severity:** High 8.2 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Mar 2026
- **Updated:** 6 Mar 2026
- **Also known as:** GHSA-v738-924g-mm67

## What is CVE-2026-30785?

CVE-2026-30785 is a high-severity vulnerability in rustdesk-client RustDesk Client, published on 5 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-916 (Use of Password Hash With Insufficient Computational Effort), CWE-323 (Reusing a Nonce, Key Pair in Encryption), CWE-257 (Storing Passwords in a Recoverable Format), CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2026-30785?

It affects 1 product.


Products: Rustdesk Rustdesk.

## How do I fix CVE-2026-30785?

No fix has been published for CVE-2026-30785 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-30785 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30785 exists.

## Other vulnerabilities in rustdesk-client RustDesk Client

- [CVE-2024-25140](https://insights.sbomify.com/CVE-2024-25140/): Misconfiguration in n/a (critical 9.8)
- [CVE-2026-30793](https://insights.sbomify.com/CVE-2026-30793/): RustDesk Flutter URI Handler Sets Permanent Password Without Privilege Check or User Confirmation (critical 9.3)
- [CVE-2026-30797](https://insights.sbomify.com/CVE-2026-30797/): RustDesk rustdesk://config/ URI Silently Re-homes Client to Attacker-Controlled Server (critical 9.3)
- [CVE-2026-30791](https://insights.sbomify.com/CVE-2026-30791/): RustDesk Client Accepts Pseudo-Encrypted Config Strings Without Cryptographic Validation (high 8.7)
- [CVE-2026-30795](https://insights.sbomify.com/CVE-2026-30795/): RustDesk HTTP Client Silently Accepts Invalid TLS Certificates After Handshake Failure (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-30785 and fix it if it is affected.

What it is: CVE-2026-30785 is a high-severity vulnerability in rustdesk-client RustDesk Client, published on 5 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30785 exists.

Affected product: rustdesk-client RustDesk Client. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-30785/ (Markdown: https://insights.sbomify.com/CVE-2026-30785/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-30785
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-30785
- OSV: https://osv.dev/vulnerability/CVE-2026-30785

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-30785/
Summaries are generated and may contain mistakes; the official description above is the record.