NetSight

Security Dashboard

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

Reset
1,430 matching advisories · page 17 of 48Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.5 CVE-2025-39794 In the Linux kernel, the following vulnerability has been resolved: ARM: tegra: Use I/O memcpy to write to IRAM Kasan crashes the kernel trying to check bounda… linux · linux_kernel, debian · debian_linux 2025-09-12 medium5.5 CVE-2025-39752 In the Linux kernel, the following vulnerability has been resolved: ARM: rockchip: fix kernel hang during smp initialization In order to bring up secondary CPU… linux · linux_kernel, debian · debian_linux 2025-09-11 medium5.5 CVE-2025-39739 In the Linux kernel, the following vulnerability has been resolved: iommu/arm-smmu-qcom: Add SM6115 MDSS compatible Add the SM6115 MDSS compatible to clients c… linux · linux_kernel 2025-09-11 medium5.3 CVE-2025-3212 Use After Free vulnerability in Arm Ltd Bifrost GPU Kernel Driver, Arm Ltd Valhall GPU Kernel Driver, Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver allows… arm · 5th_gen_gpu_architecture_kernel_driver, arm · bifrost_gpu_kernel_driver, arm · valhall_gpu_kernel_driver +3 2025-09-08 medium5.1 CVE-2025-58313 Race condition vulnerability in the device standby module. huawei · harmonyos 2025-09-05 medium6.8 CVE-2025-58276 Permission verification vulnerability in the home screen module Impact: Successful exploitation of this vulnerability may affect availability. huawei · emui, huawei · harmonyos 2025-09-05 medium5.3 GHSA-224p-v68g-5g8f GraphQL Armor Max-Depth Plugin Bypass via fragment caching npm · @escape.tech/graphql-armor-max-depth 2025-08-26 medium5.3 GHSA-hmfr-rx46-4jx2 GraphQL Armor Max-Depth Plugin Bypass via Introspection Query Obfuscation npm · @escape.tech/graphql-armor-max-depth 2025-08-26 medium5.5 CVE-2025-38649 In the Linux kernel, the following vulnerability has been resolved: arm64: dts: qcom: qcs615: fix a crash issue caused by infinite loop for Coresight An infini… linux · linux_kernel 2025-08-22 medium6.1 CVE-2025-55160 ImageMagick has Undefined Behavior (function-type-mismatch) in CloneSplayTree nuget · Magick.NET-Q16-AnyCPU, nuget · Magick.NET-Q16-HDRI-AnyCPU, nuget · Magick.NET-Q16-HDRI-OpenMP-arm64 +15 2025-08-13 medium4.8 CVE-2025-54651 Race condition vulnerability in the kernel hufs module. huawei · harmonyos 2025-08-06 medium4.2 CVE-2025-54650 Improper array index verification vulnerability in the audio codec module. huawei · harmonyos 2025-08-06 medium4.5 CVE-2025-54649 Vulnerability of using incompatible types to access resources in the location service. huawei · harmonyos 2025-08-06 medium5.4 CVE-2025-54648 Out-of-bounds read vulnerability in the SSAP module of the NearLink protocol stack. huawei · harmonyos 2025-08-06 medium5.4 CVE-2025-54647 Out-of-bounds read vulnerability in the SSAP module of the NearLink protocol stack. huawei · harmonyos 2025-08-06 medium5.1 CVE-2025-54646 Vulnerability of inadequate packet length check in the BLE module. huawei · emui, huawei · harmonyos 2025-08-06 medium5.0 CVE-2025-54645 Out-of-bounds array access issue due to insufficient data verification in the location service module. huawei · harmonyos 2025-08-06 medium6.6 CVE-2025-54644 Out-of-bounds array access issue due to insufficient data verification in the kernel ambient light module. huawei · emui, huawei · harmonyos 2025-08-06 medium6.6 CVE-2025-54643 Out-of-bounds array access issue due to insufficient data verification in the kernel ambient light module. huawei · emui, huawei · harmonyos 2025-08-06 medium6.7 CVE-2025-54642 Issue of buffer overflow caused by insufficient data verification in the kernel gyroscope module. huawei · emui, huawei · harmonyos 2025-08-06 medium6.7 CVE-2025-54641 Issue of buffer overflow caused by insufficient data verification in the kernel acceleration module. huawei · emui, huawei · harmonyos 2025-08-06 medium5.5 CVE-2025-54640 ParcelMismatch vulnerability in attribute deserialization. huawei · harmonyos 2025-08-06 medium5.5 CVE-2025-54639 ParcelMismatch vulnerability in attribute deserialization. huawei · harmonyos 2025-08-06 medium5.5 CVE-2025-54638 Issue of inconsistent read/write serialization in the ad module. huawei · harmonyos 2025-08-06 medium4.4 CVE-2025-54637 Out-of-bounds array access issue due to insufficient data verification in the kernel ambient light module. huawei · emui, huawei · harmonyos 2025-08-06 medium4.4 CVE-2025-54636 Issue of buffer overflow caused by insufficient data verification in the kernel drop detection module. huawei · emui, huawei · harmonyos 2025-08-06 medium5.9 CVE-2025-54635 Vulnerability of returning released pointers in the distributed notification service. huawei · harmonyos 2025-08-06 medium6.7 CVE-2025-54633 Out-of-bounds read vulnerability in the register configuration of the DMA module. huawei · harmonyos 2025-08-06 medium6.8 CVE-2025-54632 Vulnerability of insufficient data length verification in the HVB module. huawei · emui, huawei · harmonyos 2025-08-06 medium6.7 CVE-2025-54631 Vulnerability of insufficient data length verification in the partition module. huawei · harmonyos 2025-08-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.