LiveActive security incident?Get immediate response
CVE Record

CVE-2026-30789: RustDesk Auth Proof Uses Server-Controlled Salt/Challenge and Fast Double-SHA256, Enabling Offline Brute-Force

Use of Password Hash With Insufficient Computational Effort, Improper Restriction of Excessive Authentication Attempts vulnerability in rustdesk-client RustDesk Client rustdesk-client on Windows, MacOS, Linux, iOS, Android (Client login, peer authentication modules) allows Password Brute Forcing. The authentication proof is SHA256(SHA256(password + salt) + challenge), where both the salt and the challenge are generated entirely by the server with no client-side nonce, and the hash uses no slow key-derivation function. A rogue or on-path API/relay server (see CVE-2026-30794 / CVE-2026-30797) can issue a chosen salt and challenge, capture the resulting proof, and recover the password offline. The capture-replay claim (CWE-294) is withdrawn: the challenge is regenerated per connection (challenge = Config::get_auto_password(6)), so a captured proof is not replayable against the legitimate server. The 1.4.7 OTP brute-force limiter and the existing LOGIN_FAILURES counter constrain only ONLINE attempts and do not address offline recovery. This vulnerability is associated with program files src/client.rs and program routines handle_hash(), handle_login_from_ui() (login proof construction). This issue affects RustDesk Client: through 1.4.8.

MediumCVSS 5.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

RustDesk Client through 1.4.8 can expose user passwords to offline guessing if a client authenticates through a rogue or on-path API/relay server. The issue is not simple replay; it is weak password-proof design. No provided source confirms active exploitation or a named patch.

Executive priority

Treat as a moderate-priority credential exposure risk. Prioritize environments using RustDesk for administrative access, custom relay infrastructure, or shared passwords. Escalate if related server-positioning CVEs are present.

Technical view

The login proof uses SHA256(SHA256(password + server salt) + server challenge). Because salt and challenge are server-controlled and the hash is fast, a malicious or on-path server can capture a proof and attempt offline password recovery. CVE text says online rate limits do not address this.

Likely exposure

Exposure applies to RustDesk Client on Windows, macOS, Linux, iOS, and Android through 1.4.8, especially where clients use untrusted, compromised, or intercepted API/relay infrastructure.

Exploitation context

The source bundle marks KEV as false. It references a third-party advisory tagged exploit, but provides no confirmed active exploitation. Practical abuse requires a rogue or on-path server position and depends heavily on password strength.

Researcher notes

The capture-replay claim was withdrawn because challenges change per connection. The remaining issue is CWE-916: insufficient computational effort in a server-controlled challenge design. Evidence does not name a patch, so remediation should track vendor guidance.

Mitigation direction

  • Check RustDesk vendor guidance for fixed versions or official remediation.
  • Avoid untrusted or unexpected RustDesk API and relay servers.
  • Rotate RustDesk passwords after suspected rogue-server exposure.
  • Use strong, unique passwords to reduce offline guessing success.
  • Review related server-positioning risks in CVE-2026-30794 and CVE-2026-30797.

Validation and detection

  • Inventory RustDesk Client versions and identify deployments through 1.4.8.
  • Review client configuration for custom or unexpected server settings.
  • Confirm whether endpoints could have used untrusted relay/API infrastructure.
  • Check vendor advisories for patch status before closure.
  • Assess whether exposed passwords were reused elsewhere.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-916: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-30789 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.7 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.7CVSS 4.0MediumCVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N——VULSec

Vulnerability scoring details

Base CVSS 4.0 score

5.7Medium
CVSS 4.0 vector shape for CVE-2026-30789Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
rustdesk-clientRustDesk Clientrustdesk-client, 0affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-916 · source CWE mapping

Use of Password Hash With Insufficient Computational Effort

Use of Password Hash With Insufficient Computational Effort represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.