IntegSec - Next Level Cybersecurity

CVE-2026-76840: RustDesk Clipboard Redirection Bug - What It Means for Your Business and How to Respond

Written by Mike Chamberland | 11/18/26, 5:00 PM

CVE-2026-76840: RustDesk Clipboard Redirection Bug - What It Means for Your Business and How to Respond

Introduction

CVE-2026-76840 is a critical vulnerability in RustDesk, a widely used remote-access application. It affects Windows systems where clipboard file sharing is enabled and can be triggered when a user pastes file contents offered by a remote peer. Organizations that rely on RustDesk for IT support, vendor access, or remote work should treat this as a priority because a malicious or compromised remote endpoint could potentially crash or compromise the application receiving the paste.

The risk is especially relevant to businesses in the United States and Canada that use remote-support tools to connect employees, managed service providers, contractors, and customers. This post explains what the vulnerability means operationally, which environments are exposed, and how to respond through patching, monitoring, and stronger remote-access controls. Technical detection and remediation details are provided in the appendix for security and IT teams.

Background & History

CVE-2026-76840 was published on August 24, 2026, and concerns RustDesk versions through 1.4.9 on Windows. The issue was documented by VulnCheck, which also provided the vulnerability assessment referenced by the National Vulnerability Database.

The underlying weakness is an out-of-bounds write: RustDesk accepts a length value supplied by the remote peer and uses it when copying clipboard file data into a local memory buffer. If that value is larger than the space available, data can be written beyond the buffer. In practical terms, a malicious remote peer can send an oversized response while a local user pastes remote clipboard file contents, potentially corrupting memory in the process handling the paste.

The vulnerability carries a CVSS 3.1 base score of 9.6, classified as Critical, and a CVSS 4.0 base score of 8.5, classified as High. The related defect was also present in FreeRDP code from which RustDesk’s Windows clipboard implementation was forked; FreeRDP addressed the equivalent issue in version 3.30.0.

What This Means for Your Business

If your organization uses RustDesk on Windows, this vulnerability creates a direct path from a remote peer to a local paste operation. An attacker does not need credentials on the local machine, but the user must perform an action: pasting clipboard file contents offered by the remote side. That user-interaction requirement lowers the likelihood of silent, large-scale exploitation, but it does not eliminate the risk. Support technicians, help-desk staff, and employees who regularly accept files or clipboard content from remote users face the greatest exposure.

The most immediate operational impact is availability. A successful attack may crash the process receiving the paste, such as Windows Explorer, interrupting work and requiring a restart. More seriously, memory corruption can potentially lead to code execution with the privileges of that process, which could give an attacker a foothold on an endpoint.feedly+1

From a data-protection perspective, an endpoint compromise can expose customer records, financial data, intellectual property, credentials, and internal communications. For organizations subject to obligations such as state breach-notification laws, HIPAA, PCI DSS, or Canadian privacy legislation, an incident involving a remote-access tool can also create notification, investigation, and audit burdens. Reputationally, customers and partners may question whether remote support connections are adequately governed.

The business response should be straightforward: identify every RustDesk installation, upgrade affected versions, restrict clipboard file transfer where it is not needed, and ensure remote-access sessions are limited to trusted and authenticated peers.

Real-World Examples

Regional financial-services firm: A regional bank uses RustDesk for internal IT support across branch offices. A compromised contractor device connects to a support workstation, and an employee pastes a file offered through the shared clipboard. Memory corruption crashes Explorer and potentially enables code execution on a device with access to internal banking systems, creating operational disruption and increasing incident-response costs.

Mid-sized healthcare provider: A clinic’s managed IT provider uses RustDesk to assist clinical staff. If a support session is hijacked or the remote peer is malicious, a clinician pasting a remotely offered file could expose a workstation that handles patient scheduling or electronic health-record access. Beyond downtime, the organization may need to assess whether protected health information was accessible and whether notification obligations apply.

Small professional-services business: A five-person accounting firm allows a remote bookkeeping contractor to connect through RustDesk. The contractor’s laptop is infected with malware. When an employee pastes a file shared by that contractor, the attacker may gain a foothold on the firm’s Windows workstation, potentially reaching client tax documents, banking credentials, or email.feedly+1

Large technology company: A global software company permits RustDesk for engineering lab access. Security teams discover outdated clients during an asset inventory. Even without evidence of exploitation, the company must prioritize remediation because a successful endpoint compromise could expose source code, build systems, or customer-support data, affecting intellectual property and customer trust.

Am I Affected?

  • You are affected if you run RustDesk on Windows in version 1.4.9 or earlier; the published affected range is 0 through 1.4.9.
  • You are at higher risk if Windows clipboard file redirection or clipboard file transfer is enabled during RustDesk sessions.
  • You are exposed if users paste file contents offered by a remote RustDesk peer, especially in IT support, vendor-access, or customer-support workflows.
  • You are at elevated risk if remote peers include third parties, contractors, customers, or devices outside your direct management.feedly
  • You are less exposed if RustDesk is not installed, is used only on non-Windows systems, or clipboard file transfer is disabled and users are trained not to paste remote clipboard content.
  • You should verify the installed version directly rather than relying on procurement records, because remote-access tools are often deployed outside standard software inventories.

