Home › Intelligence › Brief
VULNERABILITY BRIEF 🟠 High Vulnerability

Oracle VirtualBox VMSVGA Stack‑based Buffer Overflow (CVE‑2026‑46873) Enables Local Privilege Escalation

A newly disclosed stack‑based buffer overflow in Oracle VirtualBox’s VMSVGA device driver (CVE‑2026‑46873) allows a local attacker with code execution on a guest VM to gain hypervisor‑level privileges. For organizations subject to SOC 2, the flaw underscores the need for continuous hypervisor patch monitoring and evidence of timely remediation.

Verisq™ Intelligence · 📅 June 25, 2026 · 📰 zerodayinitiative.com
🟠
Severity
High
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
1 sector(s)
✅
Actions
3 recommended
📰
Source
zerodayinitiative.com

ZDI-26-362: Oracle VirtualBox VMSVGA Stack‑based Buffer Overflow (CVE‑2026‑46873) Enables Local Privilege Escalation

What It Is — A stack‑based buffer overflow in the VMSVGA device driver of Oracle VirtualBox allows a local attacker who can run code on a guest VM to gain code execution in the hypervisor context, effectively escalating privileges on the host. Exploitability — The vulnerability is publicly disclosed with proof‑of‑concept code; a vendor patch has been released. CVSS 7.5 (AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H).

Affected Products — Oracle VirtualBox (all versions prior to the June 2026 security update).

Why It Matters for Compliance & Audit Readiness

  • SOC 2 CC6.1 (System Operations) requires evidence that privileged access is tightly controlled; a host‑level escalation breaks that control.
  • Continuous monitoring of hypervisor patch status is a core audit artifact; missing patches create a control gap.
  • Timely remediation demonstrates a robust risk‑management process, a prerequisite for enterprise buyers demanding SOC 2 compliance.

Recommended Actions

  1. Verify that the June 2026 Oracle VirtualBox update is applied across all host systems.
  2. Map the vulnerability to SOC 2 CC6.1 and CC7.1 (Change Management) controls; capture patch‑level evidence in your compliance repository.
  3. Deploy automated configuration‑management tools to continuously validate hypervisor versions and generate audit‑ready logs.
  4. Review guest‑to‑host isolation policies and enforce least‑privilege execution for any code running inside VMs.

Source: Zero Day Initiative Advisory ZDI‑26‑362

📰 Original Source
http://www.zerodayinitiative.com/advisories/ZDI-26-362/ ↗

This Verisq Intelligence Brief is an independent analysis. Read the original reporting at the link above.

Vulnerability exposure

Is this CVE in your supply chain?

Verisq matches published vulnerabilities against the software your vendors run, so you know which relationships this touches before the next review.

See vendor exposure →