# CVE-2026-47053: Missing authorization in Oracle VM VirtualBox

> A low-privileged attacker with local access can modify or delete critical VirtualBox data and cause partial denial of service via a missing authorization flaw.

- **Severity:** Medium 5.6 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 23 Jul 2026
- **Also known as:** GHSA-qqhx-m6vg-fc8g, UBUNTU-CVE-2026-47053

## What is CVE-2026-47053?

CVE-2026-47053 is a medium-severity missing authorization vulnerability in Oracle Vm Virtualbox, published on 21 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core).   The supported version that is affected is 7.2.12. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox.  Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in  unauthorized creation, deletion or modification access to critical data or all 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 5.6 (Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:L).

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-47053?

It affects 1 product.


Products: Oracle Vm Virtualbox.

## How do I fix CVE-2026-47053?

No fix has been published for CVE-2026-47053 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-47053 being exploited?

There is no known exploitation of CVE-2026-47053 in the wild and no public exploit code.

## Other vulnerabilities in Oracle Vm Virtualbox

- [CVE-2016-5605](https://insights.sbomify.com/CVE-2016-5605/): Unspecified vulnerability in the Oracle VM VirtualBox component before 5.1.4 in Oracle Virtualization allows remote attackers to affect conf (critical 9.1)
- [CVE-2018-3294](https://insights.sbomify.com/CVE-2018-3294/): Privilege escalation in VM VirtualBox (critical 9.0)
- [CVE-2024-21112](https://insights.sbomify.com/CVE-2024-21112/): Privilege escalation in VM VirtualBox (high 8.8)
- [CVE-2024-21113](https://insights.sbomify.com/CVE-2024-21113/): Privilege escalation in VM VirtualBox (high 8.8)
- [CVE-2024-21114](https://insights.sbomify.com/CVE-2024-21114/): Privilege escalation in VM VirtualBox (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47053 and fix it if it is affected.

What it is: CVE-2026-47053 is a medium-severity missing authorization vulnerability in Oracle Vm Virtualbox, published on 21 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-47053 in the wild and no public exploit code.

Affected product: Oracle Vm Virtualbox. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47053/ (Markdown: https://insights.sbomify.com/CVE-2026-47053/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47053
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47053
- OSV: https://osv.dev/vulnerability/CVE-2026-47053

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47053/
Summaries are generated and may contain mistakes; the official description above is the record.