CVE-2025-62641 is an easily exploitable vulnerability in the Core component of Oracle VM VirtualBox affecting supported versions 7.1.12 and 7.2.2. The flaw requires a high-privileged attacker with logon access to the infrastructure where Oracle VM VirtualBox executes. Successful exploitation can compromise the VirtualBox instance and, because the vulnerability has scope change, may significantly impact additional products beyond the vulnerable component itself. Oracle rates the issue with CVSS 3.1 vector AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Python exploit script targeting CVE-2025-62641, a remote code execution vulnerability in Oracle VirtualBox's VRDP (VirtualBox Remote Desktop Protocol) clipboard synchronization feature. The script constructs a specially crafted VRDP packet with a malformed CLIPBOARD_SYNC message and embeds a Windows x64 Meterpreter reverse TCP shellcode. The exploit connects to the target VirtualBox host on port 3389 (VRDP), sends the malicious packet, and, if successful, causes the host to execute the shellcode, resulting in a reverse shell connection to the attacker's machine. The script is self-contained, with configuration variables for the target and attacker IPs and ports. The payload is hardcoded but can be regenerated for different attacker details. The exploit is operational and demonstrates a working attack path for remote code execution on a vulnerable VirtualBox host with VRDP enabled.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.