NetSight

Security Dashboard

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

Reset
1,812 matching advisories · page 4 of 61Index updated 10 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2025-50646 A buffer overflow vulnerability exists in D-Link DI-8003 16.07.26A1 due to insufficient input validation on the name parameter in the /qos_type_asp.asp endpoin… dlink · di-8003_firmware 2026-04-08 high7.5 CVE-2025-50645 A vulnerability has been discovered in D-Link DI-8003 16.07.26A1, which can lead to a buffer overflow when the s parameter in the pppoe_list_opt.asp endpoint i… dlink · di-8003_firmware 2026-04-08 high7.5 CVE-2025-50644 A buffer overflow vulnerability exists in D-Link DI-8003 16.07.26A1 due to improper validation of user input in the qj.asp endpoint. dlink · di-8003_firmware 2026-04-08 high7.5 CVE-2025-52222 D-Link DI-8003 v16.07.26A1, DI-8500 v16.07.26A1; DI-8003G v17.12.21A1, DI-8200G v17.12.20A1, DI-8200 v16.07.26A1, DI-8400 v16.07.26A1, DI-8004w v16.07.26A1, DI… dlink · di-8100_firmware, dlink · di-8100g_firmware, dlink · di-8004w_firmware +6 2026-04-08 high7.5 CVE-2025-45059 D-Link DI-8300 v16.07.26A1 was discovered to contain a buffer overflow via the fn parameter in the tgfile_htm function. dlink · di-8300_firmware 2026-04-08 high7.5 CVE-2025-45058 D-Link DI-8300 v16.07.26A1 was discovered to contain a buffer overflow via the fx parameter in the jingx_asp function. dlink · di-8300_firmware 2026-04-08 high7.5 CVE-2025-45057 D-Link DI-8300 v16.07.26A1 was discovered to contain a buffer overflow via the ip parameter in the ip_position_asp function. dlink · di-8300_firmware 2026-04-08 high8.8 GHSA-qmwh-9m9c-h36m Gotenberg has incomplete fix for ExifTool arbitrary file write: case-insensitive bypass and missing HardLink/SymLink tags go · github.com/gotenberg/gotenberg/v8 2026-04-07 medium5.3 CVE-2026-5312 A weakness has been identified in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR… dlink · dns-1550-04_firmware, dlink · dns-315l_firmware, dlink · dns-320_firmware +9 2026-04-01 medium5.3 CVE-2026-5311 A security flaw has been discovered in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L… dlink · dnr-202l_firmware, dlink · dnr-326_firmware, dlink · dns-1100-4_firmware +9 2026-04-01 medium4.3 CVE-2026-5215 A vulnerability was identified in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR… dlink · dnr-202l_firmware, dlink · dnr-326_firmware, dlink · dns-1100-4_firmware +9 2026-03-31 high8.8 CVE-2026-5214 A vulnerability was found in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR-326,… dlink · dnr-202l_firmware, dlink · dnr-326_firmware, dlink · dns-1100-4_firmware +9 2026-03-31 high8.8 CVE-2026-5213 A vulnerability was determined in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR… dlink · dnr-202l_firmware, dlink · dnr-326_firmware, dlink · dns-1100-4_firmware +9 2026-03-31 high8.8 CVE-2026-5212 A vulnerability has been found in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR… dlink · dnr-202l_firmware, dlink · dnr-326_firmware, dlink · dns-1100-4_firmware +9 2026-03-31 high8.8 CVE-2026-5211 A flaw has been found in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR-326, DNS… dlink · dnr-202l_firmware, dlink · dnr-326_firmware, dlink · dns-1100-4_firmware +9 2026-03-31 high8.8 CVE-2026-5024 A vulnerability was found in D-Link DIR-513 1.10. dlink · dir-513_firmware 2026-03-29 high8.8 CVE-2026-4555 A weakness has been identified in D-Link DIR-513 1.10. dlink · dir-513_firmware 2026-03-22 high8.8 CVE-2026-4529 A vulnerability was identified in D-Link DHP-1320 1.00WWB04. dlink · dhp-1320_firmware 2026-03-21 high7.3 CVE-2026-4499 A vulnerability was determined in D-Link DIR-820LW 2.03. dlink · dir-820lw_firmware 2026-03-20 high8.8 CVE-2026-4486 A vulnerability was found in D-Link DIR-513 1.10. dlink · dir-513_firmware 2026-03-20 medium6.3 CVE-2026-4465 A flaw has been found in D-Link DIR-513 1.10. dlink · dir-513_firmware 2026-03-20 high8.8 CVE-2026-4214 A flaw has been found in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR-326, DNS… dlink · dnr-202l_firmware, dlink · dnr-326_firmware, dlink · dns-1100-4_firmware +9 2026-03-16 high8.8 CVE-2026-4213 A vulnerability was detected in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR-3… dlink · dnr-202l_firmware, dlink · dnr-326_firmware, dlink · dns-1100-4_firmware +9 2026-03-16 high8.8 CVE-2026-4212 A security vulnerability has been detected in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, D… dlink · dnr-202l_firmware, dlink · dnr-326_firmware, dlink · dns-1100-4_firmware +9 2026-03-16 high8.8 CVE-2026-4211 A weakness has been identified in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR… dlink · dnr-202l_firmware, dlink · dnr-326_firmware, dlink · dns-1100-4_firmware +9 2026-03-16 medium6.3 CVE-2026-4210 A security flaw has been discovered in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L… dlink · dnr-202l_firmware, dlink · dnr-326_firmware, dlink · dns-1100-4_firmware +9 2026-03-16 medium6.3 CVE-2026-4209 A vulnerability was identified in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR… dlink · dnr-202l_firmware, dlink · dnr-326_firmware, dlink · dns-1100-4_firmware +9 2026-03-16 medium6.3 CVE-2026-4207 A vulnerability was determined in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR… dlink · dnr-202l_firmware, dlink · dnr-326_firmware, dlink · dns-1100-4_firmware +9 2026-03-16 medium6.3 CVE-2026-4206 A vulnerability was found in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR-326,… dlink · dnr-202l_firmware, dlink · dnr-326_firmware, dlink · dns-1100-4_firmware +9 2026-03-16 medium6.3 CVE-2026-4205 A vulnerability has been found in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR… dlink · dnr-202l_firmware, dlink · dnr-326_firmware, dlink · dns-1100-4_firmware +9 2026-03-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.