NetSight

Security Dashboard

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

Reset
503 matching advisories · page 3 of 17Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.3 CVE-2026-5691 A vulnerability has been found in Totolink A7100RU 7.4cu.2313_b20191024. 2026-04-06 high7.3 CVE-2026-5690 A flaw has been found in Totolink A7100RU 7.4cu.2313_b20191024. 2026-04-06 high7.3 CVE-2026-5689 A vulnerability was detected in Totolink A7100RU 7.4cu.2313_b20191024. 2026-04-06 high7.3 CVE-2026-5688 A security vulnerability has been detected in Totolink A7100RU 7.4cu.2313_b20191024. 2026-04-06 high7.3 CVE-2026-5678 A weakness has been identified in Totolink A7100RU 7.4cu.2313_b20191024. 2026-04-06 high7.3 CVE-2026-5677 A security flaw has been discovered in Totolink A7100RU 7.4cu.2313_b20191024. 2026-04-06 high7.3 CVE-2026-5676 A vulnerability was identified in Totolink A8000R 5.9c.681_B20180413. 2026-04-06 high7.3 CVE-2026-5176 A security flaw has been discovered in Totolink A3300R 17.0.0cu.557_b20221024. totolink · a3300r_firmware 2026-03-31 high8.8 CVE-2026-4976 A vulnerability was found in Totolink LR350 9.3.5u.6369_B20220309. totolink · lr350_firmware 2026-03-27 high7.2 CVE-2026-4611 A flaw has been found in TOTOLINK X6000R 9.4.0cu.1360_B20241207/9.4.0cu.1498_B20250826. totolink · x6000r_firmware 2026-03-23 high7.3 CVE-2026-4497 A vulnerability was determined in Totolink WA300 5.2cu.7112_B20190227. totolink · wa300_firmware 2026-03-20 high7.3 CVE-2026-3696 A vulnerability was found in Totolink N300RH 6..1c.1353_B20190305. totolink · n300rh_firmware 2026-03-08 high7.5 CVE-2025-67445 TOTOLINK X5000R V9.1.0cu.2415_B20250515 contains a denial-of-service vulnerability in /cgi-bin/cstecgi.cgi. totolink · x5000r_firmware 2026-02-24 high8.8 CVE-2025-70328 TOTOLINK X6000R v9.4.0cu.1498_B20250826 contains an OS command injection vulnerability in the NTPSyncWithHost handler of the /usr/sbin/shttpd executable. totolink · x6000r_firmware 2026-02-23 high8.0 CVE-2025-70329 TOTOLink X5000R v9.1.0cu_2415_B20250515 contains an OS command injection vulnerability in the setIptvCfg handler of the /usr/sbin/lighttpd executable. totolink · x5000r_firmware 2026-02-23 high8.8 CVE-2026-26736 TOTOLINK A3002RU_V3 V3.0.0-B20220304.1804 was discovered to contain a stack-based buffer overflow via the static_ipv6 parameter in the formIpv6Setup function. totolink · a3002ru_firmware 2026-02-17 high8.8 CVE-2026-26732 TOTOLINK A3002RU V2.1.1-B20211108.1455 was discovered to contain a stack-based buffer overflow via the vpnUser or vpnPassword` parameters in the formFilter fun… totolink · a3002ru_firmware 2026-02-17 high8.8 CVE-2026-26731 TOTOLINK A3002RU V2.1.1-B20211108.1455 was discovered to contain a stack-based buffer overflow via the routernamer`parameter in the formDnsv6 function. totolink · a3002ru_firmware 2026-02-17 high8.8 CVE-2026-1686 A security flaw has been discovered in Totolink A3600R 5.9c.4959. totolink · a3600r_firmware 2026-01-30 high8.8 CVE-2026-1328 A vulnerability was detected in Totolink NR1800X 9.1.0u.6279_B20210910. totolink · nr1800x_firmware 2026-01-22 high8.8 CVE-2026-1158 A security flaw has been discovered in Totolink LR350 9.3.5u.6369_B20220309. totolink · lr350_firmware 2026-01-19 high8.8 CVE-2026-1157 A vulnerability was identified in Totolink LR350 9.3.5u.6369_B20220309. totolink · lr350_firmware 2026-01-19 high8.8 CVE-2026-1156 A vulnerability was determined in Totolink LR350 9.3.5u.6369_B20220309. totolink · lr350_firmware 2026-01-19 high8.8 CVE-2026-1155 A vulnerability was found in Totolink LR350 9.3.5u.6369_B20220309. totolink · lr350_firmware 2026-01-19 high8.8 CVE-2026-1143 A weakness has been identified in TOTOLINK A3700R 9.1.2u.5822_B20200513. totolink · a3700r_firmware 2026-01-19 high7.5 CVE-2025-63154 TOTOLink A7000R V9.1.0u.6115_B20201022 was discovered to contain a stack overflow in the addEffect parameter of the urldecode function. totolink · a7000r_firmware 2025-11-10 high7.5 CVE-2025-63153 TOTOLink A7000R V9.1.0u.6115_B20201022 was discovered to contain a stack overflow in the ssid parameter of the urldecode function. totolink · a7000r_firmware 2025-11-10 high7.5 CVE-2025-63459 Totolink A7000R v9.1.0u.6115_B20201022 was discovered to contain a stack overflow via the ssid5g parameter in the sub_421CF0 function. totolink · a7000r_firmware 2025-10-31 high7.5 CVE-2025-63465 Totolink LR350 v9.3.5u.6369_B20220309 was discovered to contain a stack overflow via the ssid parameter in the sub_422880 function. totolink · lr350_firmware 2025-10-31 high7.5 CVE-2025-63464 Totolink LR350 v9.3.5u.6369_B20220309 was discovered to contain a stack overflow via the ssid parameter in the sub_42396C function. totolink · lr350_firmware 2025-10-31

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.