# CVE-2026-30798: RustDesk Client Accepts Unauthenticated stop-service Command via Strategy Payload

> An unauthenticated attacker can send a stop-service command via the heartbeat loop, causing a denial of service or bypassing security controls in RustDesk Client.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Mar 2026
- **Updated:** 22 Jun 2026
- **Also known as:** GHSA-w793-gh7r-h7mx

## What is CVE-2026-30798?

CVE-2026-30798 is a high-severity missing authorization vulnerability in rustdesk-client RustDesk Client, published on 5 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insufficient Verification of Data Authenticity, Improper Handling of Exceptional Conditions vulnerability in rustdesk-client RustDesk Client rustdesk-client on Windows, MacOS, Linux, iOS, Android (Heartbeat sync loop, strategy processing modules) allows Protocol Manipulation.

 This vulnerability is associated with program files src/hbbs_http/sync.Rs and program routines stop-service handler in heartbeat loop.

This issue affects RustDesk Client: through 1.4.8.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions), CWE-345 (Insufficient Verification of Data Authenticity)

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

It affects 1 product.


Products: Rustdesk Rustdesk.

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

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

## Is CVE-2026-30798 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30798 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-30798 and fix it if it is affected.

What it is: CVE-2026-30798 is a high-severity missing authorization vulnerability in rustdesk-client RustDesk Client, published on 5 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30798 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-30798/ (Markdown: https://insights.sbomify.com/CVE-2026-30798/index.md)
```

## Sources

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

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