dbcve.org
Vm VirtualboxApplication · Oracle

CVE-2026-35248

MEDIUM · 5.0 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 →
52/100
Remediation priority · Moderate
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 unauthorized update, insert or delete access to some of Oracle VM VirtualBox accessible data as well as unauthorized read access to a subset of Oracle VM VirtualBox accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle VM VirtualBox. CVSS 3.1 Base Score 5.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:L).

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

Vulnerability in Oracle VM VirtualBox Core component (version 7.2.6) that allows a high-privileged attacker with local access to the infrastructure to potentially read, modify, or delete some VirtualBox accessible data, and cause partial denial of service. The high attack complexity and requirement for high privileges make it difficult to exploit.

MitigationApply Oracle patches when available; limit and closely control access to systems running VirtualBox; follow principle of least privilege for user accounts with access to the virtualization infrastructure.

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
Low
Integrity
Low
Availability
Low

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

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 on the system by looking for the VBoxManage binary. On Linux/macOS, run 'which VBoxManage' or 'ls /usr/bin/VBoxManage'. On Windows, check for 'VBoxManage.exe' in the VirtualBox installation directory (commonly C:\Program Files\Oracle\VirtualBox).
    Affected if VirtualBox is not installed on the system.
  2. Determine installed VirtualBox version
    Run 'VBoxManage --version' from the command line. This command outputs the version in format like '7.2.6r123456'. Record the full version string including the build number.
    Affected if Unable to retrieve version information, indicating VirtualBox may not be properly installed.
  3. Compare version against CVE-affected release
    Compare the installed version from step 2 to the affected version '7.2.6'. Check if the version string starts with '7.2.6' exactly (e.g., 7.2.6, 7.2.6r123456).
    Affected if The installed version is exactly 7.2.6 (any build number). Versions before or after 7.2.6 are not affected by this specific CVE.
  4. Assess high-privileged local access context
    Identify users with high-privileged local access to the VirtualBox host system. Check for users in privileged groups (such as sudo, root, Administrators, or equivalent) who have local system access. Review user accounts with permissions to manage VirtualBox VMs.
    Affected if The system has high-privileged local users who can access the VirtualBox infrastructure. The vulnerability requires a high-privileged attacker with local access to the host.

A system is affected if VirtualBox version 7.2.6 is installed AND there are high-privileged local users who can access the VirtualBox 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.

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

Apply Oracle patches when available; limit and closely control access to systems running VirtualBox; follow principle of least privilege for user accounts with access to the virtualization infrastructure.

Fix this in Vm Virtualbox Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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