dbcve.org
Vm VirtualboxApplication · Oracle

CVE-2026-35275

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: Shared Folders). The supported version that is affected is 7.2.8. Difficult to exploit vulnerability allows low 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 creation, deletion or modification access to critical data or all Oracle VM VirtualBox accessible data as well as unauthorized access to critical data or complete access to all Oracle VM VirtualBox accessible data. CVSS 3.1 Base Score 7.5 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/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 · moderate confidence

Vulnerability in Oracle VM VirtualBox Shared Folders component (version 7.2.8) allows a low-privileged attacker with local infrastructure access to compromise confidentiality and integrity of data accessible through VirtualBox shared folders. The attack requires local access (AV:L) and has high attack complexity, but can impact additional products beyond VirtualBox due to scope change.

MitigationApply Oracle's patches for VirtualBox 7.2.8 when available; until then, disable Shared Folders if not required, restrict physical/logical access to VirtualBox host infrastructure, and apply least-privilege principles to user accounts on the VirtualBox host.

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

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/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. Determine VirtualBox installation status and version
    Run 'VBoxManage --version' on the host system to retrieve the installed VirtualBox version
    Affected if The reported version is exactly 7.2.8
  2. Check if VirtualBox is present
    Look for VirtualBox installation directory (typically C:\Program Files\Oracle\VirtualBox on Windows or /usr/lib/virtualbox on Linux) and verify the executable VBoxManage exists
    Affected if VirtualBox 7.2.8 is installed on the system
  3. Identify configured Shared Folders
    Run 'VBoxManage sharedfolder list --global' to enumerate all shared folders defined across all virtual machines, or check the VirtualBox.xml configuration file for <SharedFolder> entries
    Affected if Any shared folders are configured or mapped to virtual machines
  4. Check for active shared folder mounts in running VMs
    For each running VM, run 'VBoxManage showvminfo <vmname>' and look for shared folder mappings, or inspect the VM configuration files (*.vbox) for <SharedFolder> elements with active='true'
    Affected if Running virtual machines have shared folders actively mounted or mapped

The environment is affected only if VirtualBox version 7.2.8 is installed AND Shared Folders feature is configured or actively in use on the host system.

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's patches for VirtualBox 7.2.8 when available; until then, disable Shared Folders if not required, restrict physical/logical access to VirtualBox host infrastructure, and apply least-privilege principles to user accounts on the VirtualBox host.

Recommended fix Moderate confidence

VirtualBox 7.2.10 or later stable release (check Oracle's VirtualBox release notes for exact patched version)

  1. 1. Identify the current VirtualBox installation version by checking Help > About VirtualBox or running `VBoxManage --version`
  2. 2. Download the latest VirtualBox version from the official Oracle website (https://www.virtualbox.org/wiki/Downloads)
  3. 3. Ensure all running virtual machines are powered off before upgrading
  4. 4. Uninstall the current VirtualBox version (7.2.8) using the system's program removal utility
  5. 5. Install the latest stable VirtualBox release which includes the security fix for the Shared Folders access control vulnerability
  6. 6. After installation, verify the new version is running by checking VBoxManage --version
  7. 7. Review and test Shared Folder configurations after upgrade to ensure proper functionality
Caveat Minor: Guest Additions may need reinstallation after upgrade to ensure full compatibility with Shared Folders functionality

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
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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