dbcve.org
Vm VirtualboxApplication · Oracle

CVE-2026-35230

HIGH · 7.5 CVSS v3.1 Published 2026-04-21
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.6. 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 · high confidence

A vulnerability in Oracle VM VirtualBox version 7.2.6 Core component allows a high-privileged attacker with local infrastructure access to compromise VirtualBox, potentially achieving full takeover. The attack requires local access and high privileges, with high attack complexity, but the scope change indicates potential impact to additional products.

MitigationUpgrade Oracle VM VirtualBox to the latest patched version once available from Oracle. Until then, restrict physical and logical access to systems running VirtualBox to high-privileged administrators only.

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.6

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 Oracle VM VirtualBox is installed
    Look for VirtualBox installation directory (typically C:\Program Files\Oracle\VirtualBox on Windows or /usr/lib/virtualbox on Linux) or run 'VBoxManage --version' command if VBoxManage is in PATH
    Affected if VirtualBox is present on the system
  2. Verify the exact installed version
    Run 'VBoxManage --version' from command line or check the version displayed in VirtualBox GUI (Help > About VirtualBox)
    Affected if The version displayed is exactly 7.2.6
  3. Confirm the Core component is present
    The Core component is the main VirtualBox engine; check that VirtualBox functions normally (can create/start a VM) to confirm Core is loaded
    Affected if VirtualBox Core functionality is operational (the vulnerability affects this component)
  4. Assess access context
    Determine if the system allows local access by non-privileged users or if high-privileged access is required for the attack vector
    Affected if High-privileged attacker with local infrastructure access is possible (required for exploitation)

You are affected if Oracle VM VirtualBox version 7.2.6 is installed and running, with the Core component active and accessible to a high-privileged local attacker.

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

Upgrade Oracle VM VirtualBox to the latest patched version once available from Oracle. Until then, restrict physical and logical access to systems running VirtualBox to high-privileged administrators only.

Recommended fix Moderate confidence

VirtualBox version greater than 7.2.6 (check Oracle security advisory for exact fixed release)

  1. 1. Check Oracle's official VirtualBox release notes and security advisories for CVE-2026-35230 to identify the specific fixed version
  2. 2. If a newer VirtualBox version (greater than 7.2.6) is available with the security fix, download it from the official Oracle VirtualBox website
  3. 3. Before upgrading, create a backup of all virtual machines or export them if possible
  4. 4. Uninstall the current VirtualBox 7.2.6 installation
  5. 5. Install the newer fixed version of VirtualBox
  6. 6. Verify that the installed version matches the expected fixed version
  7. 7. Re-import any virtual machines that were exported as backups
Caveat Minor - verify VM compatibility with newer VirtualBox version and update Extension Pack if used

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

Fix this in Vm Virtualbox Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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