CVE-2025-62592VulnerabilityPublished 21 Oct 2025

CVE-2025-62592: Oracle VM VirtualBox · Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure

Affects Oracle VM VirtualBoxSource CVE Database V5

Not known to be exploited · CVSS 6.0 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.0Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Oracle Corporation Oracle VM VirtualBox	Affected =7.1.12 =7.2.2	Fixed in–

AI-suggested

European organizations should take several specific steps to mitigate the risk posed by CVE-2025-62592 beyond generic patching advice. First, restrict and monitor administrative access to hosts running Oracle VM VirtualBox, ensuring that only trusted personnel have high privilege accounts. Implement strict access controls and use multi-factor authentication for all privileged accounts to reduce the risk of credential compromise. Employ host-based intrusion detection and prevention systems to detect unusual activities indicative of exploitation attempts. Segregate VirtualBox hosts from critical production networks where possible, limiting the blast radius of a potential compromise. Regularly audit VirtualBox configurations and logs to identify unauthorized access or configuration changes. Since patches were not available at the time of disclosure, consider temporarily disabling or limiting the use of affected VirtualBox versions in sensitive environments until updates are released. Engage with Oracle support to obtain patches or workarounds as soon as they become available. Additionally, review and harden the security posture of other Oracle products integrated with VirtualBox to mitigate the scope change risk. Finally, maintain up-to-date backups of virtual machines and critical data to enable recovery in case of compromise.

Description

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).

Impact

For European organizations, the impact of CVE-2025-62592 can be significant, especially for those relying on Oracle VM VirtualBox for virtualization in production, development, or testing environments. The vulnerability allows attackers with high privileges on the host to access sensitive data within VirtualBox, potentially breaching confidentiality of virtual machines and their contents. This could lead to exposure of intellectual property, customer data, or internal credentials. Since virtualization often underpins critical infrastructure and cloud services, exploitation could facilitate further attacks or data exfiltration. The scope change implies that other Oracle products integrated with VirtualBox might also be indirectly affected, broadening the potential impact. Organizations in sectors with strict data protection regulations, such as finance, healthcare, and government, face increased compliance risks if sensitive data is compromised. Additionally, the requirement for high privilege access means that insider threats or attackers who have already breached perimeter defenses pose the greatest risk. The absence of known exploits reduces immediate threat but does not eliminate risk, as attackers may develop exploits rapidly once details are public. The medium severity rating suggests that while the vulnerability is serious, it is not trivially exploitable remotely or by low-privilege users, somewhat limiting its impact scope.

CWE-269Improper Privilege Management (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Separation of Privilege
Follow the principle of least privilege when assigning access rights to entities in a software system.
Architecture and Design · Separation of Privilege
Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Restful Privilege Elevation (opens in a new tab)
Privilege Abuse (opens in a new tab)
Privilege Escalation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

oracle.com/security-alerts/cpuoct2025.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Oct 2025, 22:06 UTC

WeaknessesCWE-269

Technical details

References

Community reviews

Related threats