CVE-2026-21985: Oracle Vm Virtualbox

What is CVE-2026-21985?

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle VM VirtualBox accessible data. CVSS 3.1 Base Score 6.0 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N).

CVSS6 NVD 3.1

SeverityMEDIUM

ExploitationNo exploitation reported

EPSS<1% · P15

Triage statusNo Known Exploit

ActionSchedule for next cycle

CVSS vectorCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N

NVD published2026-01-20

NVD last modified2026-06-17

Timeline

2026-01-20Published to the U.S. National Vulnerability Database (NVD)
2026-03-20First covered in a defend.network daily briefing
2026-06-17NVD record last updated

Affected product

Oracle Vm Virtualbox

Remediation Steps

Apply VMware patch VMSA-2026-0004 to all ESXi hosts.
If patching is not possible within 24 hours, disable OpenSLP service as temporary mitigation.
Scan ESXi host logs for indicators of compromise: unusual VM creation or encrypted VMDK files.
Verify backup integrity for all virtual machines on affected hosts.
Monitor network traffic from ESXi management interfaces for outbound connections to unknown IPs.

References

Referenced in our briefings & reports

Vulnerability Priority Report – Week 3 of March 2026 (March 14–20)
VMware ESXi ransomware exploit; BlackSuit healthcare breach (2026-03-20)

Browse all tracked CVEs in the defend.network CVE database →

🤖 This CVE page is generated by defend.network from NVD, CISA KEV, EPSS, and our verified daily briefings. Severity and exploitation data come from official sources; always verify remediation steps against the official vendor advisory before acting in production.