NetSight

Security Dashboard

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

Reset
121 matching advisories · page 1 of 5Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.7 CVE-2026-101177 Permission control vulnerability in the Optimizer module. Impact: Successful exploitation of this... Huawei · HarmonyOS, Huawei · EMUI 19 days ago low3.6 CVE-2026-101171 Permission control vulnerability in the background task management module. Impact: Successful... Huawei · HarmonyOS 19 days ago low2.5 CVE-2026-34849 UAF vulnerability in the screen management module. huawei · harmonyos 2026-04-13 low2.2 CVE-2026-34851 Race condition vulnerability in the event notification module. huawei · harmonyos 2026-04-13 low1.9 CVE-2026-34850 Race condition vulnerability in the notification service. huawei · harmonyos 2026-04-13 low3.3 CVE-2025-66319 Permission control vulnerability in the resource scheduling module. huawei · harmonyos 2026-03-05 low3.3 CVE-2025-66334 Denial of service (DoS) vulnerability in the office service. huawei · harmonyos 2025-12-08 low3.3 CVE-2025-66333 Denial of service (DoS) vulnerability in the office service. huawei · harmonyos 2025-12-08 low3.3 CVE-2025-66332 Denial of service (DoS) vulnerability in the office service. huawei · harmonyos 2025-12-08 low3.3 CVE-2025-66331 Denial of service (DoS) vulnerability in the office service. huawei · harmonyos 2025-12-08 low3.3 CVE-2025-58292 Denial of service (DoS) vulnerability in the office service. huawei · harmonyos 2025-10-11 low3.3 CVE-2025-58291 Denial of service (DoS) vulnerability in the office service. huawei · harmonyos 2025-10-11 low3.3 CVE-2025-58290 Denial of service (DoS) vulnerability in the office service. huawei · harmonyos 2025-10-11 low3.3 CVE-2025-58286 Denial of service (DoS) vulnerability in the office service. huawei · harmonyos 2025-10-11 low2.8 CVE-2025-58282 Permission control vulnerability in the camera module. huawei · harmonyos 2025-10-11 low3.9 CVE-2025-53177 Permission bypass vulnerability in the calendar storage module Impact: Successful exploitation of this vulnerability may affect the schedule syncing function o… huawei · emui, huawei · harmonyos 2025-07-07 low3.3 CVE-2025-53176 Stack overflow risk when vector images are parsed during file preview Impact: Successful exploitation of this vulnerability may affect the file preview functio… huawei · harmonyos 2025-07-07 low2.8 CVE-2024-57956 Out-of-bounds read vulnerability in the interpreter string module Impact: Successful exploitation of this vulnerability may affect availability. huawei · harmonyos 2025-02-06 low3.7 CVE-2020-1824 There are multiple out of bounds (OOB) read vulnerabilities in the implementation of the Common Open Policy Service (COPS) protocol of some Huawei products. huawei · ips_module_firmware, huawei · ngfw_module_firmware, huawei · nip6300_firmware +6 2024-12-28 low3.7 CVE-2020-1823 There are multiple out of bounds (OOB) read vulnerabilities in the implementation of the Common Open Policy Service (COPS) protocol of some Huawei products. huawei · ips_module_firmware, huawei · ngfw_module_firmware, huawei · nip6300_firmware +6 2024-12-28 low3.7 CVE-2020-1822 There are multiple out of bounds (OOB) read vulnerabilities in the implementation of the Common Open Policy Service (COPS) protocol of some Huawei products. huawei · ips_module_firmware, huawei · ngfw_module_firmware, huawei · nip6300_firmware +6 2024-12-28 low3.7 CVE-2020-1821 There are multiple out of bounds (OOB) read vulnerabilities in the implementation of the Common Open Policy Service (COPS) protocol of some Huawei products. huawei · ips_module_firmware, huawei · ngfw_module_firmware, huawei · nip6300_firmware +6 2024-12-28 low3.7 CVE-2020-1820 There are multiple out of bounds (OOB) read vulnerabilities in the implementation of the Common Open Policy Service (COPS) protocol of some Huawei products. huawei · ips_module_firmware, huawei · ngfw_module_firmware, huawei · nip6300_firmware +6 2024-12-28 low3.3 CVE-2020-9089 There is an information vulnerability in Huawei smartphones. huawei · p30_pro_firmware 2024-12-27 low3.5 CVE-2020-9082 There is an information disclosure vulnerability in several smartphones. huawei · mate_20_firmware 2024-12-27 low3.5 CVE-2020-9081 There is an improper authorization vulnerability in some Huawei smartphones. huawei · mate_20_firmware, huawei · p30_firmware, huawei · p30_pro_firmware +4 2024-12-27 low3.7 CVE-2020-1819 There are multiple out of bounds (OOB) read vulnerabilities in the implementation of the Common Open Policy Service (COPS) protocol of some Huawei products. huawei · ips_module_firmware, huawei · ngfw_module_firmware, huawei · nip6300_firmware +6 2024-12-27 low3.7 CVE-2020-1818 There are multiple out of bounds (OOB) read vulnerabilities in the implementation of the Common Open Policy Service (COPS) protocol of some Huawei products. huawei · ips_module_firmware, huawei · ngfw_module_firmware, huawei · nip6300_firmware +6 2024-12-27 low3.3 CVE-2020-9250 There is an insufficient authentication vulnerability in some Huawei smart phone. huawei · mate_20_pro_firmware 2024-12-20 low2.5 CVE-2024-42036 Access permission verification vulnerability in the Notepad module Impact: Successful exploitation of this vulnerability may affect service confidentiality. huawei · emui, huawei · harmonyos 2024-08-08

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.