NetSight

Security Dashboard

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

Reset
67 matching advisories · page 1 of 3Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.4 CVE-2026-129352 A vulnerability was detected in TRENDnet TEW-657BRM 1.00.1. This issue affects some unknown... TRENDnet · TEW-657BRM 7 days ago critical10.0 CVE-2026-129351 A security vulnerability has been detected in TRENDnet TEW-657BRM 1.00.1. This vulnerability... TRENDnet · TEW-657BRM 7 days ago critical9.9 CVE-2026-109157 A vulnerability was found in TRENDnet TEW-432BRP 3.10B20. 39 days ago critical10.0 CVE-2026-108804 A vulnerability was detected in TRENDnet TEW-751DR, TEW-752DRU and TEW733GR 1.03B01/1.03B03. 41 days ago critical10.0 CVE-2026-77946 A vulnerability was determined in TRENDnet TEW-821DAP 2.2.01b05. 2026-08-22 critical9.9 CVE-2026-76590 A vulnerability was identified in TRENDnet TEW-755AP up to 20260702. 2026-08-19 critical9.9 CVE-2026-76589 A vulnerability was found in TRENDnet TEW-755AP up to 20260702. 2026-08-19 critical9.9 CVE-2026-76584 A security flaw has been discovered in TRENDnet TV-IP751WIC 11.03.03. 2026-08-19 critical9.9 CVE-2026-75976 A weakness has been identified in TRENDnet TEW-823DRU 1.1.02b01. 2026-08-19 critical9.9 CVE-2026-75877 A flaw has been found in TRENDnet TV-IP751WIC 11.03.03. 2026-08-18 critical10.0 CVE-2026-75784 A vulnerability was detected in TRENDnet TEW-WLC100 1v2.07b01. 2026-08-18 critical9.6 CVE-2026-75783 A security vulnerability has been detected in TRENDnet TEW-WLC100P 12.07b01. 2026-08-18 critical9.8 CVE-2025-15471 A vulnerability was detected in TRENDnet TEW-713RE 1.02. trendnet · tew-713re_firmware 2026-01-07 critical9.8 CVE-2024-46484 TRENDnet TV-IP410 vA1.0R was discovered to contain an OS command injection vulnerability via the /server/cgi-bin/testserv.cgi component. trendnet · tv-ip410_firmware 2025-08-29 critical9.8 CVE-2025-8731 A vulnerability was identified in TRENDnet TI-G160i, TI-PG102i and TPL-430AP up to 20250724. 2025-08-08 critical9.8 CVE-2024-57590 TRENDnet TEW-632BRP v1.010B31 devices have an OS command injection vulnerability in the CGl interface "ntp_sync.cgi",which allows remote attackers to execute a… trendnet · tew-632brp_firmware 2025-01-27 critical9.8 CVE-2024-50667 The boa httpd of Trendnet TEW-820AP 1.01.B01 has a stack overflow vulnerability in /boafrm/formIPv6Addr, /boafrm/formIpv6Setup, /boafrm/formDnsv6. trendnet · tew-820ap_firmware 2024-11-11 critical9.8 CVE-2024-42813 In TRENDnet TEW-752DRU FW1.03B01, there is a buffer overflow vulnerability due to the lack of length verification for the service field in gena.cgi. trendnet · tew-752dru_firmware 2024-08-19 critical9.1 CVE-2024-37642 TRENDnet TEW-814DAP v1_(FW1.01B01) was discovered to contain a command injection vulnerability via the ipv4_ping, ipv6_ping parameter at /formSystemCheck . trendnet · tew-814dap_firmware 2024-06-14 critical10.0 CVE-2024-28354 There is a command injection vulnerability in the TRENDnet TEW-827DRU router with firmware version 2.10B01. trendnet · tew-827dru_firmware 2024-03-15 critical9.8 CVE-2023-49237 An issue was discovered on TRENDnet TV-IP1314PI 5.5.3 200714 devices. trendnet · tv-ip1314pi_firmware 2024-01-09 critical9.8 CVE-2023-49236 A stack-based buffer overflow was discovered on TRENDnet TV-IP1314PI 5.5.3 200714 devices, leading to arbitrary command execution. trendnet · tv-ip1314pi_firmware 2024-01-09 critical9.8 CVE-2023-49235 An issue was discovered in libremote_dbg.so on TRENDnet TV-IP1314PI 5.5.3 200714 devices. trendnet · tv-ip1314pi_firmware 2024-01-09 critical9.8 CVE-2022-46601 TRENDnet TEW755AP 1.13B01 was discovered to contain a stack overflow via the setbg_num parameter in the icp_setbg_img (sub_41DD68) function. trendnet · tew-755ap_firmware 2022-12-30 critical9.8 CVE-2022-46600 TRENDnet TEW755AP 1.13B01 was discovered to contain a stack overflow via the wps_sta_enrollee_pin parameter in the action set_sta_enrollee_pin_24g function. trendnet · tew-755ap_firmware 2022-12-30 critical9.8 CVE-2022-46599 TRENDnet TEW755AP 1.13B01 was discovered to contain a stack overflow via the setlogo_num parameter in the icp_setlogo_img (sub_41DBF4) function. trendnet · tew-755ap_firmware 2022-12-30 critical9.8 CVE-2022-46598 TRENDnet TEW755AP 1.13B01 was discovered to contain a command injection vulnerability via the wps_sta_enrollee_pin parameter in the action set_sta_enrollee_pin… trendnet · tew-755ap_firmware 2022-12-30 critical9.8 CVE-2022-46597 TRENDnet TEW755AP 1.13B01 was discovered to contain a command injection vulnerability via the sys_service parameter in the setup_wizard_mydlink (sub_4104B8) fu… trendnet · tew-755ap_firmware 2022-12-30 critical9.8 CVE-2022-46596 TRENDnet TEW755AP 1.13B01 was discovered to contain a stack overflow via the del_num parameter in the icp_delete_img (sub_41DEDC) function. trendnet · tew-755ap_firmware 2022-12-30 critical9.8 CVE-2022-46594 TRENDnet TEW755AP 1.13B01 was discovered to contain a stack overflow via the update_file_name parameter in the auto_up_fw (sub_420A04) function. trendnet · tew-755ap_firmware 2022-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.