NetSight

Security Dashboard

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

Reset
2,362 matching advisories · page 4 of 79Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.0 CVE-2025-68956 Multi-thread race condition vulnerability in the card framework module. huawei · harmonyos 2026-01-14 high8.0 CVE-2025-68955 Multi-thread race condition vulnerability in the card framework module. huawei · harmonyos 2026-01-14 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 medium4.9 CVE-2025-66330 App lock verification bypass vulnerability in the file management app. huawei · harmonyos 2025-12-08 medium4.0 CVE-2025-66329 Permission control vulnerability in the window management module. huawei · emui, huawei · harmonyos 2025-12-08 high8.4 CVE-2025-66328 Multi-thread race condition vulnerability in the network management module. huawei · harmonyos 2025-12-08 high7.1 CVE-2025-66327 Race condition vulnerability in the network module. huawei · harmonyos 2025-12-08 medium6.2 CVE-2025-66325 Permission control vulnerability in the package management module. huawei · emui, huawei · harmonyos 2025-12-08 medium4.4 CVE-2025-58279 Permission control vulnerability in the media library module. huawei · harmonyos 2025-12-08 medium6.7 CVE-2025-66326 Race condition vulnerability in the audio module. huawei · harmonyos 2025-12-08 high8.4 CVE-2025-66324 Input verification vulnerability in the compression and decompression module. huawei · harmonyos 2025-12-08 medium5.3 CVE-2025-66323 Vulnerability of improper criterion security check in the card module. huawei · harmonyos 2025-12-08 medium5.1 CVE-2025-66322 Multi-thread race condition vulnerability in the camera framework module. huawei · harmonyos 2025-12-08 medium5.1 CVE-2025-66321 Multi-thread race condition vulnerability in the camera framework module. huawei · harmonyos 2025-12-08 medium5.1 CVE-2025-66320 Multi-thread race condition vulnerability in the camera framework module. huawei · harmonyos 2025-12-08 medium4.9 CVE-2025-64312 Permission control vulnerability in the file management module. huawei · harmonyos 2025-11-28 medium5.8 CVE-2025-58311 UAF vulnerability in the USB driver module. huawei · emui, huawei · harmonyos 2025-11-28 high7.3 CVE-2025-58308 Vulnerability of improper criterion security check in the call module. huawei · harmonyos 2025-11-28 medium6.2 CVE-2025-58305 Identity authentication bypass vulnerability in the Gallery app. huawei · harmonyos 2025-11-28 medium4.9 CVE-2025-58304 Permission control vulnerability in the file management module. huawei · harmonyos 2025-11-28 high8.4 CVE-2025-58302 Permission control vulnerability in the Settings module. huawei · emui, huawei · harmonyos 2025-11-28 medium4.4 CVE-2025-64315 Configuration defect vulnerability in the file management module. huawei · harmonyos 2025-11-28 critical9.3 CVE-2025-64314 Permission control vulnerability in the memory management module. huawei · harmonyos 2025-11-28 medium5.3 CVE-2025-64313 Denial of service (DoS) vulnerability in the office service. huawei · harmonyos 2025-11-28 medium5.1 CVE-2025-64311 Permission control vulnerability in the Notepad module. huawei · harmonyos 2025-11-28 high7.3 CVE-2025-58316 DoS vulnerability in the video-related system service module. huawei · harmonyos 2025-11-28 medium5.5 CVE-2025-58315 Permission control vulnerability in the Wi-Fi module. huawei · harmonyos 2025-11-28

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.