NetSight

Security Dashboard

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

Reset
514 matching advisories · page 3 of 18Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.7 CVE-2026-76920 3gpp phone log file parser crash in 4.6.0 to 4.6.7 and 4.4.0 to 4.4.18 allows denial of service wireshark · wireshark 2026-08-19 medium5.3 CVE-2026-76919 ESS protocol dissector crash in 4.6.0 to 4.6.7 and 4.4.0 to 4.4.18 allows denial of service wireshark · wireshark 2026-08-19 medium5.5 CVE-2026-76918 SSH protocol dissector crash in 4.6.0 to 4.6.7 and 4.4.0 to 4.4.18 allows denial of service wireshark · wireshark 2026-08-19 medium5.5 CVE-2026-76917 Bluetooth AVRCP Profile protocol dissector crash in 4.6.0 to 4.6.7 and 4.4.0 to 4.4.18 allows denial of service wireshark · wireshark 2026-08-19 medium4.7 CVE-2026-76889 UMTS FP protocol dissector crash in 4.6.0 to 4.6.7 and 4.4.0 to 4.4.18 allows denial of service wireshark · wireshark 2026-08-19 medium4.7 CVE-2026-76883 Catapult DCT2000 file parser crash in 4.6.0 to 4.6.7 and 4.4.0 to 4.4.18 allows denial of service wireshark · wireshark 2026-08-19 medium4.7 CVE-2026-76882 Bluetooth Attribute Protocol dissector crash in 4.6.0 to 4.6.7 and 4.4.0 to 4.4.18 allows denial of service wireshark · wireshark 2026-08-19 medium4.7 CVE-2026-76881 CMS protocol dissector crash in 4.6.0 to 4.6.7 and 4.4.0 to 4.4.18 allows denial of service wireshark · wireshark 2026-08-19 medium6.6 CVE-2026-19696 Ixia IxVeriWave and Vector Informatik BLF file parser crashes in 4.6.0 to 4.6.7 allows denial of service on Windows wireshark · wireshark 2026-08-13 medium4.7 CVE-2026-19695 Gammu DCT3 trace file parser crash in 4.6.0 to 4.6.7 allows denial of service wireshark · wireshark 2026-08-13 medium4.7 CVE-2026-19694 TTX Logger file parser crash in 4.6.0 to 4.6.7 allows denial of service wireshark · wireshark 2026-08-13 medium5.5 CVE-2026-15174 Catapult DCT2000 protocol dissector crash in Wireshark 4.6.0 to 4.6.6 and 4.4.0 to 4.4.16 allows denial of service wireshark · wireshark 2026-07-08 medium4.7 CVE-2026-15173 pcapng file parser crash in Wireshark 4.6.0 to 4.6.6 allows denial of service wireshark · wireshark 2026-07-08 medium5.5 CVE-2026-15172 FMP/NOTIFY protocol dissector crash in Wireshark 4.6.0 to 4.6.6 and 4.4.0 to 4.4.16 allows denial of service wireshark · wireshark 2026-07-08 medium5.5 CVE-2026-15171 SSH protocol dissector crash in Wireshark 4.6.0 to 4.6.6 and 4.4.0 to 4.4.16 allows denial of service wireshark · wireshark 2026-07-08 medium5.5 CVE-2026-15170 Z39.50 protocol dissector crash in Wireshark 4.6.0 to 4.6.6 and 4.4.0 to 4.4.16 allows denial of service wireshark · wireshark 2026-07-08 medium5.5 CVE-2026-15169 UMTS FP protocol dissector crash in Wireshark 4.6.0 to 4.6.6 and 4.4.0 to 4.4.16 allows denial of service wireshark · wireshark 2026-07-08 medium5.5 CVE-2026-15166 IEEE 802.11 protocol dissector crash in Wireshark 4.6.0 to 4.6.6 and 4.4.0 to 4.4.16 allows denial of service wireshark · wireshark 2026-07-08 medium5.5 CVE-2026-15165 TLS ECH decryptor crash in Wireshark 4.6.0 to 4.6.6 allows denial of service wireshark · wireshark 2026-07-08 medium5.5 CVE-2026-15164 Crash in ciscodump 4.6.0 to 4.6.6 and 4.4.0 to 4.4.16 allows denial of service wireshark · wireshark 2026-07-08 medium5.5 CVE-2026-15163 Multiple protocol dissector infinite loops in Wireshark 4.6.0 to 4.6.6 and 4.4.0 to 4.4.16 allow denial of service wireshark · wireshark 2026-07-08 medium5.5 CVE-2026-9759 ROHC protocol dissector crash in Wireshark 4.6.0 to 4.6.5 and 4.4.0 to 4.4.15 allows denial of service wireshark · wireshark 2026-05-27 medium6.8 CVE-2026-43901 Wireshark MCP is an MCP Server that turns tshark into a structured analysis interface, then layers in optional Wireshark suite utilities. pip · wireshark-mcp 2026-05-05 medium5.5 CVE-2026-6525 IEEE 802.11 protocol dissector crash in Wireshark 4.6.0 to 4.6.4 wireshark · wireshark 2026-05-02 medium4.7 CVE-2026-5404 K12 RF5 file parser crash in Wireshark 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14 allows denial of service wireshark · wireshark 2026-05-01 medium5.5 CVE-2026-6870 GSM RP protocol dissector crash in Wireshark 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14 allows denial of service wireshark · wireshark 2026-04-30 medium5.5 CVE-2026-6869 WebSocket protocol dissector crash in Wireshark 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14 allows denial of service wireshark · wireshark 2026-04-30 medium5.5 CVE-2026-6867 SMB2 protocol dissector crash in Wireshark 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14 allows denial of service wireshark · wireshark 2026-04-30 medium5.5 CVE-2026-6538 BEEP protocol dissector crash in Wireshark 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14 allows denial of service wireshark · wireshark 2026-04-30 medium5.5 CVE-2026-6537 ZigBee protocol dissector crash in Wireshark 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14 allows denial of service wireshark · wireshark 2026-04-30

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.