NetSight

Security Dashboard

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

Reset
1,480 matching advisories · page 15 of 50Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.2 CVE-2026-1723 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in TOTOLINK X6000R allows OS Command Injection.This is… X6000R 2026-01-30 high8.8 CVE-2026-1686 A security flaw has been discovered in Totolink A3600R 5.9c.4959. totolink · a3600r_firmware 2026-01-30 medium6.3 CVE-2026-1623 A weakness has been identified in Totolink A7000R 4.1cu.4154. totolink · a7000r_firmware 2026-01-29 medium6.3 CVE-2026-1601 A weakness has been identified in Totolink A7000R 4.1cu.4154. totolink · a7000r_firmware 2026-01-29 medium6.3 CVE-2026-1548 A flaw has been found in Totolink A7000R 4.1cu.4154. totolink · a7000r_firmware 2026-01-28 medium6.3 CVE-2026-1547 A vulnerability was detected in Totolink A7000R 4.1cu.4154. totolink · a7000r_firmware 2026-01-28 high8.8 CVE-2026-1328 A vulnerability was detected in Totolink NR1800X 9.1.0u.6279_B20210910. totolink · nr1800x_firmware 2026-01-22 medium6.3 CVE-2026-1327 A security vulnerability has been detected in Totolink NR1800X 9.1.0u.6279_B20210910. totolink · nr1800x_firmware 2026-01-22 medium6.3 CVE-2026-1326 A weakness has been identified 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 medium6.3 CVE-2026-1150 A security flaw has been discovered in Totolink LR350 9.3.5u.6369_B20220309. totolink · lr350_firmware 2026-01-19 medium6.3 CVE-2026-1149 A vulnerability was identified 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 medium5.3 CVE-2026-0731 A vulnerability has been found in TOTOLINK WA1200 5.9c.2914. totolink · wa1200-poe, totolink · wa1200-poe_firmware 2026-01-08 medium6.3 CVE-2026-0641 A security vulnerability has been detected in TOTOLINK WA300 5.2cu.7112_B20190227. totolink · wa300_firmware 2026-01-06 critical9.8 CVE-2025-14964 A vulnerability has been found in TOTOLINK T10 4.1.8cu.5083_B20200521. totolink · t10_firmware 2025-12-19 critical9.1 CVE-2025-55895 TOTOLINK A3300R V17.0.0cu.557_B20221024 and N200RE V9.3.5u.6448_B20240521 and V9.3.5u.6437_B20230519 are vulnerable to Incorrect Access Control. totolink · a3300r_firmware, totolink · n200re_firmware 2025-12-15 medium6.5 CVE-2025-55901 TOTOLINK A3300R V17.0.0cu.596_B20250515 is vulnerable to command injection in the function NTPSyncWithHost via the host_time parameter. totolink · a3300r_firmware 2025-12-15 medium6.5 CVE-2025-55893 TOTOLINK N200RE V9.3.5u.6437_B20230519 is vulnerable to command Injection in setOpModeCfg via hostName. totolink · n200re_firmware 2025-12-15 medium6.3 CVE-2025-14586 A vulnerability was determined in TOTOLINK X5000R 9.1.0cu.2089_B20211224. totolink · x5000r_firmware 2025-12-13 critical9.8 CVE-2025-13184 Unauthenticated Telnet enablement via cstecgi.cgi (auth bypass) leading to unauthenticated root login with a blank password on factory/reset X5000R V9.1.0u.636… totolink · x5000r_firmware 2025-12-10 critical9.3 CVE-2025-34319 TOTOLINK N300RT wireless router firmware versions prior to V3.4.0-B20250430 (discovered in V2.1.8-B20201030.1539) contain an OS command injection vulnerability… TOTOLINK N300RT wireless router firmware 2025-12-03 medium6.5 CVE-2025-60702 A command injection vulnerability exists in the TOTOLINK A950RG Router firmware V5.9c.4592_B20191022_ALL within the `system.so` binary. totolink · a950rg_firmware 2025-11-13 medium6.5 CVE-2025-60699 A buffer overflow vulnerability exists in the TOTOLINK A950RG Router firmware V5.9c.4592_B20191022_ALL within the `global.so` binary. totolink · a950rg_firmware 2025-11-13 medium6.5 CVE-2025-60688 A stack buffer overflow vulnerability exists in the ToToLink LR1200GB (V9.1.0u.6619_B20230130) and NR1800X (V9.1.0u.6681_B20230703) Router firmware within the … totolink · lr1200gb_firmware, totolink · nr1800x_firmware 2025-11-13 medium6.5 CVE-2025-60687 An unauthenticated command injection vulnerability exists in the ToToLink LR1200GB Router firmware V9.1.0u.6619_B20230130 within the cstecgi.cgi binary (sub_41… totolink · lr1200gb_firmware 2025-11-13 medium5.1 CVE-2025-60686 A local stack-based buffer overflow vulnerability exists in the infostat.cgi and cstecgi.cgi binaries of ToToLink routers (A720R V4.1.5cu.614_B20230630, LR1200… totolink · a720r_firmware, totolink · lr1200gb_firmware, totolink · nr1800x_firmware 2025-11-13

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.