NetSight

Security Dashboard

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

Reset
1,904 matching advisories · page 16 of 64Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.5 CVE-2025-9003 A vulnerability has been found in D-Link DIR-818LW 1.04. dlink · dir-818lw_firmware 2025-08-15 medium6.6 CVE-2025-8978 A vulnerability was determined in D-Link DIR-619L 6.02CN02. dlink · dir-619l_firmware 2025-08-14 medium6.3 CVE-2025-8956 A vulnerability was found in D-Link DIR‑818L up to 1.05B01. dlink · dir-818l_firmware 2025-08-14 high7.2 CVE-2025-8949 A vulnerability was identified in D-Link DIR-825 2.10. dlink · dir-825_firmware 2025-08-14 critical9.8 CVE-2013-10069 The web interface of multiple D-Link routers, including DIR-600 rev B (≤2.14b01) and DIR-300 rev B (≤2.13), contains an unauthenticated OS command injection vu… dlink · dir-600_firmware, dlink · dir-300_firmware 2025-08-05 high7.2 CVE-2013-10059 An authenticated OS command injection vulnerability exists in various D-Link routers (tested on DIR-615H1 running firmware version 8.04) via the tools_vct.htm … dlink · dir-615h_firmware 2025-08-01 high8.8 CVE-2013-10050 An OS command injection vulnerability exists in multiple D-Link routers (confirmed on DIR-300 rev A v1.05 and DIR-615 rev D v4.13) via the authenticated tools_… dlink · dir-300_firmware, dlink · dir-615_firmware 2025-08-01 critical9.8 CVE-2013-10048 An OS command injection vulnerability exists in various legacy D-Link routers—including DIR-300 rev B and DIR-600 (firmware ≤ 2.13 and ≤ 2.14b01, respectively)… dlink · dir-300_firmware, dlink · dir-600_firmware 2025-08-01 low3.5 CVE-2025-51385 D-LINK DI-8200 16.07.26A1 is vulnerable to Buffer Overflow in the yyxz_dlink_asp function via the id parameter. dlink · di-8200_firmware 2025-07-31 low3.5 CVE-2025-51384 D-LINK DI-8200 16.07.26A1 is vulnerable to Buffer Overflow in the ipsec_net_asp function via the remot_ip parameter. dlink · di-8200_firmware 2025-07-31 low3.5 CVE-2025-51383 D-LINK DI-8200 16.07.26A1 is vulnerable to Buffer Overflow in the ipsec_road_asp function via the host_ip parameter. dlink · di-8200_firmware 2025-07-31 critical9.8 CVE-2012-10021 A stack-based buffer overflow vulnerability exists in D-Link DIR-605L Wireless N300 Cloud Router firmware versions 1.12 and 1.13 via the getAuthCode() function. dlink · dir-605l_firmware 2025-07-31 medium6.8 CVE-2025-8231 A vulnerability, which was classified as critical, has been found in D-Link DIR-890L up to 111b04. dlink · dir-890l_firmware 2025-07-27 high8.8 CVE-2025-8184 A vulnerability was found in D-Link DIR-513 up to 1.10 and classified as critical. dlink · dir-513_firmware 2025-07-26 medium6.5 CVE-2025-8175 A vulnerability was found in D-Link DI-8400 16.07.26A1. dlink · di-8400_firmware 2025-07-26 high8.8 CVE-2025-8169 A vulnerability classified as critical has been found in D-Link DIR-513 1.10. dlink · dir-513_firmware 2025-07-25 high8.8 CVE-2025-8168 A vulnerability was found in D-Link DIR-513 1.10. dlink · dir-513_firmware 2025-07-25 critical9.8 CVE-2014-125117 A stack-based buffer overflow vulnerability in the my_cgi.cgi component of certain D-Link devices, including the DSP-W215 version 1.02, can be exploited via a … dlink · dsp-w215_firmware 2025-07-25 high8.8 CVE-2025-8159 A vulnerability was found in D-Link DIR-513 1.0. dlink · dir-513_firmware 2025-07-25 low3.5 CVE-2025-8155 A vulnerability has been found in D-Link DCS-6010L 1.15.03 and classified as problematic. dlink · dcs-6010l_firmware 2025-07-25 high8.8 CVE-2025-7945 A vulnerability was found in D-Link DIR-513 up to 20190831. 2025-07-22 medium6.3 CVE-2025-7932 A vulnerability classified as critical has been found in D-Link DIR‑817L up to 1.04B01. dlink · dir-817l_firmware 2025-07-21 high8.8 CVE-2025-7911 A vulnerability classified as critical was found in D-Link DI-8100 1.0. dlink · di-8100_firmware 2025-07-20 high8.8 CVE-2025-7910 A vulnerability classified as critical has been found in D-Link DIR-513 1.10. dlink · dir-513_firmware 2025-07-20 high8.8 CVE-2025-7909 A vulnerability was found in D-Link DIR-513 1.0. dlink · dir-513_firmware 2025-07-20 high8.8 CVE-2025-7908 A vulnerability was found in D-Link DI-8100 1.0. dlink · di-8100_firmware 2025-07-20 medium6.3 CVE-2025-7836 A vulnerability has been found in D-Link DIR-816L up to 2.06B01 and classified as critical. dlink · dir-816l_firmware 2025-07-19 high8.8 CVE-2025-7790 A vulnerability was found in D-Link DI-8100 16.07.26A1. dlink · di-8100_firmware 2025-07-18 high8.8 CVE-2025-7762 A vulnerability, which was classified as critical, has been found in D-Link DI-8100 16.07.26A1. dlink · di-8100_firmware 2025-07-17 critical9.3 CVE-2025-34125 An unauthenticated command injection vulnerability exists in the cookie handling process of the lighttpd web server on D-Link DSP-W110A1 firmware version 1.05B… 2025-07-16

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.