Threat Intelligence Database
Comprehensive database of the latest cyber threats affecting organizations worldwide. Filter and search to find specific threat intelligence relevant to your organization.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threat Intelligence
Click on any threat for detailed analysis and mitigation recommendations
RustDesk versions prior to 1.5.0 contain a vulnerability in the Cliprdr message handler on Linux and macOS where file transfer permissions are not properly validated for incoming file clipboard messages. This allows authenticated remote peers, even if file transfer permissions are disabled, to place files onto the host clipboard and retrieve copied files and clipboard contents from the process-wide clipboard cache. Join the discussion | GCVE Database | 09/25/2026, 21:33:04 UTC Added: 09/26/2026, 04:51:48 UTC |
RustDesk's Windows clipboard redirection contains a vulnerability where a peer-supplied length is copied into a fixed-size buffer without an upper bound check. This can lead to a heap buffer overflow when pasting clipboard file contents from a malicious or compromised remote peer. The flaw originates from improper handling of the requested file contents size, allowing attacker-controlled data to overwrite memory beyond the intended buffer. Join the discussion | GCVE Database | 08/24/2026, 15:31:51 UTC Added: 08/24/2026, 16:40:44 UTC |
0 A default installation of RustDesk 1.2.3 on Windows places a WDKTestCert certificate under Trusted Root Certification Authorities with Enhanced Key Usage of Code Signing (1.3.6.1.5.5.7.3.3), valid from 2023 until 2033. This is potentially unwanted, e.g., because there is no public documentation of security measures for the private key, and arbitrary software could be signed if the private key were to be compromised. NOTE: the vendor's position is "we do not have EV cert, so we use test cert as a workaround." Insertion into Trusted Root Certification Authorities was the originally intended behavior, and the UI ensured that the certificate installation step (checked by default) was visible to the user before proceeding with the product installation. Join the discussion | CVE Database V5 | 02/06/2024, 00:00:00 UTC Added: 02/25/2026, 21:45:04 UTC |
Showing 1 to 3 of 3 results