NetSight

Security Dashboard

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

Reset
177 matching advisories · page 1 of 6Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.1 CVE-2026-91139 Deco BE65 firmware contains a cryptographic weakness in the local web-management authentication flow due to the use of insufficient RSA key sizes. TP-Link Systems Inc. · Deco BE65 v3 3 days ago medium6.9 CVE-2026-91138 The Deco BE65 v3 firmware contains a shared hard-coded password hash for the root account in /etc/shadow. TP-Link Systems Inc. · Deco BE65 v3 3 days ago medium5.1 CVE-2026-125353 An incorrect permission assignment vulnerability in Omada SDN Controller prior to 6.2.20 may cause a database backup generated during the uninstall workflow to… TP-Link Systems Inc. · Omada SDN Controller 3 days ago medium5.3 CVE-2026-109683 A newline injection vulnerability exists in the UPnP service of Archer BE805 v1 such that an adjacent attacker can supply newline characters in a UPnP port-map… TP-Link Systems Inc. · Archer BE805 v1 15 days ago medium5.3 CVE-2026-102816 An authorization vulnerability exists in the country or region configuration interface of TP-Link RE305 V3. 25 days ago medium6.9 CVE-2026-102815 An operating-system command injection vulnerability exists in the tmpServer service of TP-Link RE305 V3. 25 days ago medium6.1 CVE-2026-102813 An authentication flaw exists in the password-recovery functionality of TP-Link RE305 V3. 25 days ago medium6.9 CVE-2026-102812 A hard-coded cryptographic key vulnerability exists in the user-configuration backup mechanism of TP-Link RE305 V3 and Archer C7 V5. 25 days ago medium6.8 CVE-2026-100420 A sensitive information disclosure vulnerability in the cloud-client daemon of Deco BE63 allows authenticated attackers to retrieve the plaintext TP-Link ID ac… 31 days ago medium5.3 CVE-2026-105814 TP-Link Tapo C210 V3.60 contains an authentication bypass vulnerability in the DS JSON API. 33 days ago medium5.9 CVE-2026-109506 Multiple TP-Link Wi-Fi range extenders use a custom, reversible XOR-and-dictionary transformation in the HTTP web-management login flow. 38 days ago medium6.8 CVE-2026-104945 TP-Link Tapo C500 v2.0 contains an out-of-bounds stack write vulnerability in its ONVIF PTZ SOAP handlers. 46 days ago medium6.1 CVE-2026-18330 A hard-coded cryptographic key vulnerability exists in TP-Link RE305 V3 and Archer C7 V5. 2026-09-03 medium4.3 CVE-2026-9033 An unauthenticated attacker with network access to the captive portal service of an affected device can terminate active captive portal sessions, including for… tp-link · er7212pc_firmware, tp-link · er605_firmware, tp-link · er7206_firmware +9 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 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 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 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 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 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 medium6.5 CVE-2026-9105 An authenticated stack-based buffer overflow vulnerability exists in the web management interface of TP-Link TL-WR841N v14. tp-link · tl-wr841n_firmware 2026-06-29 medium6.5 CVE-2026-12760 A denial-of-service (DoS) vulnerability has been identified in Tapo C200 v3 in the network packet handling logic due to improper handling of IPv4 fragmented pa… tp-link · tapo_c200_firmware 2026-06-24

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.