Raw vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:LCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2025-21571 is a high-severity Incorrect Permission Assignment for Critical Resource (CWE-732) vulnerability in Oracle Vm Virtualbox. Its CVSS base score is 7.3 (High).
Operationally, ranked at the 20th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-21571 is a vulnerability in the Core component of Oracle VM VirtualBox, part of Oracle Virtualization. Supported versions affected by this issue are those prior to 7.0.24 and prior to 7.1.6. The vulnerability is associated with CWE-732 (Incorrect Permission Assignment for Critical Resource) and carries a CVSS 3.1 base score of 7.3, with impacts to confidentiality, integrity, and availability.
The vulnerability is easily exploitable by a high privileged attacker who has logon access to the infrastructure where Oracle VM VirtualBox executes. Such an attacker can compromise Oracle VM VirtualBox, and while the flaw resides in VirtualBox, exploitation may significantly impact additional products due to a change in scope. Successful attacks can result in unauthorized creation, deletion, or modification of critical data or all Oracle VM VirtualBox accessible data, unauthorized read access to a subset of Oracle VM VirtualBox accessible data, and unauthorized ability to cause a partial denial of service of Oracle VM VirtualBox. The CVSS vector is CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:L.
The Oracle security advisory provides details on mitigation, available at https://www.oracle.com/security-alerts/cpujan2025.html.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-2560
Vulnerability Data
Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are Prior to 7.0.24 and prior to 7.1.6. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM…
more
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 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 7.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:L).
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Enforces the access control policy that defines permissions on resources, thereby stopping incorrect assignments from remaining exploitable.
Directly requires assignment of only the minimum necessary permissions, preventing overly broad grants on critical resources.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
A.5.15 directly requires determining access needs, defining and communicating an access control policy, implementing rules that map rights/restrictions to entities (including consistency with classification), and considering need-to-know, privileged restrictions, segregation, formal authorization, and dynamic factors — which squarely stops most incorrect permission assignments from being exploitable; the bounded remainder is misconfigurations that violate the policy itself.
A.5.18 directly governs the provisioning, review, adjustment and revocation of logical access rights (including for critical resources) according to business needs, policy, SoD and risk, which stops most unintended actors from reading/modifying via incorrect permissions; the bounded remainder is incorrect permission assignments that are not access-right decisions at all (e.g. filesystem umask, ACL syntax errors).
A.8.2 directly controls the allocation, review, expiry, and use of privileged rights (including least-privilege, temporary grants, no generic IDs, and higher authentication), which stops most unintended read/modify cases named by CWE-732; the bounded remainder is non-privileged incorrect permission assignments (e.g. on files or objects that never require privilege).
Requiring explicit configuration of access controls and permissions for files, applications and services counters the assignment of overly permissive default or incorrect file-system rights.
A.8.32's formal change process (impact assessment, authorization, testing per 8.29, documentation, and enforcement across the SDLC) prevents most incorrect permission assignments on critical resources by catching them before or during implementation; the bounded remainder is ad-hoc/emergency changes or post-deployment permission drift outside the managed process.
A.8.4 strictly controls read/write access to source code and associated critical resources per roles/business needs (with audit and change-control integration), directly preventing most unintended read/modify cases in CWE-732; the bounded remainder is misconfigured permissions on non-source-code critical resources (e.g. configs, keys, or runtime artifacts) outside the clause's explicit scope.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.