NetSight

Security Dashboard

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

Reset
1,904 matching advisories · page 15 of 64Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.3 CVE-2025-10628 A vulnerability was found in D-Link DIR-852 1.00CN B09. dlink · dir-852_firmware 2025-09-18 medium6.3 CVE-2025-10441 A vulnerability was found in D-Link DI-8100G, DI-8200G and DI-8003G 17.12.20A1/19.12.10A1. 2025-09-15 medium6.3 CVE-2025-10440 A vulnerability has been found in D-Link DI-8100, DI-8100G, DI-8200, DI-8200G, DI-8003 and DI-8003G 16.07.26A1/17.12.20A1/19.12.10A1. 2025-09-15 medium6.3 CVE-2025-10401 A vulnerability was detected in D-Link DIR-823x up to 250416. dlink · dir-823x_firmware 2025-09-14 high7.3 CVE-2025-10123 A vulnerability was determined in D-Link DIR-823X up to 250416. dlink · dir-823x_firmware 2025-09-09 medium5.3 CVE-2025-10093 A vulnerability was identified in D-Link DIR-852 up to 1.00CN B09. dlink · dir-852_firmware 2025-09-08 high8.8 CVE-2025-10034 A vulnerability was found in D-Link DIR-825 1.08.01. dlink · dir-825_firmware 2025-09-06 high8.8 CVE-2025-9938 A weakness has been identified in D-Link DI-8400 16.07.26A1. dlink · di-8400_firmware 2025-09-04 medium4.1 CVE-2025-9769 A security flaw has been discovered in D-Link DI-7400G+ 19.12.25A1. dlink · di-7400g\+_firmware 2025-09-01 high7.3 CVE-2025-9752 A security vulnerability has been detected in D-Link DIR-852 1.00CN B09. dlink · dir-852_firmware 2025-09-01 medium4.7 CVE-2025-9745 A security vulnerability has been detected in D-Link DI-500WF 14.04.10A1T. dlink · di-500wf_firmware 2025-08-31 medium6.3 CVE-2025-9727 A weakness has been identified in D-Link DIR-816L 206b01. dlink · dir-816l_firmware 2025-08-31 critical9.8 CVE-2025-55583 D-Link DIR-868L B1 router firmware version FW2.05WWB02 contains an unauthenticated OS command injection vulnerability in the fileaccess.cgi component. dlink · dir-868l_firmware 2025-08-28 critical10.0 CVE-2018-25115 Multiple D-Link DIR-series routers, including DIR-110, DIR-412, DIR-600, DIR-610, DIR-615, DIR-645, and DIR-815 firmware version 1.03, contain a vulnerability … dlink · dir-110_firmware, dlink · dir-412_firmware, dlink · dir-600_firmware +10 2025-08-27 medium6.6 CVE-2025-55582 D-Link DCS-825L firmware v1.08.01 contains a vulnerability in the watchdog script `mydlink-watch-dog.sh`, which blindly respawns binaries such as `dcp` and `si… dlink · dcs-825l_firmware 2025-08-27 high7.2 CVE-2025-29523 D-Link DSL-7740C with firmware DSL7740C.V6.TR069.20211230 was discovered to contain a command injection vulnerability via the ping6 function. dlink · dsl-7740c_firmware 2025-08-25 high7.0 CVE-2025-51281 D-Link DI-8100 16.07.26A1 is vulnerable to Buffer Overflow via the en`, `val and id parameters in the qj_asp function. dlink · di-8100_firmware 2025-08-25 medium6.5 CVE-2025-29522 D-Link DSL-7740C with firmware DSL7740C.V6.TR069.20211230 was discovered to contain a command injection vulnerability via the ping function. dlink · dsl-7740c_firmware 2025-08-25 medium5.3 CVE-2025-29521 Insecure default credentials for the Adminsitrator account of D-Link DSL-7740C with firmware DSL7740C.V6.TR069.20211230 allows attackers to escalate privileges… dlink · dsl-7740c_firmware 2025-08-25 medium5.3 CVE-2025-29520 Incorrect access control in the Maintenance module of D-Link DSL-7740C with firmware DSL7740C.V6.TR069.20211230 allows authenticated attackers with low-level p… dlink · dsl-7740c_firmware 2025-08-25 medium5.3 CVE-2025-29519 A command injection vulnerability in the EXE parameter of D-Link DSL-7740C with firmware DSL7740C.V6.TR069.20211230 allows attackers to execute arbitrary comma… dlink · dsl-7740c_firmware 2025-08-25 medium6.8 CVE-2025-29517 D-Link DSL-7740C with firmware DSL7740C.V6.TR069.20211230 was discovered to contain a command injection vulnerability via the traceroute6 function. dlink · dsl-7740c_firmware 2025-08-25 high7.2 CVE-2025-29516 D-Link DSL-7740C with firmware DSL7740C.V6.TR069.20211230 was discovered to contain a command injection vulnerability via the backup function. dlink · dsl-7740c_firmware 2025-08-25 critical9.8 CVE-2025-29515 Incorrect access control in the DELT_file.xgi endpoint of D-Link DSL-7740C with firmware DSL7740C.V6.TR069.20211230 allows attackers to modify arbitrary settin… dlink · dsl-7740c_firmware 2025-08-25 critical9.8 CVE-2025-29514 Incorrect access control in the config.xgi function of D-Link DSL-7740C with firmware DSL7740C.V6.TR069.20211230 allows attackers to download the configuration… dlink · dsl-7740c_firmware 2025-08-25 high7.3 CVE-2025-55581 D-Link DCS-825L firmware version 1.08.01 and possibly prior versions contain an insecure implementation in the mydlink-watch-dog.sh script. dlink · dcs-825l_firmware 2025-08-22 high7.5 CVE-2025-55611 D-Link DIR-619L 2.06B01 is vulnerable to Buffer Overflow in the formLanguageChange function via the nextPage parameter. dlink · dir-619l_firmware 2025-08-22 high7.5 CVE-2025-55602 D-Link DIR-619L 2.06B01 is vulnerable to Buffer Overflow in the formSysCmd function via the submit-url parameter. dlink · dir-619l_firmware 2025-08-22 high7.5 CVE-2025-55599 D-Link DIR-619L 2.06B01 is vulnerable to Buffer Overflow in the formWlanSetup function via the parameter f_wds_wepKey. dlink · dir-619l_firmware 2025-08-22 high7.3 CVE-2025-9026 A vulnerability was identified in D-Link DIR-860L 2.04.B04. dlink · dir-860l_firmware 2025-08-15

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.