| CVE-2020-14364US | medium5.0 | 5.40% (93rd) | Exploit | ✗kein Fix | 2020-08-31 | ≤ QEMU versions before 5.2.0 |
| CVE-2021-3929US | high8.2 | 0.68% (52nd) | Exploit | ✗kein Fix | 2022-08-25 | ≤ Fixed in qemu-kvm 7.0.0-rc0 |
| CVE-2021-3682US | high8.5 | 2.88% (87th) | — | ✗kein Fix | 2021-08-05 | ≤ qemu 6.1.0-rc2 |
| CVE-2022-3165US | medium6.5 | 1.55% (75th) | — | ✗kein Fix | 2022-10-17 | ≤ Affected 6.1.0 and later. Will be fixed in 7.2.0-rc0. |
| CVE-2013-4535US | high8.8 | 0.96% (61st) | — | ✗kein Fix | 2020-02-11 | ≤ before 1.7.2 |
| CVE-2022-3872US | high8.6 | 0.91% (60th) | — | ✗kein Fix | 2022-11-07 | ≤ Affected: up to latest v7.1.0-rc4 |
| CVE-2021-4206US | high8.2 | 0.83% (57th) | — | ✗kein Fix | 2022-04-29 | ≤ qemu-kvm 7.0.0 |
| CVE-2021-20203US | low3.2 | 0.59% (48th) | — | ✗kein Fix | 2021-02-25 | ≤ versions up to v5.2.0 |
| CVE-2021-3713US | high7.4 | 0.57% (47th) | — | ✗kein Fix | 2021-08-25 | ≤ qemu 6.2.0-rc0 |
| CVE-2020-35517US | high8.2 | 0.53% (45th) | — | ✗kein Fix | 2021-01-28 | ≤ qemu 5.2.0 |
| CVE-2021-3750US | high8.2 | 0.51% (44th) | — | ✗kein Fix | 2022-05-02 | ≤ QEMU before version 7.0.0 |
| CVE-2021-3507US | medium6.1 | 0.49% (42nd) | — | ✗kein Fix | 2021-05-06 | ≤ up to 6.0.0 (including) |
| CVE-2021-3409US | medium5.7 | 0.49% (42nd) | — | ✗kein Fix | 2021-03-23 | ≤ up to (including) 5.2.0 |
| CVE-2021-20196US | medium6.5 | 0.48% (41st) | — | ✗kein Fix | 2021-05-26 | ≤ vulnerable up to (including) qemu 5.2.0 |
| CVE-2021-3546US | high8.2 | 0.46% (40th) | — | ✗kein Fix | 2021-06-02 | ≤ All QEMU versions up to and including 6.0 |
| CVE-2021-3611US | medium6.5 | 0.46% (40th) | — | ✗kein Fix | 2022-05-11 | ≤ QEMU versions prior to 7.0.0 |
| CVE-2021-3416US | medium6.0 | 0.46% (40th) | — | ✗kein Fix | 2021-03-18 | ≤ versions up to and including 5.2.0 |
| CVE-2021-3392US | low3.2 | 0.45% (39th) | — | ✗kein Fix | 2021-03-23 | ≤ between 2.10.0 and 5.2.0 |
| CVE-2021-3544US | medium6.5 | 0.44% (38th) | — | ✗kein Fix | 2021-06-02 | ≤ All QEMU versions up to and including 6.0 |
| CVE-2022-0216US | medium4.4 | 0.43% (37th) | — | ✓v6.0.0, Fixed in v7.1.0-rc0 | 2022-08-26 | Affects QEMU → v6.0.0, Fixed in v7.1.0-rc0 |
| CVE-2021-3638US | medium6.5 | 0.43% (37th) | — | ✗kein Fix | 2022-03-03 | ≤ Affects qemu v4.0 to v6.1 |
| CVE-2021-3545US | medium6.5 | 0.42% (36th) | — | ✗kein Fix | 2021-06-02 | ≤ All QEMU versions up to and including 6.0 |
| CVE-2021-20255US | medium5.5 | 0.41% (35th) | — | ✗kein Fix | 2021-03-09 | ≤ all versions |
| CVE-2021-4207US | high8.2 | 0.40% (34th) | — | ✗kein Fix | 2022-04-29 | ≤ qemu-kvm 7.0.0 |
| CVE-2022-2962US | high7.8 | 0.40% (34th) | — | ✗kein Fix | 2022-09-13 | ≤ Will be fixed in QEMU 7.2.0-rc0 |
| CVE-2021-4158US | medium6.0 | 0.40% (34th) | — | ✗kein Fix | 2022-08-24 | ≤ Affects v6.0.0 and above. |
| CVE-2020-14394US | low3.2 | 0.39% (33rd) | — | ✗kein Fix | 2022-08-17 | ≤ QEMU 6.1.50 |
| CVE-2021-4145US | medium6.5 | 0.39% (33rd) | — | ✗kein Fix | 2022-01-25 | ≤ qemu-kvm 6.2.0 |
| CVE-2021-3582US | medium6.5 | 0.39% (33rd) | — | ✗kein Fix | 2022-03-25 | ≤ qemu 2.17.2 |
| CVE-2022-1050US | high8.8 | 0.38% (32nd) | — | ✗kein Fix | 2022-03-29 | ≤ qemu 2.20.1 |
| CVE-2021-20263US | low3.3 | 0.38% (31st) | — | ✗kein Fix | 2021-03-09 | ≤ qemu 5.2.50 |
| CVE-2021-3527US | medium5.5 | 0.37% (31st) | — | ✗kein Fix | 2021-05-26 | ≤ all versions |
| CVE-2021-20257US | medium6.5 | 0.37% (31st) | — | ✗kein Fix | 2022-03-16 | ≤ Fixed-In v6.2.0 |
| CVE-2020-35506US | medium6.7 | 0.37% (30th) | — | ✗kein Fix | 2021-05-28 | ≤ qemu 6.0.0 |
| CVE-2020-25723US | low3.2 | 0.36% (30th) | — | ✗kein Fix | 2020-12-02 | ≤ qemu 5.2.0 |
| CVE-2020-27821US | medium6.0 | 0.36% (30th) | — | ✗kein Fix | 2020-12-08 | ≤ prior to 5.2.0 |
| CVE-2021-3608US | medium6.0 | 0.36% (30th) | — | ✗kein Fix | 2022-02-24 | ≤ qemu-kvm 6.1.0 |
| CVE-2021-3930US | medium6.5 | 0.34% (27th) | — | ✗kein Fix | 2022-02-18 | ≤ qemu-kvm 6.2.0-rc0 |
| CVE-2020-35504US | medium6.0 | 0.34% (27th) | — | ✗kein Fix | 2021-05-28 | ≤ qemu 6.0.0 |
| CVE-2021-20181US | high7.5 | 0.33% (26th) | — | ✗kein Fix | 2021-05-13 | ≤ up to, including 5.2.0 |
| CVE-2014-0147US | medium6.2 | 0.33% (26th) | — | ✗kein Fix | 2022-09-29 | ≤ before 1.6.2 |
| CVE-2021-20221US | medium6.0 | 0.33% (26th) | — | ✗kein Fix | 2021-05-13 | ≤ up to, including qemu 4.2.0 |
| CVE-2021-3595US | low3.8 | 0.33% (26th) | — | ✗kein Fix | 2021-06-15 | ≤ libslirp 4.6.0 |
| CVE-2021-3594US | low3.8 | 0.33% (26th) | — | ✗kein Fix | 2021-06-15 | ≤ libslirp 4.6.0 |
| CVE-2021-3593US | low3.8 | 0.33% (26th) | — | ✗kein Fix | 2021-06-15 | ≤ libslirp 4.6.0 |
| CVE-2021-3592US | low3.8 | 0.33% (26th) | — | ✗kein Fix | 2021-06-15 | ≤ libslirp 4.6.0 |
| CVE-2021-3947US | medium5.5 | 0.32% (24th) | — | ✗kein Fix | 2022-02-18 | ≤ qemu-kvm 6.2.0-rc2 |
| CVE-2020-35505US | medium4.4 | 0.32% (25th) | — | ✗kein Fix | 2021-05-28 | ≤ qemu 6.0.0 |
| CVE-2023-0664US | high7.8 | 0.31% (23rd) | — | ✗kein Fix | 2023-03-29 | ≤ unknown |
| CVE-2014-0148US | medium5.5 | 0.30% (23rd) | — | ✗kein Fix | 2022-09-29 | ≤ before 2.0 |