CVE-2026-35245
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 · uneditedVulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). The supported version that is affected is 7.2.6. Easily exploitable vulnerability allows unauthenticated attacker with network access via RDP to compromise Oracle VM VirtualBox. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle VM VirtualBox. CVSS 3.1 Base Score 7.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 confidenceDenial of service vulnerability in Oracle VM VirtualBox 7.2.6 Core component, exploitable via network access through RDP. An unauthenticated attacker can cause the virtual machine to hang or repeatedly crash, resulting in complete availability loss.
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= 7.2.6CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify VirtualBox versionRun 'VBoxManage --version' on Linux/Mac or check the installed version via Programs and Features on Windows. On Linux, you can also check 'dpkg -l | grep virtualbox' or 'rpm -q VirtualBox'.Affected if The installed version is exactly 7.2.6
-
Identify VMs with RDP enabledRun 'VBoxManage list vms' to list all VMs, then for each VM run 'VBoxManage showvminfo <vmname> | grep -i rdp' to check if RDP is enabled. On Windows, open VirtualBox Manager and inspect each VM's Settings > Display > Remote Display.Affected if Any virtual machine has the Remote Display (RDP) server enabled
-
Check RDP listener statusRun 'netstat -an | grep 3389' (or the custom RDP port if configured) or 'ss -tlnp | grep 3389' to verify if VirtualBox RDP is listening on a network interface. Check VirtualBox global settings via 'VBoxManage list systemproperties' for default RDP port.Affected if VirtualBox RDP service is listening on a network-facing port (default 3389)
-
Assess network exposure of RDP serviceReview firewall rules and network configuration to determine if the RDP port is accessible from untrusted networks. Check if the host's network interface binding allows external connections versus localhost only.Affected if RDP port is bound to 0.0.0.0 or an interface accessible from untrusted networks
A user is affected if VirtualBox 7.2.6 is installed AND any VM has RDP enabled with network accessibility from untrusted networks, allowing unauthenticated attackers to cause denial of service.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Oracle's security patch for VirtualBox 7.2.6 when available. As an interim control, restrict RDP access to VirtualBox instances to trusted networks or users only, and disable RDP if not required.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35245 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-35245 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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