NetSight

Security Dashboard

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

Reset
47 matching advisories · page 1 of 2Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical10.0 CVE-2026-127277 A security flaw has been discovered in Linksys EA8100 1.0.3.216940. The affected element is an... Linksys · EA8100 9 days ago critical10.0 CVE-2026-127275 A vulnerability was determined in Linksys EA8100 1.0.3.216940. This issue affects the function... Linksys · EA8100 9 days ago critical10.0 CVE-2026-121933 A flaw has been found in Linksys E5350 1.0.00.037. Linksys · E5350 17 days ago critical10.0 CVE-2026-121932 A vulnerability was detected in Linksys E5350 1.0.00.037. Linksys · E5350 17 days ago critical9.1 CVE-2026-121931 A security vulnerability has been detected in Linksys WRT54GL 4.30.18. Linksys · WRT54GL 17 days ago critical9.1 CVE-2026-121930 A weakness has been identified in Linksys WRT54GL 4.30.18. Linksys · WRT54GL 17 days ago critical10.0 CVE-2026-121615 A vulnerability was determined in Linksys E5600 1.1.0.26. Affected is an unknown function of the... Linksys · E5600 18 days ago critical10.0 CVE-2026-120283 A vulnerability was identified in Linksys E8450 1.2.00.360516. Affected is the function strcpy of... Linksys · E8450 20 days ago critical9.9 CVE-2026-108896 A vulnerability was found in Linksys E1700 1.0.0.4.003. 40 days ago critical9.9 CVE-2026-108895 A weakness has been identified in Linksys E1700 1.0.0.4.003. 40 days ago critical9.9 CVE-2026-108894 A security flaw has been discovered in Linksys E1700 1.0.0.4.003. 40 days ago critical9.9 CVE-2026-108893 A vulnerability was identified in Linksys E1700 up to 1.0.0.4.003. Linksys E1700 40 days ago critical10.0 CVE-2026-108892 A vulnerability was determined in Linksys E1700 1.0.0.4.003. 40 days ago critical9.9 CVE-2026-86299 A vulnerability was detected in Linksys RE7000 2.0.15. 2026-09-07 critical9.8 CVE-2025-29229 linksys E5600 V1.1.0.26 is vulnerable to command injection in the function ddnsStatus. linksys · e5600_firmware 2025-12-23 critical9.8 CVE-2025-29228 Linksys E5600 V1.1.0.26 is vulnerable to command injection in the runtime.macClone function via the mc.ip parameter. linksys · e5600_firmware 2025-12-23 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 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 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 critical9.8 CVE-2024-57225 Linksys E7350 1.1.00.032 was discovered to contain a command injection vulnerability via the devname parameter in the reset_wifi function. linksys · e7350_firmware 2025-01-10 critical9.8 CVE-2024-57224 Linksys E7350 1.1.00.032 was discovered to contain a command injection vulnerability via the ifname parameter in the apcli_do_enr_pin_wps function. linksys · e7350_firmware 2025-01-10 critical9.8 CVE-2024-57223 Linksys E7350 1.1.00.032 was discovered to contain a command injection vulnerability via the ifname parameter in the apcli_wps_gen_pincode function. linksys · e7350_firmware 2025-01-10 critical9.8 CVE-2023-46012 Buffer Overflow vulnerability LINKSYS EA7500 3.0.1.207964 allows a remote attacker to execute arbitrary code via an HTTP request to the IGD UPnP. linksys · ea7500_firmware 2024-05-07 critical9.8 CVE-2024-33789 Linksys E5600 v1.1.0.26 was discovered to contain a command injection vulnerability via the ipurl parameter at /API/info form endpoint. linksys · e5600_firmware 2024-05-03 critical9.8 CVE-2022-38555 Linksys E1200 v1.0.04 is vulnerable to Buffer Overflow via ej_get_web_page_name. linksys · e1200_firmware 2022-08-28 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

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.