NetSight

Security Dashboard

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

Reset
55 matching advisories · page 2 of 2Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
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 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 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 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 high7.5 CVE-2013-4655 Symlink Traversal vulnerability in Belkin N900 due to misconfiguration in the SMB service. belkin · n900_firmware 2019-11-13 high7.5 CVE-2019-17532 An issue was discovered on Belkin Wemo Switch 28B WW_2.00.11057.PVT-OWRT-SNS devices. belkin · wemo_switch_28b_firmware 2019-10-12 high7.5 CVE-2018-1146 A remote unauthenticated user can enable telnet on the Belkin N750 using firmware version 1.10.22 by sending a crafted HTTP request to set.cgi. belkin · n750_firmware 2018-04-19 high8.8 CVE-2015-5990 Cross-site request forgery (CSRF) vulnerability on Belkin F9K1102 2 devices with firmware 2.10.17 allows remote attackers to hijack the authentication of arbit… zyxel · gs1900-10hp_firmware 2015-12-31 high8.6 CVE-2015-5987 Belkin F9K1102 2 devices with firmware 2.10.17 use an improper algorithm for selecting the ID value in the header of a DNS query, which makes it easier for rem… zyxel · gs1900-10hp_firmware 2015-12-31 high8.3 CVE-2013-3092 The Belkin N300 (F7D7301v1) router allows remote attackers to bypass authentication and gain privileges via vectors related to incorrect validation of the HTTP… belkin · n300_firmware, belkin · n300 2014-09-29 high7.8 CVE-2014-2962 Absolute path traversal vulnerability in the webproc cgi module on the Belkin N150 F9K1009 v1 router with firmware before 1.00.08 allows remote attackers to re… belkin · n150_f9k1009_firmware, belkin · n150_f9k1009 2014-06-19 high7.1 CVE-2013-6951 The Belkin WeMo Home Automation firmware before 3949 does not maintain a set of Certification Authority public keys, which allows man-in-the-middle attackers t… belkin · wemo_home_automation_firmware 2014-02-22 high7.8 CVE-2013-6950 The Belkin WeMo Home Automation firmware before 3949 does not use SSL for the distribution feed, which allows man-in-the-middle attackers to install arbitrary … belkin · wemo_home_automation_firmware 2014-02-22 high7.8 CVE-2013-6948 The peerAddresses API in the Belkin WeMo Home Automation firmware before 3949 allows remote attackers to read arbitrary files via an XML document containing an… belkin · wemo_home_automation_firmware 2014-02-22 high7.8 CVE-2008-1245 cgi-bin/setup_virtualserver.exe on the Belkin F5D7230-4 router with firmware 9.01.10 allows remote attackers to cause a denial of service (control center outag… belkin · f5d7230-4 2008-03-10 high7.5 CVE-2005-2374 Belkin 54g wireless routers do not properly set an administrative password, which allows remote attackers to gain access via the (1) Telnet or (2) web administ… belkin · belkin_54g_wireless_router 2005-07-26 high7.5 CVE-2005-0833 Belkin 54G (F5D7130) wireless router allows remote attackers to access restricted resources by sniffing URIs from UPNP datagrams, then accessing those URIs, wh… belkin · belkin_54g_wireless_router 2005-05-02 high7.5 CVE-2002-1431 Belkin F5D5230-4 4-Port Cable/DSL Gateway Router 1.20.000 modifies the source IP address of internal packets to that of the router's external interface when fo… belkin · f5d5230-4_4-port_cable_dsl_gateway_router 2003-04-11

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.