NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
523 matching advisories · page 1 of 18Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.8 CVE-2026-93834 A use-after-free vulnerability was found in QEMU's 9pfs subsystem. 57 days ago medium5.5 CVE-2026-98142 In the Linux kernel, the following vulnerability has been resolved: drm/cirrus-qemu: Validate BAR0 size during probe The `cirrus-qemu` driver relies on `CIRRUS… linux · linux_kernel 57 days ago high7.8 CVE-2026-46655 virtio-win provides Windows paravirtualized drivers for QEMU and KVM. 2026-09-18 high8.2 CVE-2026-81627 A flaw was found in QEMU. 2026-09-18 high8.0 CVE-2026-85469 A flaw was found in quay-builder-qemu. 2026-09-16 medium5.5 CVE-2026-77159 A symlink-following flaw was found in libvirt's qemuTPMEmulatorPrepareHost() function. 2026-09-11 medium4.4 CVE-2026-6426 A type mismatch vulnerability was found in QEMU's vhost inflight migration VMState handling. 2026-08-10 high7.3 CVE-2026-12080 A flaw was found in the QEMU Guest Agent (qga). A local unprivileged user can exploit a... Red Hat · Red Hat Enterprise Linux 9, Red Hat · Red Hat OpenShift Container Platform 4.22, Red Hat · Red Hat OpenShift Container Platform 5.0 +3 2026-07-20 medium6.5 CVE-2026-51083 Incorrect access control in Proxmox Virtual Environment (PVE) 9.x qemu-server before 9.1.8 and 8.x before 8.4.8 allows users within limited privileges to obtai… Proxmox Virtual Environment (PVE) 9.x qemu-server, 8.x 2026-07-17 high7.2 CVE-2026-51082 A race condition between the vncproxy and vncwebsocket API calls in Proxmox Virtual Environment (PVE) 9.x pve-manager before 9.1.9 and 8.x before 8.4.19; qemu-… Proxmox Virtual Environment (PVE) 9.x pve-manager, 8.x, qemu-server +1 2026-07-17 high7.8 CVE-2026-3842 A flaw was found in QEMU. 2026-07-16 high8.2 CVE-2026-53657 Lima: An arbitrary user in a QEMU VM could gain the root privilege in the VM via the guest agent socket go · github.com/lima-vm/lima/v2 2026-07-10 high7.1 CVE-2026-52953 In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix oops due to out of scope access Below oops triggers when kill QEMU process:… linux · linux_kernel 2026-06-24 high7.8 CVE-2026-46606 Glances is Vulnerable to Command Injection via KVM/QEMU VM Domain Names in glances/plugins/vms/engines/virsh.py pip · glances 2026-06-22 high7.4 CVE-2026-3195 A flaw was found in QEMU. 2026-06-19 medium6.7 CVE-2026-48914 A flaw was found in QEMU's virtio-blk device. 2026-06-12 medium5.1 CVE-2026-2243 A flaw was found in QEMU. 2026-02-19 medium6.5 CVE-2026-0665 An off-by-one error was found in QEMU's KVM Xen guest support. 2026-02-18 low3.3 CVE-2025-8860 A flaw was found in QEMU in the uefi-vars virtual device. 2026-02-18 medium5.5 CVE-2025-14876 A flaw was found in the virtio-crypto device of QEMU. 2026-02-18 high8.2 CVE-2026-24708 OpenStack Nova calls qemu-img without format restrictions for resize pip · Nova 2026-02-18 high8.2 CVE-2026-24843 melange QEMU runner could write files outside workspace directory go · chainguard.dev/melange 2026-02-03 medium6.5 CVE-2025-63749 pnetlab 5.3.11 is vulnerable to Command Injection via the qemu_options parameter. pnetlab · pnetlab 2025-11-18 medium6.2 CVE-2025-12464 A stack-based buffer overflow was found in the QEMU e1000 network device. 2025-10-31 high7.5 CVE-2025-11234 A flaw was found in QEMU. 2025-10-03 medium4.2 CVE-2025-54567 hw/pci/pcie_sriov.c in QEMU through 10.0.3 mishandles the VF Enable bit write mask, a related issue to CVE-2024-26327. qemu · qemu 2025-07-25 medium4.2 CVE-2025-54566 hw/pci/pcie_sriov.c in QEMU through 10.0.3 has a migration state inconsistency, a related issue to CVE-2024-26327. qemu · qemu 2025-07-25 medium5.9 CVE-2025-49133 Libtpms is a library that targets the integration of TPM functionality into hypervisors, primarily into Qemu. libtpms_project · libtpms 2025-06-10 medium5.5 CVE-2022-49297 In the Linux kernel, the following vulnerability has been resolved: nbd: fix io hung while disconnecting device In our tests, "qemu-nbd" triggers a io hung: IN… linux · linux_kernel 2025-02-26 high7.4 CVE-2024-7730 A heap buffer overflow was found in the virtio-snd device in QEMU. qemu · qemu 2024-11-14

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.