NetSight

Security Dashboard

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

Reset
694 matching advisories · page 1 of 24Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.4 CVE-2026-129258 A vulnerability was identified in Tenda AC18 15.03.05.05_multi/15.03.05.19 Build 6318. Affected... Tenda · AC18 8 days ago critical10.0 CVE-2026-123966 A vulnerability was determined in Tenda AC19 16.03.10.07. Affected by this issue is the function... Tenda · AC19 15 days ago critical9.9 CVE-2026-114268 A flaw has been found in Tenda BE3L Pro 16.03.60.62. 31 days ago critical10.0 CVE-2026-113744 A security vulnerability has been detected in Tenda AC19 16.03.10.07. 32 days ago critical9.9 CVE-2026-105778 A vulnerability has been found in Tenda AC5 02.03.01.111_multi. 47 days ago critical9.1 CVE-2026-104611 A vulnerability was detected in Tenda AC9 15.03.02.13. 51 days ago critical10.0 CVE-2026-104610 A security vulnerability has been detected in Tenda HG7, HG9 and HG10 300001138_en_xpon. 51 days ago critical9.9 CVE-2026-86167 A vulnerability was identified in Tenda HG10 300001138. 2026-09-06 critical9.8 CVE-2026-86165 A vulnerability was found in Tenda HG10 300001138. 2026-09-06 critical9.1 CVE-2026-86153 A vulnerability has been found in Tenda CP3 27.5.57.101. 2026-09-06 critical10.0 CVE-2026-86152 A flaw has been found in Tenda CP3 27.5.57.101. 2026-09-06 critical9.1 CVE-2026-86151 A vulnerability was detected in Tenda CP3 27.5.57.101. 2026-09-06 critical9.1 CVE-2026-86149 A weakness has been identified in Tenda CP3 27.5.57.101. 2026-09-05 critical9.1 CVE-2026-86148 A security flaw has been discovered in Tenda CP3 27.5.57.101. 2026-09-05 critical9.8 CVE-2026-85109 A vulnerability was determined in Tenda HG10 300001138. 2026-09-03 critical9.8 CVE-2026-38577 Insecure hardcoded credentials in the Admin account of Tenda HG21 V4.0.0-260302 allows attackers to gain root access. 2026-08-31 critical10.0 CVE-2026-82695 A security flaw has been discovered in Tenda AC18 15.03.05.19. 2026-08-31 critical10.0 CVE-2026-82694 A vulnerability was identified in Tenda AC1206 15.03.06.23. 2026-08-31 critical10.0 CVE-2026-82693 A vulnerability was determined in Tenda AC1206 15.03.06.23. 2026-08-31 critical10.0 CVE-2026-82542 A weakness has been identified in Tenda HG10 300001138. 2026-08-30 critical9.8 CVE-2026-67967 Buffer Overflow vulnerability in Tenda W20E V16.01.0.6(2782) allows an attacker to execute arbitrary code. 2026-08-17 critical9.8 CVE-2026-67966 Tenda W20E V16.01.0.6(2782) /goform/telnet endpoint allows unauthenticated remote attackers to activate the Telnet daemon and obtain root shell access. 2026-08-17 critical9.8 CVE-2026-19924 A security vulnerability has been detected in Tenda AC10 16.03.10.09_multi_TDE01. 2026-08-16 critical9.8 CVE-2026-19747 A weakness has been identified in Tenda CH7, CH7G, CH10, CP3, CP3 Pro, CP7, TC3B14C, TC3B15C, TC3T14C and TC3T15C up to 20260625. 2026-08-13 critical9.8 CVE-2026-67822 Tenda W6-S 1.0.0.4(510) contains a stack-based buffer overflow vulnerability in the /goform/wifiSSIDset endpoint. 2026-07-31 critical9.8 CVE-2024-51315 The Tenda TX9 V22.03.02.20 firmware has a stack overflow vulnerability in the sub_425964 function of the file /goform/SetOnlineDevName 2026-07-20 critical9.8 CVE-2024-51314 The Tenda TX9 V22.03.02.20 firmware has a stack overflow vulnerability in the sub_424CE0 function of the file /goform/setMacFilterCfg. 2026-07-20 critical9.8 CVE-2024-51312 The Tenda TX9 V22.03.02.20 firmware has a stack overflow vulnerability in the sub_42EEE0 function of the file /goform/SetStaticRouteCfg. 2026-07-20 critical9.8 CVE-2024-51313 The Tenda TX9 V22.03.02.20 firmware has a stack overflow vulnerability in the sub_42EA38 function of the file /goform/SetVirtualServerCfg. 2026-07-20 critical9.8 CVE-2024-51311 The Tenda TX9 V22.03.02.05 firmware has a stack overflow vulnerability in the sub_4418CC function of the file /goform/SetNetControlList. 2026-07-20

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.