← Search results
CVE-LINKED INVENTORY60 SECURITY RECORDS
Publisher not identified
Qemu
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at qemu, but registry activity is not a publisher support boundary.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2023-2680 | 13 Sep 2023 | See the vendor and CVE records for the affected range. | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-3301 | 13 Sep 2023 | See the vendor and CVE records for the affected range. | 8.1.0-rc0 | Update reference ↗ |
| CVE-2023-3180 | 3 Aug 2023 | See the vendor and CVE records for the affected range. | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2023-1386 | 24 Jul 2023 | See the vendor and CVE records for the affected range. | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-3354 | 11 Jul 2023 | See the vendor and CVE records for the affected range. | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2023-0664 | 29 Mar 2023 | unknown | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-3872 | 7 Nov 2022 | Affected: up to latest v7.1.0-rc4 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-3165 | 17 Oct 2022 | Affected 6.1.0 and later. Will be fixed in 7.2.0-rc0. | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-2962 | 13 Sep 2022 | Will be fixed in QEMU 7.2.0-rc0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-3735 | 26 Aug 2022 | Not Known | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-0216 | 26 Aug 2022 | Affects QEMU < v6.0.0, Fixed in v7.1.0-rc0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-3929 | 25 Aug 2022 | Fixed in qemu-kvm 7.0.0-rc0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-4158 | 24 Aug 2022 | Affects v6.0.0 and above. | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-14394 | 17 Aug 2022 | QEMU 6.1.50 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-3611 | 11 May 2022 | QEMU versions prior to 7.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2021-3750 | 2 May 2022 | QEMU before version 7.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-4206 | 29 Apr 2022 | qemu-kvm 7.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-4207 | 29 Apr 2022 | qemu-kvm 7.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-20295 | 1 Apr 2022 | qemu-kvm 4.2.0-34 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-1050 | 29 Mar 2022 | qemu 2.20.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-3582 | 25 Mar 2022 | qemu 2.17.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-20257 | 16 Mar 2022 | Fixed-In v6.2.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-3638 | 3 Mar 2022 | Affects qemu v4.0 to v6.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-3608 | 24 Feb 2022 | qemu-kvm 6.1.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-3607 | 24 Feb 2022 | qemu-kvm 6.1.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-3947 | 18 Feb 2022 | qemu-kvm 6.2.0-rc2 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-3930 | 18 Feb 2022 | qemu-kvm 6.2.0-rc0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-4145 | 25 Jan 2022 | qemu-kvm 6.2.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-3713 | 25 Aug 2021 | qemu 6.2.0-rc0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-3682 | 5 Aug 2021 | qemu 6.1.0-rc2 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-3595 | 15 Jun 2021 | libslirp 4.6.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-3594 | 15 Jun 2021 | libslirp 4.6.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-3593 | 15 Jun 2021 | libslirp 4.6.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-3592 | 15 Jun 2021 | libslirp 4.6.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-3546 | 2 Jun 2021 | All QEMU versions up to and including 6.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-3545 | 2 Jun 2021 | All QEMU versions up to and including 6.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-3544 | 2 Jun 2021 | All QEMU versions up to and including 6.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-35503 | 2 Jun 2021 | All QEMU versions before and including 6.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2013-4536 | 28 May 2021 | qemu-kvm 1.5.3 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-35506 | 28 May 2021 | qemu 6.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-35505 | 28 May 2021 | qemu 6.0.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-35504 | 28 May 2021 | qemu 6.0.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-20196 | 26 May 2021 | vulnerable up to (including) qemu 5.2.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-3527 | 26 May 2021 | all versions | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-20221 | 13 May 2021 | up to, including qemu 4.2.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-20181 | 13 May 2021 | up to, including 5.2.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-3507 | 6 May 2021 | up to 6.0.0 (including) | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-3409 | 23 Mar 2021 | up to (including) 5.2.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-3392 | 23 Mar 2021 | between 2.10.0 and 5.2.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-3416 | 18 Mar 2021 | versions up to and including 5.2.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.