dbcve.org
Vm VirtualboxApplication · Oracle

CVE-2026-46873

HIGH · 7.5 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: VMSVGA device). The supported version that is affected is 7.2.8. Difficult to exploit 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 takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 7.5 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A vulnerability exists in the VMSVGA virtual graphics device emulation of Oracle VM VirtualBox 7.2.8. This is a local privilege escalation vulnerability requiring high-privileged attacker access to the infrastructure where VirtualBox executes. The high complexity and local attack vector suggest exploitation requires careful crafting of malicious VM configurations or inputs to the VMSVGA device, potentially allowing escape from the virtual machine context to compromise the VirtualBox installation itself.

MitigationApply Oracle's patched version of VirtualBox when available. Until then, restrict administrative/root access to VirtualBox host systems, limit which users can create or modify VM configurations, and consider network segmentation to limit exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Vm VirtualboxApplication
Affected:= 7.2.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify VirtualBox installation
    Check if VirtualBox is installed by looking for the VBoxManage command-line tool: run 'VBoxManage --version' or check for VirtualBox installation directories (e.g., /usr/lib/virtualbox on Linux, C:\Program Files\Oracle\VirtualBox on Windows)
    Affected if VirtualBox is installed on the system
  2. Determine installed VirtualBox version
    Run 'VBoxManage --version' to retrieve the exact version number of the VirtualBox installation
    Affected if The version returned is 7.2.8 exactly
  3. Identify VMs using VMSVGA graphics controller
    Run 'VBoxManage list vms' to list all VMs, then for each VM run 'VBoxManage showvminfo <vmname> | grep -i graphics' or 'VBoxManage showvminfo <vmname>' to check the graphics controller setting, specifically looking for VMSVGA
    Affected if Any virtual machine is configured to use the VMSVGA graphics controller
  4. Check for high-privileged user access
    Review system permissions to determine if untrusted users have administrative or root access to the VirtualBox host system, or the ability to create/modify VM configurations
    Affected if Untrusted or low-privilege users have administrative access to the VirtualBox host or can modify VM configurations

A system is affected only if VirtualBox version 7.2.8 is installed AND VMs are configured to use the VMSVGA graphics controller, with an attacker who already has high-privileged access to the host system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle's patched version of VirtualBox when available. Until then, restrict administrative/root access to VirtualBox host systems, limit which users can create or modify VM configurations, and consider network segmentation to limit exposure.

Recommended fix Moderate confidence

VirtualBox 7.2.14 or latest stable 7.2.x release

  1. 1. Download the latest stable version of Oracle VM VirtualBox from the official Oracle website (https://www.virtualbox.org/wiki/Downloads)
  2. 2. Ensure all running virtual machines are properly shut down before upgrading
  3. 3. Uninstall the current VirtualBox 7.2.8 installation
  4. 4. Install the latest VirtualBox version (recommended: 7.2.14 or later stable release)
  5. 5. After installation, verify the installed version matches the expected fixed release
  6. 6. Test that existing virtual machines start correctly with the new VirtualBox version
  7. 7. Revert to the previous version and delay upgrade only if critical business VMs exhibit compatibility issues after thorough testing
Caveat VirtualBox upgrades may require reconfiguring VM settings or graphics controllers; test existing VMs before production use

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vm Virtualbox Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46873 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46873 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data