NetSight

Security Dashboard

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

Reset
893 matching advisories · page 10 of 30Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.8 CVE-2025-4350 A vulnerability classified as critical was found in D-Link DIR-600L up to 2.07B01. dlink · dir-600l_firmware 2025-05-06 high8.8 CVE-2025-4349 A vulnerability classified as critical has been found in D-Link DIR-600L up to 2.07B01. dlink · dir-600l_firmware 2025-05-06 high8.8 CVE-2025-4348 A vulnerability was found in D-Link DIR-600L up to 2.07B01. dlink · dir-600l_firmware 2025-05-06 high8.8 CVE-2025-4347 A vulnerability was found in D-Link DIR-600L up to 2.07B01. dlink · dir-600l_firmware 2025-05-06 high8.8 CVE-2025-4346 A vulnerability was found in D-Link DIR-600L up to 2.07B01. dlink · dir-600l_firmware 2025-05-06 high8.8 CVE-2025-4345 A vulnerability was found in D-Link DIR-600L up to 2.07B01 and classified as critical. dlink · dir-600l_firmware 2025-05-06 high8.8 CVE-2025-4344 A vulnerability, which was classified as critical, was found in D-Link DIR-600L up to 2.07B01. dlink · dir-600l_firmware 2025-05-06 high8.8 CVE-2025-4343 A vulnerability has been found in D-Link DIR-600L up to 2.07B01 and classified as critical. dlink · dir-600l_firmware 2025-05-06 high8.8 CVE-2025-4342 A vulnerability, which was classified as critical, has been found in D-Link DIR-600L up to 2.07B01. dlink · dir-600l_firmware 2025-05-06 high8.8 CVE-2025-3785 A vulnerability has been found in D-Link DWR-M961 1.1.36 and classified as critical. dlink · dwr-m961_firmware 2025-04-18 high7.2 CVE-2025-29039 An issue in dlink DIR 832x 240802 allows a remote attacker to execute arbitrary code via the function 0x41dda8 dlink · dir-823x_firmware 2025-04-17 high8.8 CVE-2025-3538 A vulnerability was found in D-Link DI-8100 16.07.26A1. dlink · di-8100_firmware 2025-04-13 high7.1 CVE-2025-28398 D-LINK DI-8100 16.07.26A1 is vulnerable to Buffer Overflow in the ipsec_net_asp function via the remot_ip parameter. dlink · di-8100_firmware 2025-04-01 high7.1 CVE-2025-28395 D-LINK DI-8100 16.07.26A1 is vulnerable to Buffer Overflow in the ipsec_road_asp function via the host_ip parameter. dlink · di-8100_firmware 2025-04-01 high7.2 CVE-2025-29635 D-Link DIR-823X Command Injection VulnerabilityExploited dlink · dir-823x_firmware 2025-03-25 high7.5 CVE-2024-57440 D-Link DSL-3788 revA1 1.01R1B036_EU_EN is vulnerable to Buffer Overflow via the COMM_MAKECustomMsg function of the webproc cgi dlink · dsl-3788_firmware 2025-03-20 high7.3 CVE-2025-2360 A vulnerability classified as critical was found in D-Link DIR-823G 1.0.2B05_20181207. dlink · dir-823g_firmware 2025-03-17 high7.3 CVE-2025-2359 A vulnerability classified as critical has been found in D-Link DIR-823G 1.0.2B05_20181207. dlink · dir-823g_firmware 2025-03-17 high7.3 CVE-2025-1876 A vulnerability, which was classified as critical, has been found in D-Link DAP-1562 1.10. dlink · dap-1562_firmware 2025-03-03 high8.8 CVE-2025-1539 A vulnerability, which was classified as critical, has been found in D-Link DAP-1320 1.00. dlink · dap-1320_firmware 2025-02-21 high8.8 CVE-2025-1538 A vulnerability classified as critical was found in D-Link DAP-1320 1.00. dlink · dap-1320_firmware 2025-02-21 high8.0 CVE-2025-25895 An OS command injection vulnerability was discovered in D-Link DSL-3782 v1.01 via the public_type parameter. dlink · dsl-3782_firmware 2025-02-18 high8.0 CVE-2025-25894 An OS command injection vulnerability was discovered in D-Link DSL-3782 v1.01 via the samba_wg and samba_nbn parameters. dlink · dsl-3782_firmware 2025-02-18 high8.0 CVE-2025-25893 An OS command injection vulnerability was discovered in D-Link DSL-3782 v1.01 via the inIP, insPort, inePort, exsPort, exePort, and protocol parameters. dlink · dsl-3782_firmware 2025-02-18 high8.8 CVE-2025-25745 D-Link DIR-853 A1 FW1.20B07 was discovered to contain a stack-based buffer overflow vulnerability via the Password parameter in the SetQuickVPNSettings module. dlink · dir-853_firmware 2025-02-14 high7.2 CVE-2025-25743 D-Link DIR-853 A1 FW1.20B07 was discovered to contain a command injection vulnerability in the SetVirtualServerSettings module. dlink · dir-853_firmware 2025-02-12 high7.3 CVE-2025-1104 A vulnerability has been found in D-Link DHP-W310AV 1.04 and classified as critical. dlink · dhp-w310av_firmware 2025-02-07 high8.8 CVE-2024-57376 Buffer Overflow vulnerability in D-Link DSR-150, DSR-150N, DSR-250, DSR-250N, DSR-500N, DSR-1000N from 3.13 to 3.17B901C allows unauthenticated users to execut… dlink · dsr-150_firmware, dlink · dsr-150n_firmware, dlink · dsr-250_firmware +3 2025-01-28 high7.5 CVE-2025-0492 A vulnerability has been found in D-Link DIR-823X 240126/240802 and classified as critical. dlink · dir-823x_firmware 2025-01-15 high7.3 CVE-2024-13030 A vulnerability was found in D-Link DIR-823G 1.0.2B05_20181207. dlink · dir-823g_firmware 2024-12-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.