dbcve.org
Vm VirtualboxApplication · Oracle

CVE-2026-46974

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: Core). 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 in Oracle VM VirtualBox Core component (version 7.2.8) allows a high-privileged attacker with local access to the infrastructure to compromise VirtualBox. The attack is difficult to exploit, requires high privileges and local logon access, but can result in complete takeover of VirtualBox with high impact on confidentiality, integrity, and availability.

MitigationApply Oracle's security patch for VirtualBox 7.2.8 when released, or upgrade to a patched version. Since exploitation requires local access by high-privileged users, enforce least-privilege access controls and monitor administrative activities on VirtualBox hosts.

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. Check if VirtualBox is installed
    On Windows: Open Control Panel > Programs and Features, look for Oracle VM VirtualBox. On Linux: Run 'VBoxManage --version' or check /usr/lib/virtualbox. On macOS: Check /Applications for VirtualBox.app or run 'VBoxManage --version' in Terminal.
    Affected if VirtualBox is not installed on the system - not affected
  2. Determine the installed VirtualBox version
    Run 'VBoxManage --version' from command line/terminal. This command works on all supported host operating systems and displays the exact version number.
    Affected if Version displayed is 7.2.8 exactly - affected by this CVE
  3. Compare your version to the affected range
    The CVE specifies only version 7.2.8 is affected. If your version is different (older or newer), you are not affected by this specific CVE.
    Affected if Running version 7.2.8 - this is the only affected version per the CVE
  4. Verify this is the Core component
    The vulnerability affects VirtualBox Core component. The version check above covers this since VirtualBox version 7.2.8 is the specific affected release.
    Affected if Any VirtualBox installation at version 7.2.8 contains the vulnerable Core component

You are affected only if VirtualBox version 7.2.8 is installed; any other version or no VirtualBox installation means you are not affected by CVE-2026-46974.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle's security patch for VirtualBox 7.2.8 when released, or upgrade to a patched version. Since exploitation requires local access by high-privileged users, enforce least-privilege access controls and monitor administrative activities on VirtualBox hosts.

Fix this in Vm Virtualbox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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