NetSight

Security Dashboard

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

Reset
282 matching advisories · page 4 of 10Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.8 CVE-2025-8816 A vulnerability was determined in Linksys RE6250, RE6300, RE6350, RE6500, RE7000 and RE9000 up to 20250801. linksys · re6250_firmware, linksys · re6300_firmware, linksys · re6350_firmware +3 2025-08-10 medium6.9 CVE-2013-10062 A directory traversal vulnerability exists in Linksys router's web interface (tested on the E1500 model firmware versions 1.0.00, 1.0.04, and 1.0.05), specific… 2025-08-01 high8.6 CVE-2013-10058 An authenticated OS command injection vulnerability exists in various Linksys router models (tested on WRT160Nv2) running firmware version v2.0.03 via the appl… 2025-08-01 medium5.3 CVE-2014-125122 A stack-based buffer overflow vulnerability exists in the tmUnblock.cgi endpoint of the Linksys WRT120N wireless router. 2025-07-31 critical9.8 CVE-2025-44654 In Linksys E2500 3.0.04.002, the chroot_local_user option is enabled in the vsftpd configuration file. linksys · e2500_firmware 2025-07-21 low3.9 CVE-2025-44657 In Linksys EA6350 V2.1.2, the chroot_local_user option is enabled in the dynamically generated vsftpd configuration file. linksys · ea6350_firmware 2025-07-21 high8.3 CVE-2013-3307 Linksys E1000 devices through 2.1.02, E1200 devices before 2.0.05, and E3200 devices through 1.0.04 allow OS command injection via shell metacharacters in the … Linksys E1000 devices, E1200 devices, E3200 devices 2025-07-11 high8.8 CVE-2025-6752 A vulnerability has been found in Linksys WRT1900ACS, EA7200, EA7450 and EA7500 up to 20250619 and classified as critical. 2025-06-27 high8.8 CVE-2025-6751 A vulnerability, which was classified as critical, was found in Linksys E8450 up to 1.2.00.360516. Linksys E8450 2025-06-27 critical10.0 CVE-2025-34037 An OS command injection vulnerability exists in various models of E-Series Linksys routers via the /tmUnblock.cgi and /hndUnblock.cgi endpoints over HTTP on po… 2025-06-24 medium6.3 CVE-2025-5447 A vulnerability was found in Linksys RE6500, RE6250, RE6300, RE6350, RE7000 and RE9000 1.0.013.001/1.0.04.001/1.0.04.002/1.1.05.003/1.2.07.001. linksys · re9000_firmware, linksys · re6250_firmware, linksys · re6300_firmware +3 2025-06-02 medium6.3 CVE-2025-5446 A vulnerability was found in Linksys RE6500, RE6250, RE6300, RE6350, RE7000 and RE9000 1.0.013.001/1.0.04.001/1.0.04.002/1.1.05.003/1.2.07.001. linksys · re9000_firmware, linksys · re6250_firmware, linksys · re6300_firmware +3 2025-06-02 medium6.3 CVE-2025-5445 A vulnerability was found in Linksys RE6500, RE6250, RE6300, RE6350, RE7000 and RE9000 1.0.013.001/1.0.04.001/1.0.04.002/1.1.05.003/1.2.07.001 and classified a… linksys · re9000_firmware, linksys · re6250_firmware, linksys · re6300_firmware +3 2025-06-02 medium6.3 CVE-2025-5444 A vulnerability has been found in Linksys RE6500, RE6250, RE6300, RE6350, RE7000 and RE9000 1.0.013.001/1.0.04.001/1.0.04.002/1.1.05.003/1.2.07.001 and classif… linksys · re9000_firmware, linksys · re6250_firmware, linksys · re6300_firmware +3 2025-06-02 medium6.3 CVE-2025-5443 A vulnerability, which was classified as critical, was found in Linksys RE6500, RE6250, RE6300, RE6350, RE7000 and RE9000 1.0.013.001/1.0.04.001/1.0.04.002/1.1… linksys · re9000_firmware, linksys · re6250_firmware, linksys · re6300_firmware +3 2025-06-02 medium6.3 CVE-2025-5442 A vulnerability, which was classified as critical, has been found in Linksys RE6500, RE6250, RE6300, RE6350, RE7000 and RE9000 1.0.013.001/1.0.04.001/1.0.04.00… linksys · re9000_firmware, linksys · re6250_firmware, linksys · re6300_firmware +3 2025-06-02 medium6.3 CVE-2025-5441 A vulnerability classified as critical was found in Linksys RE6500, RE6250, RE6300, RE6350, RE7000 and RE9000 1.0.013.001/1.0.04.001/1.0.04.002/1.1.05.003/1.2.… linksys · re9000_firmware, linksys · re6250_firmware, linksys · re6300_firmware +3 2025-06-02 medium6.3 CVE-2025-5440 A vulnerability classified as critical has been found in Linksys RE6500, RE6250, RE6300, RE6350, RE7000 and RE9000 1.0.013.001/1.0.04.001/1.0.04.002/1.1.05.003… linksys · re9000_firmware, linksys · re6250_firmware, linksys · re6300_firmware +3 2025-06-02 medium6.3 CVE-2025-5439 A vulnerability was found in Linksys RE6500, RE6250, RE6300, RE6350, RE7000 and RE9000 1.0.013.001/1.0.04.001/1.0.04.002/1.1.05.003/1.2.07.001. linksys · re9000_firmware, linksys · re6250_firmware, linksys · re6300_firmware +3 2025-06-02 medium6.3 CVE-2025-5438 A vulnerability was found in Linksys RE6500, RE6250, RE6300, RE6350, RE7000 and RE9000 1.0.013.001/1.0.04.001/1.0.04.002/1.1.05.003/1.2.07.001. linksys · re9000_firmware, linksys · re6250_firmware, linksys · re6300_firmware +3 2025-06-02 medium6.3 CVE-2025-5000 A vulnerability was found in Linksys FGW3000-AH and FGW3000-HK up to 1.0.17.000000. linksys · fgw3000-ah_firmware, linksys · fgw3000-hk_firmware 2025-05-20 medium6.3 CVE-2025-4999 A vulnerability was found in Linksys FGW3000-AH and FGW3000-HK up to 1.0.17.000000 and classified as critical. linksys · fgw3000-ah_firmware, linksys · fgw3000-hk_firmware 2025-05-20 critical9.8 CVE-2025-45491 Linksys E5600 v1.1.0.26 was discovered to contain a command injection vulnerability in the runtime.ddnsStatus DynDNS function via the username parameter. linksys · e5600_firmware 2025-05-06 critical9.8 CVE-2025-45490 Linksys E5600 v1.1.0.26 was discovered to contain a command injection vulnerability in the runtime.ddnsStatus DynDNS function via the password parameter. linksys · e5600_firmware 2025-05-06 critical9.8 CVE-2025-45489 Linksys E5600 v1.1.0.26 was discovered to contain a command injection vulnerability in the runtime.ddnsStatus DynDNS function via the hostname parameter. linksys · e5600_firmware 2025-05-06 critical9.8 CVE-2025-45488 Linksys E5600 v1.1.0.26 was discovered to contain a command injection vulnerability in the runtime.ddnsStatus DynDNS function via the mailex parameter. linksys · e5600_firmware 2025-05-06 critical9.8 CVE-2025-45487 Linksys E5600 v1.1.0.26 was discovered to contain a command injection vulnerability in the runtime.InternetConnection function. linksys · e5600_firmware 2025-05-06 high8.6 CVE-2025-29230 Linksys E5600 v1.1.0.26 was discovered to contain a command injection vulnerability in the runtime.emailReg function. linksys · e5600_firmware 2025-03-21 medium6.3 CVE-2025-29227 In Linksys E5600 V1.1.0.26, the \usr\share\lua\runtime.lua file contains a command injection vulnerability in the runtime.pingTest function via the pt["pkgsize… linksys · e5600_firmware 2025-03-21 medium6.3 CVE-2025-29226 In Linksys E5600 V1.1.0.26, the \usr\share\lua\runtime.lua file contains a command injection vulnerability in the runtime.pingTest function via the pt["count"]… linksys · e5600_firmware 2025-03-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.