Security readout for executives and security teams
Plain-English summary
RustDesk Client through 1.4.8 may accept an unauthenticated instruction that stops its service. For a business, the main risk is loss of remote-support availability across endpoints, not disclosed data theft. The source bundle does not identify a confirmed fixed version or active exploitation.
Executive priority
Treat this as a high-priority availability risk for remote-support operations. It should be addressed promptly where RustDesk is used at scale or on critical systems, while avoiding claims of active exploitation unless new evidence appears.
Technical view
The CVE describes insufficient data-authenticity verification and exceptional-condition handling in RustDesk Client heartbeat strategy processing. A crafted strategy payload can reach a stop-service handler without authentication, causing high availability impact. CVSS v4.0 is 8.2, network attack vector, no privileges or user interaction required, with attack requirements present.
Likely exposure
Organizations running RustDesk Client through 1.4.8 on Windows, macOS, Linux, iOS, or Android are potentially exposed, especially where clients process heartbeat or strategy synchronization data.
Exploitation context
The CVE is not listed as KEV in the supplied bundle. One third-party reference is tagged exploit, but the prompt does not provide evidence of active exploitation, public weaponization details, or observed attacks.
Researcher notes
Key unknowns are the exact trust boundary for strategy payload delivery, whether self-hosted versus public infrastructure changes exposure, and the fixed version. The supplied data supports availability impact, not confidentiality or integrity impact.
Mitigation direction
- Inventory RustDesk Client deployments and versions across endpoints.
- Check RustDesk guidance and release notes for a confirmed fixed version.
- Prioritize remediation or removal for clients through 1.4.8.
- Limit RustDesk use on high-value systems until remediation is confirmed.
- Restrict administrative control of RustDesk strategy or configuration channels.
Validation and detection
- Confirm whether any endpoint runs RustDesk Client through 1.4.8.
- Review RustDesk client configuration for heartbeat and strategy synchronization use.
- Check endpoint telemetry for unexpected RustDesk service stops.
- Track vendor and CVE records for remediation status changes.
- Validate compensating controls on systems requiring RustDesk continuity.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-345: 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 lookupCWE-755: 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 lookupCVE-2026-30798 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.2 (4.0)
- Known Exploited
- No
- Published
Vector: 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
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
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——VULSecVulnerability scoring details
Base CVSS 4.0 score
8.2HighVector: 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
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://rustdesk.com/docs/en/client/CVE reference, VULSec · technical-description, x_--config documentation
- https://docs.google.com/document/d/e/2PACX-1vSds6jjpd38oO_yIAyd1HYtKNUuea-I-ozAPpGhYI7QgAU-QGJ7D8a4rOZVj1vmiUXV1EcdRHf9aZAW/pubCVE reference, VULSec · third-party-advisory, exploit
- https://www.vulsec.org/CVE reference, VULSec · vdb-entry, third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insufficient Verification of Data Authenticity
Insufficient Verification of Data Authenticity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Handling of Exceptional Conditions
Improper Handling of Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.