CVE-2026-100417 rustdesk CVE debrief

Who should care

Defenders responsible for managing and securing systems using RustDesk should assess exposure and prioritize verification and remediation efforts. This includes reviewing system configurations, ensuring that all instances of RustDesk are updated to version 1.5.0 or later, and monitoring for suspicious activity related to clipboard file requests. Additionally, defenders should consider implementing compensating controls for exposed systems while remediation

Why it matters

CVE-2026-100417 is a low-severity vulnerability allowing authenticated peers to read files from the host clipboard. Defenders should prioritize verification, upgrading, and monitoring to prevent potential data exposure.

• Verify and restrict clipboard access to prevent unauthorized file reading
• Upgrade to RustDesk version 1.5.0 or later to enforce one-way file transfer
• Monitor for suspicious activity related to clipboard file requests

Technical summary

The vulnerability exists in RustDesk before version 1.5.0 on Windows, where the application fails to enforce the one-way file transfer option against peer clipboard file requests. This allows authenticated peers to send FormatDataRequest and FileContentsRequest messages to retrieve copied files by guessing the FileGroupDescriptorW format identifier. Defenders should prioritize verifying and upgrading to RustDesk version 1.5.0 or later, and restrict access to sensitive clipboard data to prevent potential data exposure.

Defensive priority

Defenders should prioritize verifying and upgrading to RustDesk version 1.5.0 or later, and restrict access to sensitive clipboard data.

Recommended defensive actions

• Verify and upgrade to RustDesk version 1.5.0 or later
• Restrict access to sensitive clipboard data
• Monitor for suspicious activity related to clipboard file requests
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description and CVSS score. However, the exact scope of affected systems and potential impact require further verification.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.