dbcve.org
Vm VirtualboxApplication · Oracle

CVE-2026-46877

MEDIUM · 6.0 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 →
62/100
Remediation priority · Elevated
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. 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).

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 · high confidence

This is a vulnerability in Oracle VM VirtualBox's emulated VMSVGA (VMware SVGA) graphics device. The vulnerability allows a high-privileged attacker with local system access to potentially read sensitive data from the VirtualBox environment. The VMSVGA device is the emulated graphics adapter used for VMware-compatible graphics in virtual machines.

MitigationApply the Oracle security patch for VirtualBox 7.2.8 when released. Until then, limit physical/logical access to the VirtualBox host systems and monitor for suspicious activity.

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
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

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

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 and version
    Run 'vboxmanage --version' on the host system to retrieve the installed VirtualBox version number
    Affected if The installed version is exactly 7.2.8
  2. Identify VirtualBox installation path
    Check common installation directories (C:\Program Files\Oracle\VirtualBox on Windows or /usr/lib/virtualbox on Linux) for VirtualBox binaries and verify version via 'VBoxManage --version' output
    Affected if VirtualBox 7.2.8 binaries are present on the system
  3. Locate configured virtual machines
    Run 'vboxmanage list vms' to enumerate all registered virtual machines on the host
    Affected if Any virtual machines are registered with this VirtualBox installation
  4. Inspect VM graphics device configuration
    For each VM, run 'vboxmanage showvminfo <vmname>' and look for the 'Graphics Controller' setting under the display or video configuration section. Check if the controller type is set to VMSVGA or VMware SVGA
    Affected if Any virtual machine has its graphics controller configured to use the VMSVGA (VMware SVGA) device

A system is affected if it runs Oracle VM VirtualBox version 7.2.8 with at least one virtual machine configured to use the VMSVGA graphics controller, allowing a high-privileged local attacker to potentially read sensitive data through the emulated device.

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 the Oracle security patch for VirtualBox 7.2.8 when released. Until then, limit physical/logical access to the VirtualBox host systems and monitor for suspicious activity.

Recommended fix Moderate confidence

VirtualBox 7.2.9 or latest 7.2.x stable release

  1. 1. Identify the current Oracle VM VirtualBox version installed by checking Help > About VirtualBox or running 'VBoxManage --version'
  2. 2. Navigate to the Oracle VirtualBox official downloads page at https://www.oracle.com/virtualization/virtualbox/
  3. 3. Download the latest VirtualBox 7.2.x release (or a later stable release if available) for your host operating system
  4. 4. Ensure all virtual machines are powered off (not saved state) before upgrading
  5. 5. Run the VirtualBox installer and follow the prompts to upgrade the installation
  6. 6. After upgrade, verify the new version by running 'VBoxManage --version' to confirm installation was successful
  7. 7. Test that critical virtual machines start and operate normally post-upgrade
Caveat Oracle VirtualBox upgrades may require reinstallation of the VirtualBox Extension Pack; ensure compatibility before upgrading production VMs

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46877 — 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-46877 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