Vulnerability Database · OSS-Fuzz · Package report

qemu: vulnerability history, versions and safety

qemu is a package in the OSS-Fuzz ecosystem. Vulert records 15 vulnerabilities for it across 120 releases, from Oct 2020 to May 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
15 vulnerabilities recorded H4 M7 U4
i
4 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on qemu i

Updated on 23 Oct 2026

Careful: 4 of the 15 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 15 vulnerabilities on record across 2 years, none in the last year.

What to do: Plan around the 4 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 15 over 2 years · 0 in the last year i
  • Latest disclosure 12 May 2023 i
  • Highest CVSS n/a i
  • With no published fix 4 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for qemu, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
v10.1.0-rc0 M3 No Details →
v10.0.3 M3 No Details →
v10.0.2 M3 No Details →
v10.0.1 M3 No Details →
v10.0.0 M3 No Details →
v10.0.0-rc4 M3 No Details →
v10.0.0-rc3 M3 No Details →
v10.0.0-rc2 M3 No Details →
v10.0.0-rc1 M3 No Details →
v10.0.0-rc0 M3 No Details →
v9.2.4 M3 No Details →
v9.2.3 M3 No Details →
v9.2.2 M3 No Details →
v9.2.1 M3 No Details →
v9.2.0 M3 No Details →
v9.2.0-rc3 M3 No Details →
v9.2.0-rc2 M3 No Details →
v9.2.0-rc1 M3 No Details →
v9.2.0-rc0 M3 No Details →
v9.1.3 M3 No Details →
v9.1.2 M3 No Details →
v9.1.1 M3 No Details →
v9.1.0 M3 No Details →
v9.1.0-rc4 M3 No Details →
v9.1.0-rc3 M3 No Details →
v9.1.0-rc2 M3 No Details →
v9.1.0-rc1 M3 No Details →
v9.1.0-rc0 M3 No Details →
v9.0.4 M3 No Details →
v9.0.3 M3 No Details →
v9.0.2 M3 No Details →
v9.0.1 M3 No Details →
v9.0.0 M3 No Details →
v9.0.0-rc4 M3 No Details →
v9.0.0-rc3 M3 No Details →
v9.0.0-rc2 M3 No Details →
v9.0.0-rc1 M3 No Details →
v9.0.0-rc0 M3 No Details →
v8.2.10 M3 No Details →
v8.2.9 M3 No Details →
v8.2.8 M3 No Details →
v8.2.7 M3 No Details →
v8.2.6 M3 No Details →
v8.2.5 M3 No Details →
v8.2.4 M3 No Details →
v8.2.3 M3 No Details →
v8.2.2 M3 No Details →
v8.2.1 M3 No Details →
v8.2.0 M3 No Details →
v8.2.0-rc4 M3 No Details →
v8.2.0-rc3 M3 No Details →
v8.2.0-rc2 M3 No Details →
v8.2.0-rc1 M3 No Details →
v8.2.0-rc0 M3 No Details →
v8.1.5 M3 No Details →
v8.1.4 M3 No Details →
v8.1.3 M3 No Details →
v8.1.2 M3 No Details →
v8.1.1 M3 No Details →
v8.1.0 M3 No Details →
v8.1.0-rc4 M3 No Details →
v8.1.0-rc3 M3 No Details →
v8.1.0-rc2 M3 No Details →
v8.1.0-rc1 M3 No Details →
v8.1.0-rc0 M3 No Details →
v8.0.5 M3 No Details →
v8.0.4 M3 No Details →
v8.0.3 M3 No Details →
v8.0.2 H1 M3 No Details →
v8.0.1 H1 M3 No Details →
v8.0.0 H1 M3 No Details →
v8.0.0-rc4 H1 M3 No Details →
v8.0.0-rc3 H1 M3 No Details →
v8.0.0-rc2 H1 M3 No Details →
v8.0.0-rc1 H1 M3 No Details →
v8.0.0-rc0 H1 M3 No Details →
v7.2.19 M3 No Details →
v7.2.18 M3 No Details →
v7.2.17 M3 No Details →
v7.2.16 M3 No Details →
v7.2.15 M3 No Details →
v7.2.14 M3 No Details →
v7.2.13 M3 No Details →
v7.2.12 M3 No Details →
v7.2.11 M3 No Details →
v7.2.10 M3 No Details →
v7.2.9 M3 No Details →
v7.2.8 M3 No Details →
v7.2.7 M3 No Details →
v7.2.6 M3 No Details →
v7.2.5 M3 No Details →
v7.2.4 M3 No Details →
v7.2.3 M3 No Details →
v7.2.2 M3 No Details →
v7.2.1 M3 No Details →
v7.2.0 M3 No Details →
v7.2.0-rc4 M3 No Details →
v7.2.0-rc3 M3 No Details →
v7.2.0-rc2 M3 No Details →
v7.2.0-rc1 M3 No Details →
v7.2.0-rc0 M4 No Details →
v7.1.0 M3 No Details →
v7.1.0-rc4 M3 No Details →
v7.1.0-rc3 M3 No Details →
v7.1.0-rc2 M3 No Details →
v7.1.0-rc1 M3 No Details →
v7.1.0-rc0 M3 No Details →
v7.0.0 M3 No Details →
v7.0.0-rc4 M3 No Details →
v7.0.0-rc3 M3 No Details →
v7.0.0-rc2 M3 No Details →
v7.0.0-rc1 M3 No Details →
v7.0.0-rc0 M2 No Details →
v6.2.0 M2 No Details →
v6.2.0-rc4 M2 No Details →
v6.2.0-rc3 M2 No Details →
v6.2.0-rc1 M2 No Details →
v6.2.0-rc0 M2 No Details →
v6.1.1 H1 M1 U1 No Details →
v6.1.0 H1 M1 U1 No Details →

Newest 120 of 138 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 3
  • 2021 7
  • 2022 3
  • 2023 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 15 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for qemu

The 5 most severe of 15 vulnerabilities recorded for this package

Search all 15 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-buffer-overflow in virtio_net_queue_enable in qemu N/A medium 6a4cff8e1a80bafc4b8fe2bfb10081f4880d1b3b 11 Nov 2022
Heap-buffer-overflow in ldl_he_p in qemu N/A medium d0dddab40e472ba62b5f43f11cc7dba085dabe71 04 Jan 2021
UNKNOWN READ vulnerability in qemu N/A medium No fix published 02 Jun 2021
Heap-buffer-overflow in megasas_map_sgl in qemu N/A medium No fix published 14 Jul 2022
Heap-use-after-free vulnerability in qemu N/A high 7efd65423ab22e6f5890ca08ae40c84d6660242f 24 Feb 2023

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About qemu

Is qemu safe to use?

Vulert records 15 vulnerabilities for qemu in OSS-Fuzz: 0 critical, 4 high, 7 medium and 0 low, plus 4 not yet rated. 4 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does qemu have?

15 vulnerabilities are recorded for qemu in the OSS-Fuzz ecosystem: 0 critical, 4 high, 7 medium and 0 low, plus 4 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new qemu vulnerabilities disclosed?

0 vulnerabilities were recorded for qemu in the last 12 months, and the oldest entry in this database dates to 29 Oct 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of qemu are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor qemu for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the qemu version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.