Vulnerability Database

346,508

Total vulnerabilities in the database

Vulnerabilities for products matching "qemu"

Found 2 matching products. Filters apply to all results.

You can search for specific versions with /product/qemu/1.2.3

qemu / qemu

2821 vulnerabilities found
Title Severity Exploit Date Affected Version
Medium November 4, 2016 11/4/16
<= 2.7.1
Medium November 4, 2016 11/4/16
<= 2.7.1
Low October 10, 2016 10/10/16
<= 2.7.1
Low October 5, 2016 10/5/16
<= 2.7.1
Low October 5, 2016 10/5/16
<= 2.7.1
Low October 5, 2016 10/5/16
<= 2.8.1.1
== 2.9.0-rc1
== 2.9.0-rc2
== 2.9.0-rc3
== 2.9.0-rc0
== 2.9.0-rc4
== 2.9.0-rc5
Critical October 5, 2016 10/5/16
== 2.7.0-rc0
<= 2.6.2
== 2.7.0-rc1
== 2.7.0-rc2
Medium September 7, 2016 9/7/16
<= 2.6.2
Medium September 2, 2016 9/2/16
<= 2.6.2
Medium September 2, 2016 9/2/16
<= 2.6.2
Low September 2, 2016 9/2/16
<= 2.6.2
Medium September 2, 2016 9/2/16
<= 2.6.2
Medium August 2, 2016 8/2/16
<= 2.6.0
== 2.7.0-rc0
Low June 16, 2016 6/16/16
<= 2.5.0
Low June 16, 2016 6/16/16
<= 2.5.0
Low June 16, 2016 6/16/16
== 2.5.0
Medium June 16, 2016 6/16/16
<= 2.5.1.1
High June 14, 2016 6/14/16
<= 2.6.2
Medium June 14, 2016 6/14/16
<= 2.6.2
Low June 14, 2016 6/14/16
<= 2.6.2
High June 1, 2016 6/1/16
<= 2.6.2
Medium June 1, 2016 6/1/16
<= 2.6.0
Low June 1, 2016 6/1/16
<= 2.6.0
Medium May 25, 2016 5/25/16
<= 2.6.2
Medium May 23, 2016 5/23/16
<= 2.5.1
== 2.6.0-rc1
== 2.6.0-rc2
== 2.6.0-rc0
High May 23, 2016 5/23/16
== 2.6.0-rc1
== 2.6.0-rc0
<= 2.5.1.1
Medium May 23, 2016 5/23/16
<= 2.5.1.1
Medium May 20, 2016 5/20/16
<= 2.6.0
Medium May 20, 2016 5/20/16
<= 2.6.0
Medium May 11, 2016 5/11/16
<= 2.5.1
== 2.6.0-rc1
== 2.6.0-rc2
== 2.6.0-rc3
== 2.6.0-rc4
== 2.6.0-rc0
High May 11, 2016 5/11/16
<= 2.5.1
== 2.6.0-rc1
== 2.6.0-rc2
== 2.6.0-rc3
== 2.6.0-rc4
== 2.6.0-rc0
Critical April 26, 2016 4/26/16
<= 2.6.2
High April 12, 2016 4/12/16
<= 2.5.1.1
High April 12, 2016 4/12/16
<= 2.5.1.1
Medium April 12, 2016 4/12/16
== 2.4.0-rc1
== 2.4.0-rc2
>= 2.2.0 < 2.4.0
== 2.4.0
Medium April 7, 2016 4/7/16
<= 2.5.1.1
Medium April 7, 2016 4/7/16
<= 2.3.0
High January 12, 2016 1/12/16
== 2.3.0-rc1
<= 2.2.1
== 2.3.0-rc0
Critical January 8, 2016 1/8/16
<= 2.4.1
== 2.5.0-rc1
== 2.5.0-rc2
== 2.5.0-rc0
Medium November 9, 2015 11/9/15
<= 2.4.1
High November 6, 2015 11/6/15
<= 2.4.1
High November 6, 2015 11/6/15
<= 2.4.0
High September 28, 2015 9/28/15
<= 2.4.0
Medium August 31, 2015 8/31/15
<= 2.3.0
Low August 26, 2015 8/26/15
<= 2.3.0
High August 12, 2015 8/12/15
<= 2.3.0
High June 15, 2015 6/15/15
<= 2.3.1
Low June 3, 2015 6/3/15
<= 2.3.1
High May 13, 2015 5/13/15
<= 2.3.0
Low April 21, 2015 4/21/15
== 1.0-rc1
== 2.0.0
== 2.0.2
== 1.1-rc3
== 2.1.3
== 2.1.0-rc2
== 1.6.0
== 1.5.0-rc1
== 1.0-rc2
== 1.5.3
== 1.5.0
== 1.6.0-rc3
== 1.5.1
== 1.1-rc4
== 1.5.0-rc3
== 1.0
== 1.1-rc2
== 2.0.0-rc0
== 2.1.0
== 2.1.1
== 1.5.2
== 1.0.1
== 1.0-rc3
== 2.0.0-rc1
== 1.5.0-rc2
== 2.1.0-rc3
== 2.1.0-rc1
== 1.7.1
== 1.4.1
== 1.6.0-rc2
== 1.4.2
== 1.6.2
== 1.6.0-rc1
== 1.6.1
== 2.1.0-rc5
== 2.0.0-rc2
== 2.1.0-rc0
== 2.1.2
== 1.0-rc4
== 2.0.0-rc3
== 1.1-rc1
== 1.1

Showing vulnerabilities for 2 products matching "qemu". Each product has independent pagination.

Frequently Asked Questions

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.