NetSight

Security Dashboard

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

Reset
282 matching advisories · page 5 of 10Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.3 CVE-2025-29223 Linksys E5600 v1.1.0.26 was discovered to contain a command injection vulnerability via the pt parameter in the traceRoute function. linksys · e5600_firmware 2025-03-21 high7.3 CVE-2025-25522 Buffer overflow vulnerability in Linksys WAP610N v1.0.05.002 due to the lack of length verification, which is related to the time setting operation. linksys · wap610n_firmware 2025-02-11 medium5.5 CVE-2024-57545 Linksys E8450 v1.2.00.360516 was discovered to contain a buffer overflow vulnerability. linksys · e8450_firmware 2025-01-21 medium5.5 CVE-2024-57544 Linksys E8450 v1.2.00.360516 was discovered to contain a buffer overflow vulnerability. linksys · e8450_firmware 2025-01-21 medium5.5 CVE-2024-57543 Linksys E8450 v1.2.00.360516 was discovered to contain a buffer overflow vulnerability. linksys · e8450_firmware 2025-01-21 high8.8 CVE-2024-57542 Linksys E8450 v1.2.00.360516 was discovered to contain a command injection vulnerability via the field id_email_check_btn. linksys · e8450_firmware 2025-01-21 medium5.5 CVE-2024-57541 Linksys E8450 v1.2.00.360516 was discovered to contain a buffer overflow vulnerability. linksys · e8450_firmware 2025-01-21 medium6.5 CVE-2024-57540 Linksys E8450 v1.2.00.360516 was discovered to contain a buffer overflow vulnerability. linksys · e8450_firmware 2025-01-21 high8.2 CVE-2024-57539 Linksys E8450 v1.2.00.360516 was discovered to contain a command injection vulnerability via userEmail. linksys · e8450_firmware 2025-01-21 medium6.5 CVE-2024-57538 Linksys E8450 v1.2.00.360516 was discovered to contain a buffer overflow vulnerability. linksys · e8450_firmware 2025-01-21 medium6.3 CVE-2024-57537 Linksys E8450 v1.2.00.360516 was discovered to contain a buffer overflow vulnerability. linksys · e8450_firmware 2025-01-21 high8.0 CVE-2024-57536 Linksys E8450 v1.2.00.360516 was discovered to contain a command injection vulnerability via wizard_status. linksys · e8450_firmware 2025-01-21 medium4.8 CVE-2025-22997 A stored cross-site scripting (XSS) vulnerability in the prf_table_content component of Linksys E5600 Router Ver. linksys · e5600_firmware 2025-01-15 medium4.8 CVE-2025-22996 A stored cross-site scripting (XSS) vulnerability in the spf_table_content component of Linksys E5600 Router Ver. linksys · e5600_firmware 2025-01-15 high8.0 CVE-2024-57228 Linksys E7350 1.1.00.032 was discovered to contain a command injection vulnerability via the iface parameter in the vif_disable function. linksys · e7350_firmware 2025-01-10 high8.0 CVE-2024-57227 Linksys E7350 1.1.00.032 was discovered to contain a command injection vulnerability via the ifname parameter in the apcli_do_enr_pbc_wps function. linksys · e7350_firmware 2025-01-10 high8.0 CVE-2024-57226 Linksys E7350 1.1.00.032 was discovered to contain a command injection vulnerability via the iface parameter in the vif_enable function. linksys · e7350_firmware 2025-01-10 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 medium6.3 CVE-2024-57222 Linksys E7350 1.1.00.032 was discovered to contain a command injection vulnerability via the ifname parameter in the apcli_cancel_wps function. linksys · e7350_firmware 2025-01-10 high8.0 CVE-2024-48286 Linksys E3000 1.0.06.002_US is vulnerable to command injection via the diag_ping_start function. linksys · e3000_firmware 2024-11-21 medium6.3 CVE-2024-8408 A vulnerability was found in Linksys WRT54G 4.21.5. linksys · wrt54g_firmware 2024-09-04 high8.8 CVE-2024-42633 A Command Injection vulnerability exists in the do_upgrade_post function of the httpd binary in Linksys E1500 v1.0.06.001. linksys · e1500_firmware 2024-08-19 high8.0 CVE-2024-40495 A vulnerability was discovered in Linksys Router E2500 with firmware 2.0.00, allows authenticated attackers to execute arbitrary code via the hnd_parentalctrl_… linksys · e2500_firmware 2024-07-24 high8.8 CVE-2024-41281 Linksys WRT54G v4.21.5 has a stack overflow vulnerability in get_merge_mac function. linksys · wrt54g_firmware 2024-07-19 medium5.3 CVE-2024-40750 Linksys Velop Pro 6E 1.0.8 MX6200_1.0.8.215731 and 7 1.0.10.215314 devices send cleartext Wi-Fi passwords over the public Internet during app-based installatio… linksys · mx6200_firmware, linksys · mbe7000_firmware 2024-07-09 medium6.8 CVE-2024-36821 Insecure permissions in Linksys Velop WiFi 5 (WHW01v1) 1.1.13.202617 allows attackers to escalate privileges from Guest to root. linksys · velop_whw0101_firmware 2024-06-11 high7.5 CVE-2023-30305 An issue discovered in Linksys E5600 routers allows attackers to hijack TCP sessions which could lead to a denial of service. linksys · e5600_firmware 2024-05-28 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

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.