NetSight

Security Dashboard

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

Reset
611 matching advisories · page 2 of 21Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.4 CVE-2026-19683 A vulnerability exists in the Dynamic DNS (DDNS) functionality of TP-Link Omada Gateways. tp-link · er7212pc_firmware, tp-link · er605_firmware, tp-link · er7206_firmware +9 2026-08-20 critical9.8 CVE-2026-19586 A pre-authentication OS command injection vulnerability has been identified in Omada gateways configured to operate as an OpenVPN Server due to insufficient va… tp-link · er7212pc_firmware, tp-link · er605_firmware, tp-link · er605w_firmware +9 2026-08-20 high7.5 CVE-2026-8619 An unauthenticated denial-of-service vulnerability was identified in TP-Link TL-MR100 v3.2, TL-MR150 v3.2, TL-MR6400 v8.0 and Archer MR600 v2, due to improper … tp-link · tl-mr100_firmware, tp-link · archer_mr600_firmware, tp-link · tl-mr150_firmware +1 2026-08-20 medium6.8 CVE-2026-75616 An OS command injection vulnerability exists in the web management interface of Archer C20 v6 firmware when processing certain WAN-related configuration operat… tp-link · archer_c20_firmware 2026-08-19 medium5.7 CVE-2026-75619 Tapo C100/C101 V5 contains a heap-based buffer overflow vulnerability in the RTSP service. tp-link · tapo_c100_firmware, tp-link · tapo_c101_firmware 2026-08-19 medium6.5 CVE-2026-75618 Tapo C100/C101 V5 contains a null pointer dereference vulnerability in the RTSP service. tp-link · tapo_c100_firmware, tp-link · tapo_c101_firmware 2026-08-19 medium6.5 CVE-2026-15316 An improper input validation vulnerability in the configuration service for processing encrypted credential data has been identified in Tapo C200 v5. tp-link · tapo_c200_firmware 2026-08-18 high8.7 CVE-2026-15315 Tapo C120 and C200 contain an improper authentication vulnerability within the login authentication verification module. tp-link · tapo_c120_firmware, tp-link · tapo_c200_firmware, TP-Link Systems Inc. · Tapo C200 v5 +4 2026-08-18 medium5.7 CVE-2026-15141 The web interface of the affected device relies on the HTTP referrer header as part of request validation. tp-link · tl-wr820n_firmware 2026-08-12 high8.6 CVE-2025-30241 Certain web interface components in affected TP-Link Aginet devices do not validate and sanitize user-supplied input properly before passing it to system-level… 2026-08-10 medium5.1 CVE-2025-30240 The affected TP-Link Aginet devices do not properly validate symbolic links created on external USB storage devices. 2026-08-10 high8.5 CVE-2025-30239 In affected TP-Link Aginet devices, use of hardcoded cryptographic keys embedded in the firmware to protect sensitive configuration data may allow an attacker … 2026-08-10 high8.6 CVE-2025-30238 In affected TP-Link Aginet devices, insufficient authorization validation allows authenticated low-privileged users to execute higher-privileged operations. 2026-08-10 high8.7 CVE-2025-30237 The affected TP-Link Aginet devices contain a flaw in the web management interface where authentication checks are not consistently enforced on certain endpoin… 2026-08-10 high7.5 CVE-2026-15314 Tapo P110 v1 smart Wi-Fi Plug contains an improper boundary validation vulnerability in the handling of authenticated HTTP request bodies due to insufficient i… tp-link · tapo_p110_firmware 2026-08-04 medium5.9 CVE-2025-15631 A cryptographic weakness exists in affected Omada devices where site credentials are protected using a legacy hashing algorithm that does not provide sufficien… tp-link · omada_fusion_2.5g_firmware, tp-link · omada_er707-m2_firmware, tp-link · omada_er7206_firmware +9 2026-08-03 medium5.9 CVE-2025-15630 A race condition exists in the cloud-based Omada device adoption process when an attacker may be able to interact with the adoption workflow before a legitimat… tp-link · omada_oc200_v3_firmware, tp-link · omada_oc300_firmware, tp-link · omada_oc400_firmware +9 2026-08-03 high7.5 CVE-2025-15629 A cryptographic weakness exists in the Omada adoption protocol where session encryption keys used to protect communications between controllers and managed dev… tp-link · omada_oc200_v3_firmware, tp-link · omada_oc300_firmware, tp-link · omada_oc400_firmware +9 2026-08-03 high7.5 CVE-2025-15628 Affected Omada devices rely on embedded certificates that are shared across deployments to establish trust between controllers and managed devices. tp-link · omada_oc200_v3_firmware, tp-link · omada_oc300_firmware, tp-link · omada_oc400_firmware +9 2026-08-03 high7.5 CVE-2025-15627 A cryptographic weakness exists in the Omada adoption protocol. tp-link · omada_oc200_v3_firmware, tp-link · omada_oc300_firmware, tp-link · omada_oc400_firmware +9 2026-08-03 medium5.9 CVE-2025-15544 A cryptographic weakness exists in the Omada device adoption process. tp-link · omada_oc200_v3_firmware, tp-link · omada_oc300_firmware, tp-link · omada_oc400_firmware +9 2026-08-03 medium6.5 CVE-2025-9291 A certification validation weakness exists in communication between affected Omada devices and cloud controllers. tp-link · omada_fusion_2.5g_firmware, tp-link · omada_er707-m2_firmware, tp-link · omada_er7206_firmware +9 2026-08-03 high8.0 CVE-2026-9044 An OS command injection vulnerability exists in the VPN module of TP-Link AXE75 V1 routers. tp-link · archer_axe75_firmware 2026-07-31 medium5.2 CVE-2026-12001 A hardcoded credential vulnerability exists in the firmware of multiple TP-Link routers (TL-WR845N v4, TL-WR850N v3, TL-WR902AC v4, Archer C20 v6 & Archer MR20… 2026-07-27 medium5.3 CVE-2026-9770 Kasa EC71 v4 and EC70 v4 firmware contains a static cryptographic private key stored in a read-only filesystem that is shared across devices. tp-link · kasa_ec71_firmware, tp-link · kasa_ec70_firmware 2026-07-15 medium6.5 CVE-2026-13230 An information disclosure vulnerability was identified in TP-Link Kasa EC70 v4 and EC71 v4 in the local discovery mechanism, which exposes sensitive geolocatio… tp-link · kasa_ec70_firmware, tp-link · kasa_ec71_firmware 2026-07-15 medium6.7 CVE-2026-5040 TP-Link Deco M5 v1 uses a weak password hashing mechanism to store user credentials. tp-link · deco_m5_firmware 2026-07-14 high8.8 CVE-2026-15429 A privilege escalation vulnerability exists in the HTTP authentication component in Archer VX1800v v1. tp-link · archer_vx1800v_firmware 2026-07-14 high8.8 CVE-2026-15428 An OS command injection vulnerability exists in Archer VX800v v1 due to insufficient input sanitization of the domain name parameter. tp-link · archer_vx1800v_firmware 2026-07-14 high8.1 CVE-2026-15427 An OS command injection vulnerability exists in the TR-069 / CWMP management interface of Archer VX1800v v1 due to insufficient input validation and sanitizati… tp-link · archer_vx1800v_firmware 2026-07-14

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.