dbcve.org
Vm VirtualboxApplication · Oracle

CVE-2026-35246

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 local privilege escalation vulnerability in Oracle VM VirtualBox Core (version 7.2.6) allows a high-privileged attacker with logon access to the infrastructure to compromise VirtualBox and potentially impact additional products through scope change. Successful exploitation yields complete confidentiality, integrity, and availability compromise.

MitigationApply Oracle VM VirtualBox patches when released; restrict physical and logical access to the hypervisor infrastructure and limit privileged user accounts.

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. Confirm VirtualBox installation
    On Windows: Check Program Files\Oracle\VirtualBox or run 'VBoxManage --version' from Command Prompt. On Linux: Run 'VBoxManage --version' or check via package manager (dpkg -l | grep virtualbox, rpm -q VirtualBox). On macOS: Check /Applications for VirtualBox.app or run 'VBoxManage --version'.
    Affected if VirtualBox is not installed on the system
  2. Retrieve installed VirtualBox version
    Execute 'VBoxManage --version' from a command prompt or terminal. This command returns the exact version string of the installed VirtualBox instance.
    Affected if Command fails or VirtualBox is not recognized (not installed)
  3. Compare version against CVE-affected release
    Verify if the version output from the previous step is exactly '7.2.6'. Compare the full version string returned by VBoxManage to the affected version 7.2.6.
    Affected if Installed version equals 7.2.6 exactly

The system is affected if Oracle VM VirtualBox version 7.2.6 is installed and the attacker has high-privileged logon access to the infrastructure.

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 VM VirtualBox patches when released; restrict physical and logical access to the hypervisor infrastructure and limit privileged user accounts.

Recommended fix Moderate confidence

VirtualBox latest stable release (currently 7.2.x or 7.3.x series)

  1. 1. Backup all virtual machines and VirtualBox configuration data
  2. 2. Download the latest stable VirtualBox release from the official Oracle website (https://www.virtualbox.org/wiki/Downloads)
  3. 3. Uninstall the current VirtualBox 7.2.6 installation
  4. 4. Install the latest VirtualBox version following the installation wizard prompts
  5. 5. After installation, verify the new version by checking Help > About VirtualBox
  6. 6. Re-register any existing virtual machines that were not automatically detected
Caveat Minor: Some older VM configurations may require adjustment; guest additions may need reinstallation

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
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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