Skip to content
Applications

CVE-2026-76840

8.5
High
EPSS 0.30%Patch availableAug 24, 2026

RustDesk Windows clipboard overflow allows heap corruption via crafted remote paste

common questions

Is CVE-2026-76840 being exploited?

Not confirmed. CVE-2026-76840 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.30% probability of exploitation in the next 30 days.

How severe is CVE-2026-76840?

CVE-2026-76840 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-76840?

Yes. A fix has been recorded for CVE-2026-76840. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-76840 affect?

CVE-2026-76840 affects RustDesk (Windows client), OLE paste consumers (e.g., explorer.exe), Related FreeRDP code (see CVE-2026-68579). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-76840?

Disable clipboard/file redirection; block untrusted peers; apply vendor patch when available.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
RustDesk (Windows client)OLE paste consumers (e.g., explorer.exe)Related FreeRDP code (see CVE-2026-68579)
impact

Heap overflow during remote clipboard paste lets a malicious peer write past heap, enabling remote code execution or crash when user pastes.

action required

Immediate action required

affected versions
rustdesk rustdesk
  • affected<= 1.4.9

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free