NetSight

Security Dashboard

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

Reset
503 matching advisories · page 5 of 17Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2025-55588 TOTOLINK A3002R v4.0.0-B20230531.1404 was discovered to contain a buffer overflow in the fw_ip parameter at /boafrm/formPortFw. totolink · a3002r_firmware 2025-08-18 high7.5 CVE-2025-55587 TOTOLINK A3002R v4.0.0-B20230531.1404 was discovered to contain a buffer overflow in the hostname parameter at /boafrm/formMapDelDevice. totolink · a3002r_firmware 2025-08-18 high7.5 CVE-2025-55586 TOTOLINK A3002R v4.0.0-B20230531.1404 was discovered to contain a buffer overflow in the url parameter at /boafrm/formFilter. totolink · a3002r_firmware 2025-08-18 high8.8 CVE-2025-8246 A vulnerability was found in TOTOLINK X15 1.0.0-B20230714.1105. totolink · x15_firmware 2025-07-27 high8.8 CVE-2025-8245 A vulnerability was found in TOTOLINK X15 1.0.0-B20230714.1105. totolink · x15_firmware 2025-07-27 high8.8 CVE-2025-8244 A vulnerability was found in TOTOLINK X15 1.0.0-B20230714.1105. totolink · x15_firmware 2025-07-27 high8.8 CVE-2025-8243 A vulnerability was found in TOTOLINK X15 1.0.0-B20230714.1105 and classified as critical. totolink · x15_firmware 2025-07-27 high8.8 CVE-2025-8242 A vulnerability has been found in TOTOLINK X15 1.0.0-B20230714.1105 and classified as critical. totolink · x15_firmware 2025-07-27 high7.2 CVE-2025-8181 A vulnerability, which was classified as critical, was found in TOTOLINK N600R and X2000R 1.0.0.1. totolink · n600r_firmware, totolink · x2000r_firmware 2025-07-26 high8.8 CVE-2025-8170 A vulnerability classified as critical was found in TOTOLINK T6 4.1.5cu.748_B20211015. totolink · t6_firmware 2025-07-25 high8.8 CVE-2025-8140 A vulnerability was found in TOTOLINK A702R 4.0.0-B20230721.1521. totolink · a702r_firmware 2025-07-25 high8.8 CVE-2025-8139 A vulnerability was found in TOTOLINK A702R 4.0.0-B20230721.1521. totolink · a702r_firmware 2025-07-25 high8.8 CVE-2025-8138 A vulnerability was found in TOTOLINK A702R 4.0.0-B20230721.1521 and classified as critical. totolink · a702r_firmware 2025-07-25 high8.8 CVE-2025-8137 A vulnerability has been found in TOTOLINK A702R 4.0.0-B20230721.1521 and classified as critical. totolink · a702r_firmware 2025-07-25 high8.8 CVE-2025-8136 A vulnerability, which was classified as critical, was found in TOTOLINK A702R 4.0.0-B20230721.1521. totolink · a702r_firmware 2025-07-25 high8.8 CVE-2025-7913 A vulnerability, which was classified as critical, was found in TOTOLINK T6 4.1.5cu.748_B20211015. totolink · t6_firmware 2025-07-21 high8.8 CVE-2025-7912 A vulnerability, which was classified as critical, has been found in TOTOLINK T6 4.1.5cu.748_B20211015. totolink · t6_firmware 2025-07-20 high7.3 CVE-2025-7862 A vulnerability has been found in TOTOLINK T6 4.1.5cu.748_B20211015 and classified as critical. totolink · t6_firmware 2025-07-20 high8.8 CVE-2025-7837 A vulnerability was found in TOTOLINK T6 4.1.5cu.748_B20211015 and classified as critical. totolink · t6_firmware 2025-07-19 high8.8 CVE-2025-7758 A vulnerability, which was classified as critical, has been found in TOTOLINK T6 up to 4.1.5cu.748_B20211015. totolink · t6_firmware 2025-07-17 high8.8 CVE-2025-7460 A vulnerability has been found in TOTOLINK T6 4.1.5cu.748_B20211015 and classified as critical. totolink · t6_firmware 2025-07-11 high8.8 CVE-2025-52089 A hidden remote support feature protected by a static secret in TOTOLINK N300RB firmware version 8.54 allows an authenticated attacker to execute arbitrary OS … totolink · n300rb_firmware 2025-07-11 high8.8 CVE-2025-6953 A vulnerability, which was classified as critical, was found in TOTOLINK A3002RU 3.0.0-B20230809.1615. totolink · a3002ru_firmware 2025-07-01 high8.8 CVE-2025-6940 A vulnerability classified as critical was found in TOTOLINK A702R 4.0.0-B20230721.1521. totolink · a702r_firmware 2025-07-01 high8.8 CVE-2025-6939 A vulnerability classified as critical has been found in TOTOLINK A3002RU 3.0.0-B20230809.1615. totolink · a3002ru_firmware 2025-07-01 high8.8 CVE-2025-6916 A vulnerability, which was classified as critical, was found in TOTOLINK T6 4.1.5cu.748_B20211015. totolink · t6_firmware 2025-06-30 high8.8 CVE-2025-6825 A vulnerability classified as critical was found in TOTOLINK A702R up to 4.0.0-B20230721.1521. totolink · a702r_firmware 2025-06-28 high8.8 CVE-2025-6824 A vulnerability classified as critical has been found in TOTOLINK X15 up to 1.0.0-B20230714.1105. totolink · x15_firmware 2025-06-28 high8.8 CVE-2025-6627 A vulnerability has been found in TOTOLINK A702R 4.0.0-B20230721.1521 and classified as critical. totolink · a702r_firmware 2025-06-25 high8.8 CVE-2025-6568 A vulnerability classified as critical has been found in TOTOLINK EX1200T 4.1.2cu.5232_B20210713. totolink · ex1200t_firmware 2025-06-24

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.