NetSight

Security Dashboard

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

Reset
104 matching advisories · page 2 of 4Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.8 CVE-2025-7093 A vulnerability was found in Belkin F9K1122 1.00.33. belkin · f9k1122_firmware 2025-07-06 high8.8 CVE-2025-7092 A vulnerability has been found in Belkin F9K1122 1.00.33 and classified as critical. belkin · f9k1122_firmware 2025-07-06 high8.8 CVE-2025-7091 A vulnerability was found in Belkin F9K1122 1.00.33. belkin · f9k1122_firmware 2025-07-06 high8.8 CVE-2025-7090 A vulnerability, which was classified as critical, has been found in Belkin F9K1122 1.00.33. belkin · f9k1122_firmware 2025-07-06 high8.8 CVE-2025-7089 A vulnerability was found in Belkin F9K1122 1.00.33 and classified as critical. belkin · f9k1122_firmware 2025-07-06 high8.8 CVE-2025-7088 A vulnerability, which was classified as critical, was found in Belkin F9K1122 1.00.33. belkin · f9k1122_firmware 2025-07-06 high8.8 CVE-2025-7087 A vulnerability classified as critical was found in Belkin F9K1122 1.00.33. belkin · f9k1122_firmware 2025-07-06 high8.8 CVE-2025-7086 A vulnerability classified as critical has been found in Belkin F9K1122 1.00.33. belkin · f9k1122_firmware 2025-07-06 high8.8 CVE-2025-7085 A vulnerability was found in Belkin F9K1122 1.00.33. belkin · f9k1122_firmware 2025-07-06 high8.8 CVE-2025-7084 A vulnerability was found in Belkin F9K1122 1.00.33. belkin · f9k1122_firmware 2025-07-06 medium6.3 CVE-2025-7083 A vulnerability was found in Belkin F9K1122 1.00.33. belkin · f9k1122_firmware 2025-07-06 medium6.3 CVE-2025-7082 A vulnerability was found in Belkin F9K1122 1.00.33 and classified as critical. belkin · f9k1122_firmware 2025-07-06 medium6.3 CVE-2025-7081 A vulnerability has been found in Belkin F9K1122 1.00.33 and classified as critical. belkin · f9k1122_firmware 2025-07-06 medium6.5 CVE-2023-33768 Incorrect signature verification of the firmware during the Device Firmware Update process of Belkin Wemo Smart Plug WSP080 v1.2 allows attackers to cause a De… belkin · wemo_smart_plug_wsp080_firmware 2023-07-13 critical9.8 CVE-2023-27217 A stack-based buffer overflow in the ChangeFriendlyName() function of Belkin Smart Outlet V2 F7c063 firmware_2.00.11420.OWRT.PVT_SNSV2 allows attackers to caus… belkin · f7c063_firmware 2023-05-18 critical9.8 CVE-2022-30105 In Belkin N300 Firmware 1.00.08, the script located at /setting_hidden.asp, which is accessible before and after configuring the device, exhibits multiple remo… belkin · n300_firmware 2022-05-18 high8.8 CVE-2021-25310 The administration web interface on Belkin Linksys WRT160NL 1.0.04.002_US_20130619 devices allows remote authenticated attackers to execute system commands wit… belkin · linksys_wrt160nl_firmware 2021-02-02 high7.5 CVE-2020-35716 Belkin LINKSYS RE6500 devices before 1.0.012.001 allow remote attackers to cause a persistent denial of service (segmentation fault) via a long /goform/langSwi… linksys · re6500_firmware 2020-12-26 high8.8 CVE-2020-35715 Belkin LINKSYS RE6500 devices before 1.0.012.001 allow remote authenticated users to execute arbitrary commands via shell metacharacters in a filename to the u… linksys · re6500_firmware 2020-12-26 high8.8 CVE-2020-35714 Belkin LINKSYS RE6500 devices before 1.0.11.001 allow remote authenticated users to execute arbitrary commands via goform/systemCommand?command= in conjunction… linksys · re6500_firmware 2020-12-26 critical9.8 CVE-2020-35713 Belkin LINKSYS RE6500 devices before 1.0.012.001 allow remote attackers to execute arbitrary commands or set a new password via shell metacharacters to the gof… linksys · re6500_firmware 2020-12-26 high8.8 CVE-2020-26561 Belkin LINKSYS WRT160NL 1.0.04.002_US_20130619 devices have a stack-based buffer overflow vulnerability because of sprintf in create_dir in mini_httpd. belkin · linksys_wrt_160nl_firmware 2020-10-23 medium6.1 CVE-2013-2679 Multiple cross-site scripting (XSS) vulnerabilities in Cisco Linksys E4200 router with firmware 1.0.05 build 7 allow remote attackers to inject arbitrary web s… belkin · linksys_e4200_firmware 2020-02-18 critical9.8 CVE-2013-7173 Belkin n750 routers have a buffer overflow. belkin · n750_firmware 2020-02-13 critical9.8 CVE-2013-3091 An Authentication Bypass vulnerability in Belkin N300 (F7D7301v1) router allows remote attackers to bypass authentication using "Javascript debugging." belkin · n300_firmware 2020-02-07 critical9.8 CVE-2013-2748 Belkin Wemo Switch before WeMo_US_2.00.2176.PVT could allow remote attackers to upload arbitrary files onto the system. belkin · wemo_switch_firmware 2020-01-28 high8.3 CVE-2019-17094 A Stack-based Buffer Overflow vulnerability in libbelkin_api.so component of Belkin WeMo Insight Switch firmware allows a local attacker to obtain code executi… belkin · wemo_insight_switch_firmware 2020-01-27 critical9.8 CVE-2013-3088 Belkin N900 router (F9K1104v1) contains an Authentication Bypass using "Javascript debugging". belkin · n900_firmware 2019-12-26 critical9.8 CVE-2013-3085 An authentication bypass exists in the web management interface in Belkin F5D8236-4 v2. belkin · f5d8236-4_firmware 2019-12-26 critical9.8 CVE-2019-16340 Belkin Linksys Velop 1.1.8.192419 devices allows remote attackers to discover the recovery key via a direct request for the /sysinfo_json.cgi URI. linksys · velop_whw0303_firmware, linksys · velop_whw0302_firmware, linksys · velop_whw0301_firmware 2019-11-21

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.