- Top reward
- $1,500
- Top severity paid
- Critical
- Assets in scope
- 15
- Public CVEs
- 428
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays from $1,500
- for critical bugs.
- Report on Sorona
- Submit through the program page.
- Partial safe harbor
- Some legal protection; read the terms.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What Sorona lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical | $1,500+ | |
| High | $700+ | |
| Medium | $300+ | |
| Low |
|
$100 $100 / 1 month Claude Max |
- Safe harbor
-
Partial
Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf.
Summarised with AI from the program policy on Sorona, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
15 assets you may test, 6 excluded.
Web 1
- https://www.virtualbox.org
Products and areas 14
- Disk image handling for VDI, VMDK, VHD and the other supported formats, plus OVF and OVA appliance import
- Oracle's reporting page is the declared channel: PGP-encrypted email to the security alert address, with fixes shipped in the quarterly Critical Patch Update and credit given in the advisory. virtualbox.org routes security findings there and away from the public tracker. Nothing narrower is declared, so the whole product is in
- Shared folders in full, on every host platform
- The 3D acceleration and graphics stack, where guest-supplied rendering commands are interpreted by host code
- The emulated network adapters, including E1000, PCnet and virtio-net, plus the user-space NAT stack behind them
- The emulated storage controllers in full, including IDE, AHCI, NVMe, LsiLogic and BusLogic
- The Guest Additions and every host channel they open: shared clipboard, drag and drop, guest properties, guest control, and the VBoxService and VBoxClient pair
- The HGCM host-guest communication manager and every service registered on it
- The host kernel drivers on Windows, macOS and Linux, including VBoxDrv and the network filter and adapter drivers
- The installer and the update mechanism on each host platform, plus the Extension Pack components where they are reachable
- The VMM core: the hardware virtualization backends, the recompiler paths and the instruction emulation behind both
- The VRDE remote display server and any other network-facing console path
- USB emulation across OHCI, EHCI and xHCI, along with the audio and graphics device implementations
- VBoxSVC and the COM and XPCOM API surface, including how a less privileged host user reaches it
Out of scope (6)
- Configuration that deliberately removes isolation, for example enabling a writable shared folder and then reporting that the guest wrote to it
- Findings filed on the public bug tracker, which the project asks you not to use for security issues
- Guest operating system defects rather than VirtualBox
- Host operating system defects or CPU errata rather than VirtualBox's handling of them
- Other Oracle products, which share the reporting address but are entirely different targets
- Third-party front ends such as Vagrant and the various management GUIs
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Sorona's policy. "We" in these lines means Sorona, not this site.
While testing
-
Submit through sorona.xyz. This project runs no bounty of its own; we validate, coordinate disclosure with the maintainers, and pay you directly.
-
Report to the address on the policy page , PGP-encrypted to Oracle's published public key using the step-by-step procedure on the reporting page
-
Do not use the public bug tracker. virtualbox.org routes security findings away from it and to Oracle explicitly
-
State the host platform and version alongside the guest.
-
Say whether the Extension Pack was installed and whether Guest Additions were running.
-
Hold detail until that advisory is out.
Not accepted
-
Guest operating system defects rather than VirtualBox
-
Host operating system defects or CPU errata rather than VirtualBox's handling of them
-
Third-party front ends such as Vagrant and the various management GUIs
-
Configuration that deliberately removes isolation, for example enabling a writable shared folder and then reporting that the guest wrote to it
-
Findings filed on the public bug tracker, which the project asks you not to use for security issues
-
Other Oracle products, which share the reporting address but are entirely different targets
Summarised with AI from the program policy on Sorona, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 1 hour ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
Sorona credits this project with 428 CVEs, 55 of them recent. The individual records appear here after the next sync.
Original policy
Copied from sorona.xyz on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Skip to content What this pays This project runs no bounty of its own. sorona.xyz pays you directly on qualified, reproduced findings. Severity │ sorona.xyz pays Critical │ $1,500+ High │ $700+ Medium │ $300+ Low │ $100 / 1 month Claude Max Submit a vulnerability CVE history 55 Last 12 months 428 Lifetime Guest-to-host escape 40 % Memory safety 25 % Local privilege escalation 20 % Info disclosure 15 % Latest advisories Loading the feed Overview VirtualBox is the most-installed desktop hypervisor there is, running on developer laptops, Vagrant environments and CI runners across Windows, macOS and Linux. A guest-to-host escape lands on a machine holding source code, SSH keys and cloud credentials. Oracle takes reports through an encrypted security address and ships fixes in the quarterly Critical Patch Update, where the stated reward is credit in the advisory. Oracle's vulnerability handling documentation carries no bounty or compensation language anywhere, and Oracle runs no programme on any commercial platform. sorona.xyz pays you directly on qualified, reproduced findings. In scope Oracle's reporting page is the declared channel: PGP-encrypted email to the security alert address, with fixes shipped in the quarterly Critical Patch Update and credit given in the advisory. virtualbox.org routes security findings there and away from the public tracker. Nothing narrower is declared, so the whole product is in The VMM core: the hardware virtualization backends, the recompiler paths and the instruction emulation behind both The emulated storage controllers in full, including IDE, AHCI, NVMe, LsiLogic and BusLogic The emulated network adapters, including E1000, PCnet and virtio-net, plus the user-space NAT stack behind them USB emulation across OHCI, EHCI and xHCI, along with the audio and graphics device implementations The 3D acceleration and graphics stack, where guest-supplied rendering commands are interpreted by host code Shared folders in full, on every host platform The Guest Additions and every host channel they open: shared clipboard, drag and drop, guest properties, guest control, and the VBoxService and VBoxClient pair The HGCM host-guest communication manager and every service registered on it The host kernel drivers on Windows, macOS and Linux, including VBoxDrv and the network filter and adapter drivers VBoxSVC and the COM and XPCOM API surface, including how a less privileged host user reaches it Disk image handling for VDI, VMDK, VHD and the other supported formats, plus OVF and OVA appliance import The VRDE remote display server and any other network-facing console path The installer and the update mechanism on each host platform, plus the Extension Pack components where they are reachable Out of scope Guest operating system defects rather than VirtualBox Host operating system defects or CPU errata rather than VirtualBox's handling of them Third-party front ends such as Vagrant and the various management GUIs Configuration that deliberately removes isolation, for example enabling a writable shared folder and then reporting that the guest wrote to it Findings filed on the public bug tracker, which the project asks you not to use for security issues Other Oracle products, which share the reporting address but are entirely different targets Most-valued findings Guest-to-host escape out of an emulated device, the class that matters most on a machine holding a developer's credentials and source tree The 3D and graphics path, where guest-supplied rendering commands reach host code with a large and lightly-audited parsing surface Shared folder handling, including path traversal and symlink resolution that reaches outside the shared directory The HGCM services and the Guest Additions channels. Clipboard, drag and drop, guest control and guest properties are all guest-controlled input arriving at a host process Local privilege escalation on the host through the kernel drivers or through VBoxSVC, both of which unprivileged host users can reach Disk image and appliance parsing, since a VMDK or an OVA is attacker-controlled input in every workflow that imports one Memory safety in the network implementations, including the user-space NAT stack that processes guest traffic on the host side Anything specific to the macOS or Windows host drivers, which see less independent research than the Linux side Program rules Submit through sorona.xyz. This project runs no bounty of its own; we validate, coordinate disclosure with the maintainers, and pay you directly. Report to [email protected] , PGP-encrypted to Oracle's published public key using the step-by-step procedure on the reporting page Do not use the public bug tracker. virtualbox.org routes security findings away from it and to Oracle explicitly Oracle's stated reward is credit in the Critical Patch Update advisory. There is no money in the process and no reward terms to negotiate Fixes ship on the quarterly Critical Patch Update cycle, so expect a long wait between acknowledgement and publication and plan your own timeline around it State the host platform and version alongside the guest. The kernel drivers differ substantially between Windows, macOS and Linux and get uneven attention Say whether the Extension Pack was installed and whether Guest Additions were running. Both open surface that is absent in a bare install Disclosure Coordinated by Oracle's security alert team through the encrypted reporting address, with the fix released in a quarterly Critical Patch Update and the researcher credited in the accompanying advisory. Oracle publishes on a fixed calendar rather than per finding, so the embargo runs to the next scheduled CPU date rather than to a day count from your report. Hold detail until that advisory is out. Safe harbor Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf. You are responsible for understanding and following the laws that apply to you, wherever you are, and for staying within any scope the project has defined. Submit a vulnerability