NetSight

Security Dashboard

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

Reset
2,362 matching advisories · page 2 of 79Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.7 CVE-2026-34854 UAF vulnerability in the kernel module. huawei · harmonyos, huawei · emui 2026-04-13 low2.5 CVE-2026-34849 UAF vulnerability in the screen management module. huawei · harmonyos 2026-04-13 medium5.6 CVE-2026-34867 Double free vulnerability in the multi-mode input system. huawei · harmonyos 2026-04-13 medium4.1 CVE-2026-34860 Access control vulnerability in the memo module. huawei · harmonyos 2026-04-13 high7.3 CVE-2026-34856 UAF vulnerability in the communication module. huawei · harmonyos 2026-04-13 high7.7 CVE-2026-34853 Permission bypass vulnerability in the LBS module. huawei · harmonyos, huawei · emui 2026-04-13 medium6.1 CVE-2026-34852 Stack overflow vulnerability in the media platform. 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 medium6.9 CVE-2026-28553 Vulnerability of improper permission control in the theme setting module. huawei · harmonyos, huawei · emui 2026-04-13 medium4.7 CVE-2026-28551 Race condition vulnerability in the device security management module. huawei · harmonyos 2026-03-05 medium6.6 CVE-2026-28549 Race condition vulnerability in the permission management service. huawei · harmonyos 2026-03-05 high7.1 CVE-2026-28548 Vulnerability of improper verification in the email application. huawei · emui, huawei · harmonyos 2026-03-05 medium6.8 CVE-2026-28547 Vulnerability of uninitialized pointer access in the scanning module. huawei · harmonyos 2026-03-05 medium5.9 CVE-2026-28546 Buffer overflow vulnerability in the scanning module. huawei · harmonyos 2026-03-05 high7.3 CVE-2026-28542 Permission bypass vulnerability in the system service framework. huawei · emui, huawei · harmonyos 2026-03-05 medium6.5 CVE-2026-28552 Out-of-bounds write vulnerability in the IMS module. huawei · emui, huawei · harmonyos 2026-03-05 medium4.0 CVE-2026-28550 Race condition vulnerability in the security control module. huawei · harmonyos 2026-03-05 medium5.9 CVE-2026-28545 Race condition vulnerability in the printing module. huawei · harmonyos 2026-03-05 medium6.2 CVE-2026-28544 Race condition vulnerability in the printing module. huawei · harmonyos 2026-03-05 medium4.4 CVE-2026-28543 Race condition vulnerability in the maintenance and diagnostics module. huawei · harmonyos 2026-03-05 medium4.0 CVE-2026-28541 Permission control vulnerability in the cellular_data module. huawei · harmonyos 2026-03-05 medium4.0 CVE-2026-28540 Out-of-bounds character read vulnerability in Bluetooth. huawei · harmonyos 2026-03-05 medium6.2 CVE-2026-28539 Data processing vulnerability in the certificate management module. huawei · harmonyos 2026-03-05 medium5.9 CVE-2026-28538 Path traversal vulnerability in the certificate management module. huawei · harmonyos 2026-03-05 medium5.1 CVE-2026-28537 Double free vulnerability in the window module. huawei · harmonyos 2026-03-05 low3.3 CVE-2025-66319 Permission control vulnerability in the resource scheduling module. huawei · harmonyos 2026-03-05 critical9.6 CVE-2026-28536 Authentication bypass vulnerability in the device authentication module. huawei · harmonyos 2026-03-05 medium5.8 CVE-2026-24928 Out-of-bounds write vulnerability in the file system module. huawei · emui, huawei · harmonyos 2026-02-06 medium5.5 CVE-2026-24927 Out-of-bounds access vulnerability in the frequency modulation module. huawei · emui, huawei · harmonyos 2026-02-06

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.