NetSight

Security Dashboard

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

Reset
50 matching advisories · page 1 of 2Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.3 CVE-2025-8860 A flaw was found in QEMU in the uefi-vars virtual device. 2026-02-18 low3.8 CVE-2024-8612 A flaw was found in QEMU, in the virtio-scsi, virtio-blk, and virtio-crypto devices. 2024-09-20 low3.4 CVE-2023-34354 A stored cross-site scripting (XSS) vulnerability exists in the upload_brand.cgi functionality of peplink Surf SOHO HW1 v6.3.5 (in QEMU). peplink · surf_soho_firmware 2023-10-11 low3.3 CVE-2023-1386 A flaw was found in the 9p passthrough filesystem (9pfs) implementation in QEMU. qemu · qemu, fedoraproject · fedora 2023-07-24 low3.2 CVE-2020-14394 An infinite loop flaw was found in the USB xHCI controller emulation of QEMU while computing the length of the Transfer Request Block (TRB) Ring. qemu · qemu, fedoraproject · extra_packages_for_enterprise_linux, fedoraproject · fedora +2 2022-08-17 low3.2 CVE-2022-26354 A flaw was found in the vhost-vsock device of QEMU. qemu · qemu, debian · debian_linux 2022-03-16 low3.8 CVE-2021-3595 An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. libslirp_project · libslirp, redhat · enterprise_linux, debian · debian_linux +1 2021-06-15 low3.8 CVE-2021-3594 An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. libslirp_project · libslirp, redhat · enterprise_linux, debian · debian_linux +1 2021-06-15 low3.8 CVE-2021-3593 An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. libslirp_project · libslirp, redhat · enterprise_linux, fedoraproject · fedora +1 2021-06-15 low3.8 CVE-2021-3592 An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. libslirp_project · libslirp, redhat · enterprise_linux, debian · debian_linux +1 2021-06-15 low3.2 CVE-2021-3392 A use-after-free flaw was found in the MegaRAID emulator of QEMU. qemu · qemu, fedoraproject · fedora, debian · debian_linux 2021-03-23 low3.3 CVE-2021-20263 A flaw was found in the virtio-fs shared file system daemon (virtiofsd) of QEMU. qemu · qemu 2021-03-09 low3.2 CVE-2021-20203 An integer overflow issue was found in the vmxnet3 NIC emulator of the QEMU for versions up to v5.2.0. qemu · qemu, fedoraproject · fedora, debian · debian_linux 2021-02-25 low3.9 CVE-2020-29443 ide_atapi_cmd_reply_end in hw/ide/atapi.c in QEMU 5.1.0 allows out-of-bounds read access because a buffer index is not validated. qemu · qemu, debian · debian_linux 2021-01-26 low3.8 CVE-2020-11947 iscsi_aio_ioctl_cb in block/iscsi.c in QEMU 4.1.0 has a heap-based buffer over-read that may disclose unrelated information from process memory to an attacker. qemu · qemu 2020-12-31 low3.2 CVE-2020-25723 A reachable assertion issue was found in the USB EHCI emulation code of QEMU. qemu · qemu, debian · debian_linux 2020-12-02 low3.2 CVE-2020-25743 hw/ide/pci.c in QEMU before 5.1.1 can trigger a NULL pointer dereference because it lacks a pointer check before an ide_cancel_dma_sync call. qemu · qemu, redhat · openstack_platform, redhat · enterprise_linux 2020-10-06 low3.2 CVE-2020-25742 pci_change_irq_level in hw/pci/pci.c in QEMU before 5.1.1 has a NULL pointer dereference because pci_get_bus() might not return a valid pointer. qemu · qemu 2020-10-06 low3.2 CVE-2020-25741 fdctrl_write_data in hw/block/fdc.c in QEMU 5.0.0 has a NULL pointer dereference via a NULL block pointer for the current drive. qemu · qemu 2020-10-02 low3.2 CVE-2020-25084 QEMU 5.0.0 has a use-after-free in hw/usb/hcd-xhci.c because the usb_packet_map return value is not checked. qemu · qemu, debian · debian_linux 2020-09-25 low3.8 CVE-2020-12829 In QEMU through 5.0.0, an integer overflow was found in the SM501 display driver implementation. qemu · qemu, canonical · ubuntu_linux, debian · debian_linux 2020-08-31 low3.3 CVE-2020-14415 oss_write in audio/ossaudio.c in QEMU before 5.0.0 mishandles a buffer position. qemu · qemu, canonical · ubuntu_linux 2020-08-27 low3.8 CVE-2020-16092 In QEMU through 5.0.0, an assertion failure can occur in the network packet processing. qemu · qemu, debian · debian_linux, canonical · ubuntu_linux +1 2020-08-11 low3.3 CVE-2020-15859 QEMU 4.2.0 has a use-after-free in hw/net/e1000e_core.c because a guest OS user can trigger an e1000e packet with the data's address set to the e1000e's MMIO a… qemu · qemu, debian · debian_linux 2020-07-21 low2.3 CVE-2020-15469 In QEMU 4.2.0, a MemoryRegionOps object may lack read/write callback methods, leading to a NULL pointer dereference. qemu · qemu, debian · debian_linux 2020-07-02 low2.5 CVE-2020-13659 address_space_map in exec.c in QEMU 4.2.0 can trigger a NULL pointer dereference related to BounceBuffer. qemu · qemu, debian · debian_linux, opensuse · leap +1 2020-06-02 low3.2 CVE-2020-13362 In QEMU 5.0.0 and earlier, megasas_lookup_frame in hw/scsi/megasas.c has an out-of-bounds read via a crafted reply_queue_head field from a guest OS user. qemu · qemu, debian · debian_linux, opensuse · leap +1 2020-05-28 low3.9 CVE-2020-13361 In QEMU 5.0.0 and earlier, es1370_transfer_audio in hw/audio/es1370.c does not properly validate the frame count, which allows guest OS users to trigger an out… qemu · qemu, debian · debian_linux, opensuse · leap +1 2020-05-28 low3.3 CVE-2020-10717 A potential DoS flaw was found in the virtio-fs shared file system daemon (virtiofsd) implementation of the QEMU version >= v5.0. qemu · qemu 2020-05-04 low3.3 CVE-2020-11869 An integer overflow was found in QEMU 4.0.1 through 4.2.0 in the way it implemented ATI VGA emulation. qemu · qemu 2020-04-27

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.