- Top reward
- $1,500
- Top severity paid
- Critical
- Assets in scope
- 11
- Public CVEs
- 60
- 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
11 assets you may test, 6 excluded.
Web 1
- https://www.qemu.org
Products and areas 10
- Device passthrough and the IOMMU-facing paths, including vhost and vhost-user backends
- Live migration, including the state one host deserialises from another
- QEMU's security process splits by use case rather than by component. The virtualization use case is what it triages: a guest that should not be able to reach the host, and a host that should not be exposed by running one. Everything below sits inside that framing
- TCG, the translation engine, where guest instruction sequences become host code
- The block layer and every disk image format QEMU parses, since an image file is frequently supplied by somebody other than the operator
- The firmware and boot interfaces QEMU presents to a guest, which a guest can drive from its first instruction
- The host-facing services QEMU exposes: NBD, VNC, SPICE and the character device backends
- The QMP and HMP monitor interfaces and anything a management layer drives through them
- The whole system-mode device model set: network, block, SCSI, USB, display, audio, character and input devices, emulated and paravirtualised alike
- virtio in full, including the shared-memory ring handling that every modern guest drives
Out of scope (6)
- Findings that depend on a long embargo, since the process refuses arbitrary embargo requests
- Guest-visible crashes and misbehaviour that stay inside the guest without reaching the host or another tenant
- Operator configuration decisions, including deliberately exposing a monitor socket or a VNC server with no authentication
- qemu-user emulation, which is the non-virtualization case in practice and therefore the weakest part of this scope
- The host kernel, KVM itself and the management stack around QEMU, all of which belong to their own projects
- The non-virtualization use case, which the process states is generally ineligible. Reports there are converted into public bugs
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Sorona's policy.
While testing
-
Submit through sorona.xyz.
-
File a GitLab work item on the QEMU project and mark it confidential before you submit.
-
Email disclosure is no longer accepted. There is no security address to write to
-
Frame the finding as the virtualization use case.
-
Expect a short embargo.
-
Low-severity issues may be published with no patch available, so do not plan a coordinated release around one
Not accepted
-
The non-virtualization use case, which the process states is generally ineligible
-
qemu-user emulation, which is the non-virtualization case in practice
-
Guest-visible crashes and misbehaviour that stay inside the guest without reaching the host or another tenant
-
Operator configuration decisions, including deliberately exposing a monitor socket or a VNC server with no authentication
-
The host kernel, KVM itself and the management stack around QEMU
-
Findings that depend on a long embargo
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.
| CVE | Summary | Severity | Published |
|---|---|---|---|
| CVE-2025-54567 | hw/pci/pcie_sriov.c in QEMU through 10.0.3 mishandles the VF Enable bit write mask, a related issue to CVE-2024-26327. | Medium 4.2 | 25 Jul 2025 |
| CVE-2025-54566 | hw/pci/pcie_sriov.c in QEMU through 10.0.3 has a migration state inconsistency, a related issue to CVE-2024-26327. | Medium 4.2 | 25 Jul 2025 |
| CVE-2024-7730 | A heap buffer overflow was found in the virtio-snd device in QEMU. When reading input audio in the virtio-snd input callback, virtio_snd_pcm_in_cb, the function did not check whether the iov can fit the data buffer. This issue can trigger an out-of-bounds write if the size of the virtio queue element is equal to virtio_snd_pcm_status, which makes the available space for audio data zero. | High 7.4 | 14 Nov 2024 |
| CVE-2024-3447 | A heap-based buffer overflow was found in the SDHCI device emulation of QEMU. The bug is triggered when both `s->data_count` and the size of `s->fifo_buffer` are set to 0x200, leading to an out-of-bound access. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition. | Medium 6.0 | 14 Nov 2024 |
| CVE-2024-6519 | A use-after-free vulnerability was found in the QEMU LSI53C895A SCSI Host Bus Adapter emulation. This issue can lead to a crash or VM escape. | High 8.2 | 21 Oct 2024 |
| CVE-2024-8354 | A flaw was found in QEMU. An assertion failure was present in the usb_ep_get() function in hw/net/core.c when trying to get the USB endpoint from a USB device. This flaw may allow a malicious unprivileged guest user to crash the QEMU process on the host and cause a denial of service condition. | Medium 5.5 | 19 Sep 2024 |
| CVE-2024-6505 | A flaw was found in the virtio-net device in QEMU. When enabling the RSS feature on the virtio-net network card, the indirections_table data within RSS becomes controllable. Setting excessively large values may cause an index out-of-bounds issue, potentially resulting in heap overflow access. This flaw allows a privileged user in the guest to crash the QEMU process on the host. | Medium 6.8 | 5 Jul 2024 |
| CVE-2024-3567 | A flaw was found in QEMU. An assertion failure was present in the update_sctp_checksum() function in hw/net/net_tx_pkt.c when trying to calculate the checksum of a short-sized fragmented packet. This flaw allows a malicious guest to crash QEMU and cause a denial of service condition. | Medium 5.5 | 10 Apr 2024 |
| CVE-2024-24474 | QEMU before 8.2.0 has an integer underflow, and resultant buffer overflow, via a TI command when an expected non-DMA transfer length is less than the length of the available FIFO data. This occurs in esp_do_nodma in hw/scsi/esp.c because of an underflow of async_len. | High 8.8 | 20 Feb 2024 |
| CVE-2024-26328 | An issue was discovered in QEMU 7.1.0 through 8.2.1. register_vfs in hw/pci/pcie_sriov.c does not set NumVFs to PCI_SRIOV_TOTAL_VF, and thus interaction with hw/nvme/ctrl.c is mishandled. | Medium 6.0 | 19 Feb 2024 |
| CVE-2024-26327 | An issue was discovered in QEMU 7.1.0 through 8.2.1. register_vfs in hw/pci/pcie_sriov.c mishandles the situation where a guest writes NumVFs greater than TotalVFs, leading to a buffer overflow in VF implementations. | Medium 5.3 | 19 Feb 2024 |
| CVE-2023-6683 | A flaw was found in the QEMU built-in VNC server while processing ClientCutText messages. The qemu_clipboard_request() function can be reached before vnc_server_cut_text_caps() was called and had the chance to initialize the clipboard peer, leading to a NULL pointer dereference. This could allow a malicious authenticated VNC client to crash QEMU and trigger a denial of service. | Medium 6.5 | 12 Jan 2024 |
| CVE-2023-6693 | A stack based buffer overflow was found in the virtio-net device of QEMU. This issue occurs when flushing TX in the virtio_net_flush_tx function if guest features VIRTIO_NET_F_HASH_REPORT, VIRTIO_F_VERSION_1 and VIRTIO_NET_F_MRG_RXBUF are enabled. This could allow a malicious user to overwrite local variables allocated on the stack. Specifically, the `out_sg` variable could be used to read a part | Medium 4.9 | 2 Jan 2024 |
| CVE-2023-2861 | A flaw was found in the 9p passthrough filesystem (9pfs) implementation in QEMU. The 9pfs server did not prohibit opening special files on the host side, potentially allowing a malicious client to escape from the exported 9p tree by creating and opening a device file in the shared folder. | Medium 6.0 | 6 Dec 2023 |
| CVE-2023-5088 | A bug in QEMU could cause a guest I/O operation otherwise addressed to an arbitrary disk offset to be targeted to offset 0 instead (potentially overwriting the VM's boot code). This could be used, for example, by L2 guests with a virtual disk (vdiskL2) stored on a virtual disk of an L1 (vdiskL1) hypervisor to read and/or write data to LBA 0 of vdiskL1, potentially gaining control of L1 at its next | Medium 6.4 | 3 Nov 2023 |
| CVE-2023-2680 | This CVE exists because of an incomplete fix for CVE-2021-3750. More specifically, the qemu-kvm package as released for Red Hat Enterprise Linux 9.1 via RHSA-2022:7967 included a version of qemu-kvm that was actually missing the fix for CVE-2021-3750. | High 7.5 | 13 Sep 2023 |
| CVE-2023-3255 | A flaw was found in the QEMU built-in VNC server while processing ClientCutText messages. A wrong exit condition may lead to an infinite loop when inflating an attacker controlled zlib buffer in the `inflate_buffer` function. This could allow a remote authenticated client who is able to send a clipboard to the VNC server to trigger a denial of service. | Medium 6.5 | 13 Sep 2023 |
| CVE-2023-3301 | A flaw was found in QEMU. The async nature of hot-unplug enables a race scenario where the net device backend is cleared before the virtio-net pci frontend has been unplugged. A malicious guest could use this time window to trigger an assertion and cause a denial of service. | Medium 5.6 | 13 Sep 2023 |
| CVE-2023-42467 | QEMU through 8.0.0 could trigger a division by zero in scsi_disk_reset in hw/scsi/scsi-disk.c because scsi_disk_emulate_mode_select does not prevent s->qdev.blocksize from being 256. This stops QEMU and the guest immediately. | Medium 5.5 | 11 Sep 2023 |
| CVE-2020-24165 | An issue was discovered in TCG Accelerator in QEMU 4.2.0, allows local attackers to execute arbitrary code, escalate privileges, and cause a denial of service (DoS). Note: This is disputed as a bug and not a valid security issue by multiple third parties. | High 8.8 | 28 Aug 2023 |
| CVE-2022-36648 | The hardware emulation in the of_dpa_cmd_add_l2_flood of rocker device model in QEMU, as used in 7.0.0 and earlier, allows remote attackers to crash the host qemu and potentially execute code on the host via execute a malformed program in the guest OS. Note: This has been disputed by multiple third parties as not a valid vulnerability due to the rocker device not falling within the virtualization | Critical 10.0 | 22 Aug 2023 |
| CVE-2023-40360 | QEMU through 8.0.4 accesses a NULL pointer in nvme_directive_receive in hw/nvme/ctrl.c because there is no check for whether an endurance group is configured before checking whether Flexible Data Placement is enabled. | Medium 5.5 | 14 Aug 2023 |
| CVE-2023-4135 | A heap out-of-bounds memory read flaw was found in the virtual nvme device in QEMU. The QEMU process does not validate an offset provided by the guest before computing a host heap pointer, which is used for copying data back to the guest. Arbitrary heap memory relative to an allocated buffer can be disclosed. | Medium 6.0 | 4 Aug 2023 |
| CVE-2023-3180 | A flaw was found in the QEMU virtual crypto device while handling data encryption/decryption requests in virtio_crypto_handle_sym_req. There is no check for the value of `src_len` and `dst_len` in virtio_crypto_sym_op_helper, potentially leading to a heap buffer overflow when the two values differ. | Medium 6.0 | 3 Aug 2023 |
| CVE-2023-3019 | A DMA reentrancy issue leading to a use-after-free error was found in the e1000e NIC emulation code in QEMU. This issue could allow a privileged guest user to crash the QEMU process on the host, resulting in a denial of service. | Medium 6.0 | 24 Jul 2023 |
| CVE-2023-1386 | A flaw was found in the 9p passthrough filesystem (9pfs) implementation in QEMU. When a local user in the guest writes an executable file with SUID or SGID, none of these privileged bits are correctly dropped. As a result, in rare circumstances, this flaw could be used by malicious users in the guest to elevate their privileges within the guest and help a host local user to elevate privileges on t | Low 3.3 | 24 Jul 2023 |
| CVE-2023-3354 | A flaw was found in the QEMU built-in VNC server. When a client connects to the VNC server, QEMU checks whether the current number of connections crosses a certain threshold and if so, cleans up the previous connection. If the previous connection happens to be in the handshake phase and fails, QEMU cleans up the connection again, resulting in a NULL pointer dereference issue. This could allow a re | High 7.5 | 11 Jul 2023 |
| CVE-2023-0664 | A flaw was found in the QEMU Guest Agent service for Windows. A local unprivileged user may be able to manipulate the QEMU Guest Agent's Windows installer via repair custom actions to elevate their privileges on the system. | High 7.8 | 29 Mar 2023 |
| CVE-2023-1544 | A flaw was found in the QEMU implementation of VMWare's paravirtual RDMA device. This flaw allows a crafted guest driver to allocate and initialize a huge number of page tables to be used as a ring of descriptors for CQ and async events, potentially leading to an out-of-bounds read and crash of QEMU. | Medium 6.0 | 23 Mar 2023 |
| CVE-2023-0330 | A vulnerability in the lsi53c895a device affects the latest version of qemu. A DMA-MMIO reentrancy problem may lead to memory corruption bugs like stack overflow or use-after-free. | Medium 5.3 | 6 Mar 2023 |
| CVE-2022-4144 | An out-of-bounds read flaw was found in the QXL display device emulation in QEMU. The qxl_phys2virt() function does not check the size of the structure pointed to by the guest physical address, potentially reading past the end of the bar space into adjacent pages. A malicious guest user could use this flaw to crash the QEMU process on the host causing a denial of service condition. | Medium 6.5 | 29 Nov 2022 |
| CVE-2022-4172 | An integer overflow and buffer overflow issues were found in the ACPI Error Record Serialization Table (ERST) device of QEMU in the read_erst_record() and write_erst_record() functions. Both issues may allow the guest to overrun the host buffer allocated for the ERST memory device. A malicious guest could use these flaws to crash the QEMU process on the host. | Medium 6.5 | 29 Nov 2022 |
| CVE-2022-3872 | An off-by-one read/write issue was found in the SDHCI device of QEMU. It occurs when reading/writing the Buffer Data Port Register in sdhci_read_dataport and sdhci_write_dataport, respectively, if data_count == block_size. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition. | High 8.6 | 7 Nov 2022 |
| CVE-2022-3165 | An integer underflow issue was found in the QEMU VNC server while processing ClientCutText messages in the extended format. A malicious client could use this flaw to make QEMU unresponsive by sending a specially crafted payload message, resulting in a denial of service. | Medium 6.5 | 17 Oct 2022 |
| CVE-2014-0144 | QEMU before 2.0.0 block drivers for CLOOP, QCOW2 version 2 and various other image formats are vulnerable to potential memory corruptions, integer/buffer overflows or crash caused by missing input validations which could allow a remote user to execute arbitrary code on the host with the privileges of the QEMU process. | High 8.6 | 29 Sep 2022 |
| CVE-2014-0147 | Qemu before 1.6.2 block diver for the various disk image formats used by Bochs and for the QCOW version 2 format, are vulnerable to a possible crash caused by signed data types or a logic error while creating QCOW2 snapshots, which leads to incorrectly calling update_refcount() routine. | Medium 6.2 | 29 Sep 2022 |
| CVE-2014-0148 | Qemu before 2.0 block driver for Hyper-V VHDX Images is vulnerable to infinite loops and other potential issues when calculating BAT entries, due to missing bounds checks for block_size and logical_sector_size variables. These are used to derive other fields like 'sectors_per_block' etc. A user able to alter the Qemu disk image could ise this flaw to crash the Qemu instance resulting in DoS. | Medium 5.5 | 29 Sep 2022 |
| CVE-2022-2962 | A DMA reentrancy issue was found in the Tulip device emulation in QEMU. When Tulip reads or writes to the rx/tx descriptor or copies the rx/tx frame, it doesn't check whether the destination address is its own MMIO address. This can cause the device to trigger MMIO handlers multiple times, possibly leading to a stack or heap overflow. A malicious guest could use this flaw to crash the QEMU process | High 7.8 | 13 Sep 2022 |
| CVE-2022-0358 | A flaw was found in the QEMU virtio-fs shared file system daemon (virtiofsd) implementation. This flaw is strictly related to CVE-2018-13405. A local guest user can create files in the directories shared by virtio-fs with unintended group ownership in a scenario where a directory is SGID to a certain group and is writable by a user who is not a member of the group. This could allow a malicious unp | High 7.8 | 29 Aug 2022 |
| CVE-2022-0216 | A use-after-free vulnerability was found in the LSI53C895A SCSI Host Bus Adapter emulation of QEMU. The flaw occurs while processing repeated messages to cancel the current SCSI request via the lsi_do_msgout function. This flaw allows a malicious privileged user within the guest to crash the QEMU process on the host, resulting in a denial of service. | Medium 4.4 | 26 Aug 2022 |
| CVE-2021-3735 | A deadlock issue was found in the AHCI controller device of QEMU. It occurs on a software reset (ahci_reset_port) while handling a host-to-device Register FIS (Frame Information Structure) packet from the guest. A privileged user inside the guest could use this flaw to hang the QEMU process on the host, resulting in a denial of service condition. The highest threat from this vulnerability is to sy | Medium 4.4 | 26 Aug 2022 |
| CVE-2021-3929 | A DMA reentrancy issue was found in the NVM Express Controller (NVME) emulation in QEMU. This CVE is similar to CVE-2021-3750 and, just like it, when the reentrancy write triggers the reset function nvme_ctrl_reset(), data structs will be freed leading to a use-after-free issue. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition | High 8.2 | 25 Aug 2022 |
| CVE-2021-4158 | A NULL pointer dereference issue was found in the ACPI code of QEMU. A malicious, privileged user within the guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition. | Medium 6.0 | 24 Aug 2022 |
| CVE-2020-14394 | An infinite loop flaw was found in the USB xHCI controller emulation of QEMU while computing the length of the Transfer Request Block (TRB) Ring. This flaw allows a privileged guest user to hang the QEMU process on the host, resulting in a denial of service. | Low 3.2 | 17 Aug 2022 |
| CVE-2022-35414 | softmmu/physmem.c in QEMU through 7.0.0 can perform an uninitialized read on the translate_fail path, leading to an io_readx or io_writex crash. NOTE: a third party states that the Non-virtualization Use Case in the qemu.org reference applies here, i.e., "Bugs affecting the non-virtualization use case are not considered security bugs at this time. | High 8.8 | 11 Jul 2022 |
| CVE-2021-3611 | A stack overflow vulnerability was found in the Intel HD Audio device (intel-hda) of QEMU. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition. The highest threat from this vulnerability is to system availability. This flaw affects QEMU versions prior to 7.0.0. | Medium 6.5 | 11 May 2022 |
| CVE-2021-3750 | A DMA reentrancy issue was found in the USB EHCI controller emulation of QEMU. EHCI does not verify if the Buffer Pointer overlaps with its MMIO region when it transfers the USB packets. Crafted content may be written to the controller's registers and trigger undesirable actions (such as reset) while the device is still transferring packets. This can ultimately lead to a use-after-free issue. A ma | High 8.2 | 2 May 2022 |
| CVE-2021-4206 | A flaw was found in the QXL display device emulation in QEMU. An integer overflow in the cursor_alloc() function can lead to the allocation of a small cursor object followed by a subsequent heap-based buffer overflow. This flaw allows a malicious privileged guest user to crash the QEMU process on the host or potentially execute arbitrary code within the context of the QEMU process. | High 8.2 | 29 Apr 2022 |
| CVE-2021-4207 | A flaw was found in the QXL display device emulation in QEMU. A double fetch of guest controlled values `cursor->header.width` and `cursor->header.height` can lead to the allocation of a small cursor object followed by a subsequent heap-based buffer overflow. A malicious privileged guest user could use this flaw to crash the QEMU process on the host or potentially execute arbitrary code within the | High 8.2 | 29 Apr 2022 |
| CVE-2021-20295 | It was discovered that the update for the virt:rhel module in the RHSA-2020:4676 (https://access.redhat.com/errata/RHSA-2020:4676) erratum released as part of Red Hat Enterprise Linux 8.3 failed to include the fix for the qemu-kvm component issue CVE-2020-10756, which was previously corrected in virt:rhel/qemu-kvm via erratum RHSA-2020:4059 (https://access.redhat.com/errata/RHSA-2020:4059). CVE-20 | Medium 6.5 | 1 Apr 2022 |
| CVE-2022-1050 | A flaw was found in the QEMU implementation of VMWare's paravirtual RDMA device. This flaw allows a crafted guest driver to execute HW commands when shared buffers are not yet allocated, potentially leading to a use-after-free condition. | High 8.8 | 29 Mar 2022 |
| CVE-2021-3582 | A flaw was found in the QEMU implementation of VMWare's paravirtual RDMA device. The issue occurs while handling a "PVRDMA_CMD_CREATE_MR" command due to improper memory remapping (mremap). This flaw allows a malicious guest to crash the QEMU process on the host. The highest threat from this vulnerability is to system availability. | Medium 6.5 | 25 Mar 2022 |
| CVE-2021-3748 | A use-after-free vulnerability was found in the virtio-net device of QEMU. It could occur when the descriptor's address belongs to the non direct access region, due to num_buffers being set after the virtqueue elem has been unmapped. A malicious guest could use this flaw to crash QEMU, resulting in a denial of service condition, or potentially execute code on the host with the privileges of the QE | High 7.5 | 23 Mar 2022 |
| CVE-2022-26353 | A flaw was found in the virtio-net device of QEMU. This flaw was inadvertently introduced with the fix for CVE-2021-3748, which forgot to unmap the cached virtqueue elements on error, leading to memory leakage and other unexpected results. Affected QEMU version: 6.2.0. | High 7.5 | 16 Mar 2022 |
| CVE-2022-26354 | A flaw was found in the vhost-vsock device of QEMU. In case of error, an invalid element was not detached from the virtqueue before freeing its memory, leading to memory leakage and other unexpected results. Affected QEMU versions <= 6.2.0. | Low 3.2 | 16 Mar 2022 |
| CVE-2021-20257 | An infinite loop flaw was found in the e1000 NIC emulator of the QEMU. This issue occurs while processing transmits (tx) descriptors in process_tx_desc if various descriptor fields are initialized with invalid values. This flaw allows a guest to consume CPU cycles on the host, resulting in a denial of service. The highest threat from this vulnerability is to system availability. | Medium 6.5 | 16 Mar 2022 |
| CVE-2021-3638 | An out-of-bounds memory access flaw was found in the ATI VGA device emulation of QEMU. This flaw occurs in the ati_2d_blt() routine while handling MMIO write operations when the guest provides invalid values for the destination display parameters. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service. | Medium 6.5 | 3 Mar 2022 |
| CVE-2021-3607 | An integer overflow was found in the QEMU implementation of VMWare's paravirtual RDMA device in versions prior to 6.1.0. The issue occurs while handling a "PVRDMA_REG_DSRHIGH" write from the guest due to improper input validation. This flaw allows a privileged guest user to make QEMU allocate a large amount of memory, resulting in a denial of service. The highest threat from this vulnerability is | Medium 6.0 | 24 Feb 2022 |
| CVE-2021-3608 | A flaw was found in the QEMU implementation of VMWare's paravirtual RDMA device in versions prior to 6.1.0. The issue occurs while handling a "PVRDMA_REG_DSRHIGH" write from the guest and may result in a crash of QEMU or cause undefined behavior due to the access of an uninitialized pointer. The highest threat from this vulnerability is to system availability. | Medium 6.0 | 24 Feb 2022 |
| CVE-2021-3947 | A stack-buffer-overflow was found in QEMU in the NVME component. The flaw lies in nvme_changed_nslist() where a malicious guest controlling certain input can read out of bounds memory. A malicious user could use this flaw leading to disclosure of sensitive information. | Medium 5.5 | 18 Feb 2022 |
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 343 Last 12 months Memory safety 45 % Denial of service 25 % Privilege escalation 20 % Info disclosure 10 % Latest advisories Loading the feed Overview QEMU is the emulation and virtualization layer under nearly all of Linux virtualization. It sits beneath KVM in libvirt, Proxmox, oVirt and OpenStack, runs the Android emulator, and is what makes multi-architecture container builds work in CI. Its device models parse data a guest controls, so a bug in the network, USB, SCSI or display emulation is a route from inside a virtual machine onto the host running it. QEMU carries by far the heaviest CVE traffic of anything in this toolchain category. The project runs no bounty and takes reports as confidential GitLab issues, so sorona.xyz pays you directly on qualified, reproduced findings. In scope QEMU's security process splits by use case rather than by component. The virtualization use case is what it triages: a guest that should not be able to reach the host, and a host that should not be exposed by running one. Everything below sits inside that framing The whole system-mode device model set: network, block, SCSI, USB, display, audio, character and input devices, emulated and paravirtualised alike virtio in full, including the shared-memory ring handling that every modern guest drives The block layer and every disk image format QEMU parses, since an image file is frequently supplied by somebody other than the operator Live migration, including the state one host deserialises from another The QMP and HMP monitor interfaces and anything a management layer drives through them TCG, the translation engine, where guest instruction sequences become host code The host-facing services QEMU exposes: NBD, VNC, SPICE and the character device backends Device passthrough and the IOMMU-facing paths, including vhost and vhost-user backends The firmware and boot interfaces QEMU presents to a guest, which a guest can drive from its first instruction Out of scope The non-virtualization use case, which the process states is generally ineligible. Reports there are converted into public bugs qemu-user emulation, which is the non-virtualization case in practice and therefore the weakest part of this scope Guest-visible crashes and misbehaviour that stay inside the guest without reaching the host or another tenant Operator configuration decisions, including deliberately exposing a monitor socket or a VNC server with no authentication The host kernel, KVM itself and the management stack around QEMU, all of which belong to their own projects Findings that depend on a long embargo, since the process refuses arbitrary embargo requests Most-valued findings Guest-to-host escape out of a device model. This is the class the security process exists for and where QEMU's CVE volume concentrates, in network, USB, SCSI and display emulation Memory corruption in virtio or in the block layer reachable from data a guest writes into a shared ring or an image file Host memory disclosure into a guest, which on shared infrastructure crosses a tenant boundary rather than only a process boundary Migration state deserialisation defects, where one host acts on a structure another host produced Anything reachable through NBD, VNC or SPICE from the network rather than only from a guest Denial of service that takes down the host or the other guests on it, as opposed to only the guest that caused it 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. File a GitLab work item on the QEMU project and mark it confidential before you submit. The process is explicit about that order Email disclosure is no longer accepted. There is no security address to write to Frame the finding as the virtualization use case. Reports outside it are generally ineligible and get reopened as ordinary public bugs qemu-user is the weak part of this scope. A user-mode emulation finding is likely to be handled as an ordinary bug however real it is Expect a short embargo. The project holds confidentiality only as long as it takes to build a patch and allocate a CVE, and generally refuses arbitrary embargo requests Low-severity issues may be published with no patch available, so do not plan a coordinated release around one No response time is published and the project pays nothing for a report Disclosure Coordinated through a confidential GitLab work item. QEMU runs a deliberately minimal embargo, holding confidentiality only as long as it takes to develop a patch and allocate a CVE, and it declines arbitrary embargo requests. Low-severity issues can be disclosed publicly with no patch available. No response time is published, so treat the timeline as the project's call rather than yours. 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