Oracle released VirtualBox 7.2.18, remediating 11 vulnerabilities and 19 additional defects. The most severe issue, CVE-2026-87273, carries a CVSS score of 8.6; five further flaws are rated 7.8, including four affecting Windows. The vulnerabilities could allow a guest virtual machine to access its host system, creating a material isolation risk for affected VirtualBox deployments.
The release also improves Linux Guest Additions compatibility and stability, Windows 11 on ARM support, VDI media handling, Linux-host 3D acceleration, and Shared Clipboard reliability. Organizations using VirtualBox should prioritize updating hosts and guest tooling to version 7.2.18, particularly where untrusted or externally supplied virtual machines are run.

See real exploitation activity before you spend the cycle.
2 events from the most recent confirmed update back to the earliest known activity.
Oracle released VirtualBox 7.2.18, fixing 11 vulnerabilities and 19 additional defects. The update addresses CVE-2026-87273 (CVSS 8.6) and five further flaws rated 7.8, with disclosed issues potentially allowing guest-to-host access.
Oracle released a Critical Patch Update addressing 673 vulnerabilities across its products, including fixes for MySQL, Java SE/GraalVM, and Solaris. The update includes two Java SE/GraalVM flaws remotely exploitable over HTTP, including a GraalVM vulnerability rated CVSS 8.1.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
3 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.