NetSight

Security Dashboard

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

Reset
177 matching advisories · page 2 of 6Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2026-8714 A denial-of-service vulnerability exists in the RTSP server component of TP-Link Tapo C520WS v2 due to improper handling of syntactically invalid input. tp-link · tapo_c520ws_firmware 2026-06-05 medium6.5 CVE-2026-1871 TP-Link Tapo C200 v5 contains a stack-based buffer overflow flaw in RTSP authentication handling due to improper validation of Authorization header field lengt… tp-link · tapo_c200_firmware 2026-06-02 medium4.8 CVE-2026-34127 A stored cross-site scripting (XSS) vulnerability has been identified in the web management interface of TP-Link's TL-SG108PE v5 switch due to improper sanitat… tp-link · tl-sg108pe_firmware 2026-05-29 medium4.3 CVE-2018-25321 TP-Link TL-WR720N wireless router contains a cross-site request forgery vulnerability that allows attackers to perform unauthorized administrative actions by c… tp-link · tl-wr720n_firmware 2026-05-17 medium5.7 CVE-2026-30817 An external configuration control vulnerability in the OpenVPN module of TP-Link AX53 v1.0 allows an authenticated adjacent attacker to read arbitrary files wh… tp-link · archer_ax53_firmware 2026-04-08 medium5.7 CVE-2026-30816 An external control of configuration vulnerability in the OpenVPN module of TP-Link AX53 v1.0 allows an authenticated adjacent attacker to read arbitrary file … tp-link · archer_ax53_firmware 2026-04-08 medium6.5 CVE-2026-34124 A denial-of-service vulnerability was identified in TP-Link Tapo C520WS v2.6 within the HTTP request path parsing logic. tp-link · tapo_c520ws_firmware 2026-04-02 medium6.5 CVE-2026-34122 A stack-based buffer overflow vulnerability was identified in TP-Link Tapo C520WS v2.6 within a configuration handling component due to insufficient input vali… tp-link · tapo_c520ws_firmware 2026-04-02 medium6.5 CVE-2026-34120 A heap-based buffer overflow vulnerability was identified in TP-Link Tapo C520WS v2.6 within the asynchronous parsing of local video stream content due to insu… tp-link · tapo_c520ws_firmware 2026-04-02 medium6.5 CVE-2026-34119 A heap-based buffer overflow vulnerability was identified in TP-Link Tapo C520WS v2.6 within the HTTP parsing loop when appending segmented request bodies with… tp-link · tapo_c520ws_firmware 2026-04-02 medium6.8 CVE-2026-4346 The vulnerability affecting TL-WR850N v3 allows cleartext storage of administrative and Wi-Fi credentials in a region of the device’s flash memory while the se… tp-link · tl-wr850n_firmware 2026-03-26 medium6.8 CVE-2026-3227 A command injection vulnerability was identified in TP-Link TL-WR802N v4, TL-WR841N v14, and TL-WR840N v6 due to improper neutralization of special elements us… tp-link · tl-wr802n_firmware, tp-link · tl-wr841n_firmware, tp-link · tl-wr840n_firmware 2026-03-16 medium6.5 CVE-2025-7375 A denial-of-service (DoS) vulnerability was identified in Omada EAP610 v3. tp-link · omada_eap610_firmware 2026-03-05 medium6.1 CVE-2026-1571 User-controlled input is reflected into the HTML output without proper encoding on TP-Link Archer C60 v3, allowing arbitrary JavaScript execution via a crafted… tp-link · archer_c60_firmware 2026-02-11 medium6.5 CVE-2026-0653 On TP-Link Tapo C260 v1 and D235 v1, a guest‑level authenticated user can bypass intended access restrictions by sending crafted requests to a synchronization … tp-link · tapo_c260_firmware 2026-02-10 medium5.6 CVE-2025-15551 The response coming from TP-Link Archer MR200 v5.2, C20 v5 and v6, TL-WR850N v3, and TL-WR845N v4 for any request is getting executed by the JavaScript functio… tp-link · archer_mr200_firmware, tp-link · archer_c20_firmware, tp-link · tl-wr850n_firmware +1 2026-02-05 medium4.9 CVE-2026-22228 An authenticated user with high privileges may trigger a denial‑of‑service condition in TP-Link Archer BE230 v1.2 by restoring a crafted configuration file con… tp-link · archer_be230_firmware 2026-02-03 medium4.5 CVE-2026-22220 A lack of proper input validation in the HTTP processing path in TP-Link Archer BE230 v1.2 (web modules) may allow a crafted request to cause the device’s web … tp-link · archer_be230_firmware 2026-02-03 medium6.5 CVE-2025-15548 Some VX800v v1.0 web interface endpoints transmit sensitive information over unencrypted HTTP due to missing application layer encryption, allowing a network a… tp-link · vx800v_firmware 2026-01-29 medium4.6 CVE-2025-15543 Improper link resolution in USB HTTP access path in VX800v v1.0 allows a crafted USB device to expose root filesystem contents, giving an attacker with physica… tp-link · vx800v_firmware 2026-01-29 medium5.3 CVE-2025-15542 Improper handling of exceptional conditions in VX800v v1.0 in SIP processing allows an attacker to flood the device with crafted INVITE messages, blocking all … tp-link · vx800v_firmware 2026-01-29 medium6.3 CVE-2025-15541 Improper link resolution in the VX800v v1.0 SFTP service allows authenticated adjacent attackers to use crafted symbolic links to access system files, resultin… tp-link · vx800v_firmware 2026-01-29 medium6.8 CVE-2025-15545 The backup restore function does not properly validate unexpected or unrecognized tags within the backup file. tp-link · archer_re605x_firmware 2026-01-29 medium5.3 CVE-2025-9522 Blind Server-Side Request Forgery (SSRF) in Omada Controllers through webhook functionality, enabling crafted requests to internal services, which may lead to … tp-link · omada_controller 2026-01-26 medium6.5 CVE-2025-9521 Password Confirmation Bypass vulnerability in Omada Controllers, allowing an attacker with a valid session token to bypass secondary verification, and change t… tp-link · omada_controller 2026-01-26 medium6.8 CVE-2025-9520 An IDOR vulnerability exists in Omada Controllers that allows an attacker with Administrator permissions to manipulate requests and potentially hijack the Owne… tp-link · omada_controller 2026-01-26 medium5.9 CVE-2025-9290 An authentication weakness was identified in Omada Controllers, Gateways and Access Points, controller-device adoption due to improper handling of random value… tp-link · omada_controller, tp-link · oc200_firmware, tp-link · oc220_firmware +9 2026-01-23 medium4.7 CVE-2025-9289 A Cross-Site Scripting (XSS) vulnerability was identified in a parameter in Omada Controllers due to improper input sanitization. tp-link · omada_controller, tp-link · oc200_firmware, tp-link · oc220_firmware +2 2026-01-22 medium6.5 CVE-2025-14631 A NULL Pointer Dereference vulnerability in TP-Link Archer BE400 V1(802.11 modules) allows an adjacent attacker to cause a denial-of-service (DoS) by triggerin… tp-link · archer_be400_firmware 2026-01-07 medium6.5 CVE-2025-14175 A vulnerability in the SSH server of TP-Link TL-WR820N v2.80 allows the use of a weak cryptographic algorithm, enabling an adjacent attacker to intercept and d… tp-link · tl-wr820n_firmware 2025-12-29

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.