dbcve.org
Vm VirtualboxApplication · Oracle

CVE-2025-62591

MEDIUM · 6.0 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 →
62/100
Remediation priority · Elevated
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 unauthorized access to critical data or complete access to all Oracle VM VirtualBox accessible data. CVSS 3.1 Base Score 6.0 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/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

A local privilege escalation vulnerability in Oracle VM VirtualBox Core (versions 7.1.12 and 7.2.2) allows a high-privileged attacker with local system access to potentially gain unauthorized access to sensitive data. The CVSS vector indicates a local attack requiring high privileges but no user interaction, with high confidentiality impact and scope change affecting additional products.

MitigationApply Oracle's patched VirtualBox version (later than 7.2.2) or vendor-supplied security update. Verify no unauthorized access has occurred and review access controls for systems running VirtualBox.

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/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. Confirm VirtualBox installation
    Check if Oracle VM VirtualBox is installed on the system. On Windows, inspect the registry key HKLM\SOFTWARE\Oracle\VirtualBox or look in Programs and Features. On Linux, run 'VBoxManage --version' or check installed packages with dpkg/rpm. On macOS, inspect /Applications for VirtualBox.app.
    Affected if VirtualBox is not found on the system, the system is not affected by this specific vulnerability.
  2. Retrieve installed VirtualBox version
    Run 'VBoxManage --version' from command line (add to PATH if needed), or check the version displayed in the VirtualBox GUI under Help > About, or query the registry value Version on Windows.
    Affected if Unable to determine the installed version prevents assessment of this specific CVE.
  3. Compare version against affected releases
    Match the retrieved version string exactly against 7.1.12 and 7.2.2. Note that only these two specific versions are affected; earlier versions (like 7.1.10, 7.1.0) and later patched versions (7.2.4, 7.3.0) are not vulnerable.
    Affected if The installed version is exactly 7.1.12 or exactly 7.2.2, indicating the system may be affected by this CVE.
  4. Verify current patch level
    If the version is 7.1.12 or 7.2.2, check for any installed updates or patches. Query the system for recent VirtualBox-related updates: on Windows check installed updates, on Linux check package history.
    Affected if No security updates have been applied to the affected versions, increasing likelihood of exposure.

A system is affected if Oracle VM VirtualBox version 7.1.12 or 7.2.2 is installed and no vendor security patches have been applied.

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's patched VirtualBox version (later than 7.2.2) or vendor-supplied security update. Verify no unauthorized access has occurred and review access controls for systems running VirtualBox.

Fix this in Vm Virtualbox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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