CVE-2026-30783
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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, api-server config handling. This issue affects RustDesk Client: through 1.4.8.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA privilege abuse vulnerability exists in RustDesk Client's client signaling, API sync loop, and config management modules. The flaw is present in the rendezvous_mediator.Rs and hbbs_http/sync.Rs components, where improper handling of API server configuration and synchronization allows attackers to exploit privilege boundaries. This affects all platforms (Windows, MacOS, Linux, iOS, Android, WebClient) through version 1.4.8.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.4.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check RustDesk Client versionOpen the RustDesk Client application, go to Settings or About section to view the installed version number. Alternatively, check the program's installation directory for version information.Affected if The installed version is 1.4.5 or lower (any version <= 1.4.5).
-
Verify API sync configurationInspect the RustDesk configuration files for API sync settings. Look for configuration entries related to API synchronization or server communication settings.Affected if API sync feature is enabled and the client is configured to sync with an API server (hbbs_http or custom API endpoint).
-
Check api-server configurationReview the RustDesk client configuration for any configured api-server, hbbs server, or relay server addresses. These are typically found in config files or connection settings.Affected if A custom or third-party api-server is configured in the client settings, as the vulnerability affects api-server config handling.
-
Inspect network connectivity to remote serversReview network connections or logs to identify which RustDesk relay or ID registration servers the client is connecting to.Affected if The client is connecting to untrusted or non-official RustDesk servers, as the vulnerability allows potential session hijacking through the rendezvous mediator component.
A user is affected if their RustDesk Client version is 1.4.5 or lower AND they have API sync or custom api-server configuration enabled, particularly when connecting to untrusted servers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade RustDesk Client to a version beyond 1.4.8 that contains the security patch for this privilege abuse vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30783 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-30783 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data