NetSight

Security Dashboard

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

Reset
4,692 matching advisories · page 22 of 157Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2025-52513 An issue was discovered in Samsung Mobile Processor Exynos 2400, 1580, 2500. samsung · exynos_1580_firmware, samsung · exynos_2400_firmware, samsung · exynos_2500_firmware 2025-11-04 high7.5 CVE-2025-52512 An issue was discovered in Samsung Mobile Processor Exynos 2400, 1580, 2500. samsung · exynos_1580_firmware, samsung · exynos_2400_firmware, samsung · exynos_2500_firmware 2025-11-04 medium5.3 CVE-2025-54333 An issue was discovered in NPU in Samsung Mobile Processor Exynos 1380 through July 2025. samsung · exynos_1380_firmware 2025-11-04 medium5.3 CVE-2025-54325 An issue was discovered in VTS in Samsung Mobile Processor and Wearable Processor Exynos 1080, 1280, 2200, 1380, 1480, 2400, 1580, 2500, W920, W930, W1000. samsung · exynos_1080_firmware, samsung · exynos_1280_firmware, samsung · exynos_1380_firmware +8 2025-11-04 high7.5 CVE-2025-54332 An issue was discovered in NPU in Samsung Mobile Processor Exynos 1380 through July 2025. samsung · exynos_1380_firmware 2025-11-04 medium5.3 CVE-2025-54331 An issue was discovered in NPU in Samsung Mobile Processor Exynos 1380 through July 2025. samsung · exynos_1380_firmware 2025-11-04 medium5.3 CVE-2025-54330 An issue was discovered in NPU in Samsung Mobile Processor Exynos 1380 through July 2025. samsung · exynos_1380_firmware 2025-11-04 high7.5 CVE-2025-54329 An issue was discovered in NAS in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, 990, 850, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 1580,… samsung · exynos_1280_firmware, samsung · exynos_1330_firmware, samsung · exynos_1380_firmware +9 2025-11-04 high7.5 CVE-2025-54323 An issue was discovered in the camera in Samsung Mobile Processor Exynos 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, and 1580. samsung · exynos_1080_firmware, samsung · exynos_1280_firmware, samsung · exynos_1330_firmware +9 2025-11-04 critical GHSA-vm4w-438j-rgf3 Malware in powerbi-visuals-sunburstMalware npm · powerbi-visuals-sunburst 2025-10-29 medium5.3 CVE-2025-62892 Missing Authorization vulnerability in sunshinephotocart Sunshine Photo Cart sunshine-photo-cart allows Accessing Functionality Not Properly Constrained by ACL… Sunshine Photo Cart: from n/a through 2025-10-27 critical9.1 CVE-2025-52758 Unrestricted Upload of File with Dangerous Type vulnerability in Gesundheit Bewegt GmbH Zippy zippy allows Using Malicious Files.This issue affects Zippy: from… Zippy: from n/a through 2025-10-22 medium4.3 CVE-2025-48025 In Samsung Mobile Processor and Wearable Processor Exynos 980, 850, 1280, 1330, 1380, 1480, 1580, W920, W930, and W1000, there is an improper access control vu… samsung · exynos_980_firmware, samsung · exynos_850_firmware, samsung · exynos_1280_firmware +7 2025-10-20 high7.5 CVE-2025-26782 An issue was discovered in L2 in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 9110, … samsung · exynos_w920_firmware, samsung · exynos_1080_firmware, samsung · exynos_980_firmware +9 2025-10-20 high7.5 CVE-2025-26781 An issue was discovered in L2 in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 9110, … samsung · exynos_w920_firmware, samsung · exynos_1080_firmware, samsung · exynos_980_firmware +9 2025-10-20 high7.5 CVE-2024-55568 An issue was discovered in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 9110, … samsung · exynos_1080_firmware, samsung · exynos_1330_firmware, samsung · exynos_1380_firmware +9 2025-10-20 high7.8 CVE-2025-39986 In the Linux kernel, the following vulnerability has been resolved: can: sun4i_can: populate ndo_change_mtu() to prevent buffer overflow Sending an PF_PACKET a… 2025-10-15 medium4.0 CVE-2025-21070 Out-of-bounds write in the SPI decoder in Samsung Notes prior to version 4.4.30.63 allows local attackers to write out-of-bounds memory. samsung · notes 2025-10-10 medium4.0 CVE-2025-21069 Out-of-bounds read in the parsing of image data in Samsung Notes prior to version 4.4.30.63 allows local attackers to access out-of-bounds memory. samsung · notes 2025-10-10 medium4.0 CVE-2025-21068 Out-of-bounds read in the reading of image data in Samsung Notes prior to version 4.4.30.63 allows local attackers to access out-of-bounds memory. samsung · notes 2025-10-10 medium4.0 CVE-2025-21067 Out-of-bounds read in the allocation of image buffer in Samsung Notes prior to version 4.4.30.63 allows local attackers to access out-of-bounds memory. samsung · notes 2025-10-10 medium4.0 CVE-2025-21066 Out-of-bounds read in the SPI decoder in Samsung Notes prior to version 4.4.30.63 allows local attackers to access out-of-bounds memory. samsung · notes 2025-10-10 high8.8 CVE-2025-21064 Improper authentication in Smart Switch prior to version 3.7.66.6 allows adjacent attackers to access transferring data. samsung · smart_switch 2025-10-10 medium4.6 CVE-2025-21063 Improper access control in Samsung Voice Recorder prior to version 21.5.73.12 in Android 15 and 21.5.81.40 in Android 16 allows physical attackers to access re… samsung · voice_recorder 2025-10-10 high7.8 CVE-2025-21062 Use of a broken or risky cryptographic algorithm in Smart Switch prior to version 3.7.67.2 allows local attackers to replace the restoring application. samsung · smart_switch 2025-10-10 high7.1 CVE-2025-21061 Cleartext storage of sensitive information in Smart Switch prior to version 3.7.67.2 allows local attackers to access sensitive data. samsung · smart_switch 2025-10-10 medium5.5 CVE-2025-21060 Cleartext storage of sensitive information in Smart Switch prior to version 3.7.67.2 allows local attackers to access backup data from applications. samsung · smart_switch 2025-10-10 medium6.2 CVE-2025-21059 Improper authorization in Samsung Health prior to version 6.30.5.105 allows local attackers to access data in Samsung Health. samsung · health 2025-10-10 medium4.0 CVE-2025-21057 Use of implicit intent for sensitive communication in Samsung Notes prior to version 4.4.30.63 allows local attackers to access shared notes. samsung · notes 2025-10-10 medium4.3 CVE-2025-21055 Out-of-bounds read and write in libimagecodec.quram.so prior to SMR Oct-2025 Release 1 allows remote attackers to access out-of-bounds memory. samsung · android 2025-10-10

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.