rustdesk-client RustDesk Client up to 1.4.5 rendezvous_mediator.Rs client-side enforcement of server-side security
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in rustdesk-client RustDesk Client up to 1.4.5. It has been rated as critical. This vulnerability affects unknown code of the file src/rendezvous_mediator.Rs. Performing a manipulation results in client-side enforcement of server-side security. This vulnerability is cataloged as CVE-2026-30783. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability classified as critical has been found in rustdesk-client RustDesk Client up to 1.4.5. This affects an unknown function of the file src/rendezvous_mediator.Rs. The manipulation with an unknown input leads to a client-side enforcement of server-side security vulnerability. CWE is classifying the issue as CWE-602. The product is composed of a server that relies on the client to implement a mechanism that is intended to protect the server. This is going to have an impact on integrity, and availability. The summary by CVE is:
A 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.5.
The weakness was shared by Erez Kalman. This vulnerability is uniquely identified as CVE-2026-30783 since 03/05/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/26/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 8.1VulDB Meta Temp Score: 8.1
VulDB Base Score: 6.5
VulDB Temp Score: 6.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Client-side enforcement of server-side securityCWE: CWE-602
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
03/05/2026 Advisory disclosed03/05/2026 CVE reserved
03/05/2026 VulDB entry created
03/26/2026 VulDB entry last update
Sources
Researcher: Erez KalmanStatus: Not defined
CVE: CVE-2026-30783 (🔒)
GCVE (CVE): GCVE-0-2026-30783
GCVE (VulDB): GCVE-100-349209
Entry
Created: 03/05/2026 17:53Updated: 03/26/2026 04:18
Changes: 03/05/2026 17:53 (64), 03/26/2026 04:18 (12)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.