NetSight

Security Dashboard

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

Reset
291 matching advisories · page 1 of 10Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
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 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 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 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 medium5.5 CVE-2025-14876 A flaw was found in the virtio-crypto device of QEMU. 2026-02-18 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 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 medium6.0 CVE-2024-3447 A heap-based buffer overflow was found in the SDHCI device emulation of QEMU. qemu · qemu, netapp · hci_compute_node 2024-11-14 medium5.5 CVE-2024-8354 A flaw was found in QEMU. qemu · qemu, redhat · enterprise_linux 2024-09-19 medium5.5 CVE-2022-48870 In the Linux kernel, the following vulnerability has been resolved: tty: fix possible null-ptr-defer in spk_ttyio_release Run the following tests on the qemu p… linux · linux_kernel 2024-08-21 medium6.8 CVE-2024-6505 A flaw was found in the virtio-net device in QEMU. qemu · qemu, redhat · enterprise_linux 2024-07-05 medium5.5 CVE-2024-4693 A flaw was found in the QEMU Virtio PCI Bindings (hw/virtio/virtio-pci.c). 2024-05-14 medium5.3 CVE-2023-45209 An information disclosure vulnerability exists in the web interface /cgi-bin/download_config.cgi functionality of Peplink Smart Reader v1.2.0 (in QEMU). peplink · smart_reader_firmware 2024-04-17 medium5.3 CVE-2023-43491 An information disclosure vulnerability exists in the web interface /cgi-bin/debug_dump.cgi functionality of Peplink Smart Reader v1.2.0 (in QEMU). peplink · smart_reader_firmware 2024-04-17 medium6.8 CVE-2023-40146 A privilege escalation vulnerability exists in the /bin/login functionality of Peplink Smart Reader v1.2.0 (in QEMU). peplink · smart_reader_firmware 2024-04-17 medium5.5 CVE-2024-3567 A flaw was found in QEMU. qemu · qemu, redhat · enterprise_linux 2024-04-10 medium6.0 CVE-2024-26328 An issue was discovered in QEMU 7.1.0 through 8.2.1. qemu · qemu 2024-02-19 medium5.3 CVE-2024-26327 An issue was discovered in QEMU 7.1.0 through 8.2.1. qemu · qemu 2024-02-19 medium6.5 CVE-2023-6683 A flaw was found in the QEMU built-in VNC server while processing ClientCutText messages. qemu · qemu, redhat · enterprise_linux 2024-01-12 medium4.9 CVE-2023-6693 A stack based buffer overflow was found in the virtio-net device of QEMU. qemu · qemu, redhat · enterprise_linux, fedoraproject · fedora 2024-01-02 medium6.0 CVE-2023-2861 A flaw was found in the 9p passthrough filesystem (9pfs) implementation in QEMU. qemu · qemu 2023-12-06 medium6.4 CVE-2023-5088 A bug in QEMU could cause a guest I/O operation otherwise addressed to an arbitrary disk offset to be targeted to offset 0 instead (potentially overwriting the… qemu · qemu, redhat · enterprise_linux, Red Hat · Red Hat Enterprise Linux 9 +1 2023-11-03 medium5.6 CVE-2023-3301 A flaw was found in QEMU. qemu · qemu, redhat · enterprise_linux 2023-09-13

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.