dbcve.org
Vm VirtualboxApplication · Oracle

CVE-2025-62590

HIGH · 8.2 CVSS v3.1 Published 2025-10-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/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). Supported versions that are affected are 7.1.12 and 7.2.2. Easily exploitable 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 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/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 local privilege escalation vulnerability in the Core component of Oracle VM VirtualBox (versions 7.1.12 and 7.2.2) allows a high-privileged attacker with local system access to compromise the virtualization platform and potentially gain control over the host or adjacent systems through the scope change mechanism.

MitigationApply Oracle's published security patches for this vulnerability; upgrade VirtualBox installations to patched versions. Since the attack requires high-privilege local access, ensure strict access controls on systems running VirtualBox and monitor for suspicious local activity.

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.1.12= 7.2.2

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

CVSS:3.1/AV:L/AC:L/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. Verify VirtualBox installation
    Check if Oracle VM VirtualBox is installed on the system by looking for the VBoxManage.exe executable in common installation paths such as C:\Program Files\Oracle\VirtualBox\ or /usr/lib/virtualbox/ on Linux, or by querying the system package manager.
    Affected if VirtualBox is installed on the system
  2. Determine installed VirtualBox version
    Run the command 'VBoxManage --version' from the VirtualBox installation directory or via PATH to retrieve the exact version number of the installed VirtualBox instance.
    Affected if The version returned matches exactly 7.1.12 or 7.2.2
  3. Check VirtualBox core services status
    On Windows, use Services.msc to verify that VirtualBox System Service or VirtualBox Global Service is running; on Linux, check for VBoxSVC or related VirtualBox daemon processes using 'ps aux | grep -i vbox'.
    Affected if VirtualBox core services are active and the version matches 7.1.12 or 7.2.2
  4. Verify VirtualBox kernel modules are loaded
    On Linux, run 'lsmod | grep vbox' to confirm VirtualBox kernel modules (vboxdrv, vboxnetadp, vboxnetflt) are loaded; on Windows, check Device Manager for VirtualBox entries under System devices.
    Affected if VirtualBox kernel modules or drivers are loaded and the version is 7.1.12 or 7.2.2

The system is affected if Oracle VM VirtualBox is installed with an exact version of 7.1.12 or 7.2.2 and the VirtualBox core components are active or loaded.

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 published security patches for this vulnerability; upgrade VirtualBox installations to patched versions. Since the attack requires high-privilege local access, ensure strict access controls on systems running VirtualBox and monitor for suspicious local activity.

Recommended fix High confidence

VirtualBox 7.1.14 or later 7.1.x / VirtualBox 7.2.4 or later 7.2.x

  1. 1. Download VirtualBox 7.1.14 (or later 7.1.x) from the official VirtualBox website: https://www.virtualbox.org/wiki/Downloads
  2. 2. Ensure all virtual machines are powered off and backed up if necessary
  3. 3. Uninstall the current VirtualBox version (7.1.12 or 7.2.2)
  4. 4. Install the new VirtualBox version (7.1.14 or later 7.1.x; alternatively 7.2.4 or later 7.2.x)
  5. 5. After installation, verify the version by checking Help > About VirtualBox
Caveat Minor: VirtualBox guest additions may need reinstallation or updating after the upgrade

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
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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