Key Takeaways

  • CVE-2026-76840 affects RustDesk through version 1.4.9 on Windows and involves an out-of-bounds write in clipboard file redirection.
  • A malicious or compromised remote peer can trigger the flaw when a local user pastes clipboard file contents, potentially causing a crash or code execution.
  • The highest-risk users are IT support teams, managed service providers, contractors, and employees who accept files through remote-access sessions.feedly
  • The vulnerability is rated Critical at CVSS 3.1 9.6 and High at CVSS 4.0 8.5, making timely remediation important even though user interaction is required.
  • Businesses should inventory RustDesk installations, update to a patched release, restrict clipboard file transfer, and monitor remote-access activity.

Call to Action

If RustDesk is part of your remote-support environment, do not wait for an incident to confirm your exposure. IntegSec can help you identify vulnerable remote-access deployments, validate remediation, test exploitation paths safely, and strengthen the controls around third-party and privileged remote access. Visit https://integsec.com to schedule a penetration test and a practical cybersecurity risk assessment.

Technical Appendix

A — Technical Analysis

CVE-2026-76840 is an out-of-bounds write, classified as CWE-787, with an additional CWE-20 improper-input-validation classification. The vulnerable component is RustDesk’s Windows clipboard redirection implementation, specifically CliprdrStream_Read in libs/clipboard/src/windows/wf_cliprdr.c.

When an OLE paste consumer, such as explorer.exe, calls IStream::Read with a buffer of cb bytes, RustDesk requests that quantity of remote file data through cliprdr_send_request_filecontents. The peer-supplied CLIPRDR FileContentsResponse value cbRequested is assigned to req_fdata handling and ultimately used as the copy length in CopyMemory(pv, clipboard->req_fdata, clipboard->req_fsize). The code does not clamp req_fsize to the caller-provided cb value before copying. Its only comparison, req_fsize < cb, addresses a short read but occurs after the copy, so an oversized response writes beyond the destination heap buffer.

The attack vector is adjacent network access through an established RustDesk peer connection. Attack complexity is low, privileges are not required, and user interaction is required because the local user must paste clipboard file contents offered by the remote side. VulnCheck’s CVSS 4.0 vector is CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:L/SI:H/SA:H, while the CVSS 3.1 vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:H. The NVD reference is https://nvd.nist.gov/vuln/detail/CVE-2026-76840.

B — Detection & Verification

Version enumeration commands:

Scanner signatures: Configure vulnerability scanners to flag RustDesk installations at version 1.4.9 or lower and correlate the finding with CVE-2026-76840. Because the flaw is in Windows clipboard redirection, scanner coverage should include both user-installed and portable copies of the client.

Log indicators: Review RustDesk connection logs for unexpected peer IDs, unfamiliar devices, sessions originating outside approved geographies or networks, and sessions involving clipboard or file-transfer activity. Retain and correlate these logs with endpoint telemetry.

Behavioral anomalies: Monitor for explorer.exe or other OLE paste consumers crashing shortly after a RustDesk session, abnormal child-process creation from paste-related processes, heap-corruption alerts, and unexpected outbound connections following a file paste.

Network exploitation indicators: Look for RustDesk sessions followed by unusually large or malformed clipboard file-contents responses. A peer returning data substantially larger than the requested cb size during a file-contents operation is consistent with the vulnerability condition.

C — Mitigation & Remediation

  1. Immediate (0–24h): Inventory all Windows endpoints for RustDesk and identify versions 1.4.9 or earlier. Disable clipboard file redirection and file transfer for high-risk sessions, restrict RustDesk access to approved support personnel and managed devices, and instruct users not to paste remote clipboard file contents until systems are updated.
  2. Short-term (1–7d): Apply the official vendor fix by upgrading RustDesk to a release that includes the remediation; the project’s current release line includes version 1.5.0, and organizations should deploy the latest vendor-supported build after validation. If immediate upgrading is not possible, use application allowlisting, network segmentation, conditional access, and session recording to limit exposure. Remove RustDesk from systems that do not require remote support.github
  3. Long-term (ongoing): Incorporate remote-access tools into vulnerability management, software inventory, and patch SLAs. Enforce least privilege for support accounts, require multifactor authentication for remote sessions, restrict clipboard and file-transfer features by default, and periodically review peer-access relationships. Test the updated configuration through controlled penetration testing and validate that endpoint detection controls alert on suspicious paste-related or process-injection behavior.

For environments that cannot patch immediately, the strongest interim control is to prevent the required user action: block or disable clipboard file sharing and prohibit pasting remote clipboard file contents. Combine this with network restrictions around RustDesk relay and rendezvous services, and treat any unmanaged peer connection as untrusted.

D — Best Practices

  • Validate all peer-supplied lengths against the destination buffer size before copying data, especially in protocol parsers and clipboard handlers.
  • Apply secure coding checks that identify unchecked CopyMemory, memcpy, and similar operations where attacker-controlled sizes determine copy length.
  • Disable clipboard file redirection unless a documented business need exists, and enable it only for specific approved users or sessions.
  • Maintain an accurate inventory of remote-access software, including portable installations and third-party support tools.
  • Monitor remote sessions for unexpected peers, file-transfer activity, process crashes, and post-connection execution anomalies