VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

qemu: vulnerability history, versions and safety

qemu is a package in the Debian ecosystem. Vulert records 17 vulnerabilities for it across 17 releases, from Jul 2017 to Apr 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
17 vulnerabilities recorded U17
i
0 with no fix published

Every vulnerability has a patched version to move to.

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.

See all qemu vulnerabilities

Vulert verdict on qemu i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 04 Apr 2022. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 17 vulnerabilities on record across 4 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 17 over 4 years · 0 in the last year i
  • Latest disclosure 04 Apr 2022 i
  • Highest CVSS n/a i
  • With no published fix 0 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.

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 3
  • 2018 2
  • 2019 3
  • 2020 4
  • 2021 4
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for qemu

The 5 most severe of 17 vulnerabilities recorded for this package

Search all 17 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
QEMU - Security Update N/A unrated 1:2.8+dfsg-6+deb9u11 13 Sep 2020
qemu - Security Update N/A unrated 1:2.8+dfsg-6+deb9u4 29 May 2018
QEMU Security Update - Multiple Vulnerabilities N/A unrated 1:2.8+dfsg-6+deb9u13 16 Feb 2021
Security Update for qemu in Debian 9 N/A unrated 1:2.8+dfsg-6+deb9u10 25 Jul 2020
QEMU - Multiple Vulnerabilities N/A unrated 1:2.8+dfsg-6+deb9u2 04 Aug 2017

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 17 vulnerabilities for qemu in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 17 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does qemu have?

17 vulnerabilities are recorded for qemu in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 17 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 25 Jul 2017. 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.