NetSight

Security Dashboard

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

Reset
179 matching advisories · page 1 of 6Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2026-118871 SQL injection vulnerability classified as an internal threat level.Attackers can steal database information via SQL injection while logged in. ZTE · ElasticNet RNIA R18 NGI 19 days ago medium5.5 CVE-2026-108506 ZTE Z80 Ultra's system interfaces do not have robust invocation authentication, with inadequate access control. 42 days ago medium5.5 CVE-2026-108504 ZTE Z80 Ultra has an unauthorized information disclosure vulnerability. 42 days ago medium5.7 CVE-2026-108501 ZTE Z80 Ultra has a system interface permission verification defect. 43 days ago medium5.3 CVE-2026-86556 There is an information disclosure vulnerability in ZTE U30 Air. 53 days ago medium6.2 CVE-2026-86555 The ZTE SmartLife application has a hardcoded key. 2026-09-20 medium5.4 CVE-2026-11466 A weakness has been identified in zilliztech deep-searcher up to 0.0.2. pip · deepsearcher 2026-06-07 medium6.3 CVE-2026-10279 A vulnerability was identified in hiraishikentaro wezterm-mcp 0.1.0. 2026-06-01 medium5.7 CVE-2026-44409 There is an an information disclosure vulnerability in ZTE MU5250. zte · mu5250_firmware 2026-05-22 medium6.3 CVE-2026-44408 There is an unauthorized access vulnerability in ZTE MU5250. 2026-05-19 medium4.7 CVE-2026-44407 A remote denial-of-service vulnerability exists in the ZTE Cloud PC client uSmartview, which may lead to memory corruption and remote denial of service. zte · zxcloud_irai 2026-05-07 medium5.7 CVE-2026-44406 ZTE Cloud PC client uSmartView contains a DLL hijacking vulnerability; since uSmartViewServiceAgent.exe runs with SYSTEM privileges, successful hijacking enabl… zte · zxcloud_irai 2026-05-07 medium5.5 CVE-2026-40004 There exists an openssl.cnf privilege escalation vulnerability in ZTE Cloud PC client uSmartview. zte · zxcloud_irai 2026-05-07 medium5.1 CVE-2026-40003 ZTE ZX297520V3 BootROM contains a vulnerability that allows arbitrary memory writes via USB. zte · zx297520v3_firmware 2026-05-07 medium5.2 CVE-2026-40001 There is a local privilege escalation vulnerability in the ZTE PROCESS Guard service of the cloud computer client, which may allow local arbitrary code executi… 2026-05-06 medium5.0 CVE-2026-40002 Red Magic 11 Pro (NX809J) contains a vulnerability that allows non-privileged applications to trigger sensitive operations. zte · nubia-in_nx809j_firmware 2026-04-17 medium4.3 CVE-2025-66315 There is a configuration defect vulnerability in the version server of ZTE MF258K Pro products. zte · mf258k_pro_firmware 2026-01-09 medium5.3 CVE-2025-46583 There is a Denial of Service(DoS)vulnerability in the ZTE MC889A Pro product. 2025-10-27 medium5.7 CVE-2025-26711 There is an unauthorized access vulnerability in ZTE T5400. 2025-09-16 medium5.7 CVE-2025-26709 There is an unauthorized access vulnerability in ZTE F50. 2025-08-15 medium6.5 CVE-2025-46578 There are SQL injection vulnerabilities in multiple interfaces of the GoldenDB database product. zte · zxcloud_goldendb 2025-04-27 medium6.5 CVE-2025-46577 There is a SQL injection vulnerability in the GoldenDB database product. zte · zxcloud_goldendb 2025-04-27 medium5.4 CVE-2025-46576 There is a Permission Management and Access Control vulnerability in the GoldenDB database product. zte · zxcloud_goldendb 2025-04-27 medium4.9 CVE-2025-46575 There is an information disclosure vulnerability in the GoldenDB database product. zte · zxcloud_goldendb 2025-04-27 medium4.1 CVE-2025-46574 There is an information disclosure vulnerability in the GoldenDB database product. zte · zxcloud_goldendb 2025-04-27 medium5.4 CVE-2025-26706 Improper Privilege Management vulnerability in ZTE GoldenDB allows Privilege Escalation.This issue affects GoldenDB: from 6.1.03 through 6.1.03.07. zte · goldendb 2025-03-11 medium5.3 CVE-2025-26705 Improper Privilege Management vulnerability in ZTE GoldenDB allows Privilege Escalation.This issue affects GoldenDB: from 6.1.03 through 6.1.03.05. zte · goldendb 2025-03-11 medium6.4 CVE-2025-26704 Improper Privilege Management vulnerability in ZTE GoldenDB allows Privilege Escalation.This issue affects GoldenDB: from 6.1.03 through 6.1.03.05. zte · goldendb 2025-03-11 medium4.3 CVE-2025-26703 Improper Privilege Management vulnerability in ZTE GoldenDB allows Privilege Escalation.This issue affects GoldenDB: from 6.1.03 through 6.1.03.04. zte · goldendb 2025-03-11 medium4.9 CVE-2025-26702 Improper Input Validation vulnerability in ZTE GoldenDB allows Input Data Manipulation.This issue affects GoldenDB: from 6.1.03 through 6.1.03.04. zte · goldendb 2025-03-11

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.