NetSight

Security Dashboard

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

Reset
605 matching advisories · page 5 of 21Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.0 CVE-2023-21475 Out-of-bounds Write vulnerability in libaudiosaplus_sec.so library prior to SMR Apr-2023 Release 1 allows local attacker to execute arbitrary code. samsung · android 2025-09-03 high7.1 CVE-2025-53080 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in Samsung DMS(Data Management Server) allows authenticated attackers to create … samsung · data_management_server_firmware 2025-07-29 high8.0 CVE-2025-53078 Deserialization of Untrusted Data in Samsung DMS(Data Management Server) allows attackers to execute arbitrary code via write file to system samsung · data_management_server_firmware 2025-07-29 high8.8 CVE-2025-54453 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Samsung Electronics MagicINFO 9 Server allows Code Injection.Th… samsung · magicinfo_9_server 2025-07-23 high7.3 CVE-2025-54452 Improper Authentication vulnerability in Samsung Electronics MagicINFO 9 Server allows Authentication Bypass.This issue affects MagicINFO 9 Server: less than 2… samsung · magicinfo_9_server 2025-07-23 high7.2 CVE-2025-54450 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Samsung Electronics MagicINFO 9 Server allows Code Injection.Th… samsung · magicinfo_9_server 2025-07-23 high8.1 CVE-2025-54447 Unrestricted Upload of File with Dangerous Type vulnerability in Samsung Electronics MagicINFO 9 Server allows Code Injection.This issue affects MagicINFO 9 Se… samsung · magicinfo_9_server 2025-07-23 high8.2 CVE-2025-54445 Improper Restriction of XML External Entity Reference vulnerability in Samsung Electronics MagicINFO 9 Server allows Server Side Request Forgery.This issue aff… samsung · magicinfo_9_server 2025-07-23 high8.8 CVE-2025-54441 Unrestricted Upload of File with Dangerous Type vulnerability in Samsung Electronics MagicINFO 9 Server allows Code Injection.This issue affects MagicINFO 9 Se… samsung · magicinfo_9_server 2025-07-23 high8.8 CVE-2025-54439 Unrestricted Upload of File with Dangerous Type vulnerability in Samsung Electronics MagicINFO 9 Server allows Code Injection.This issue affects MagicINFO 9 Se… samsung · magicinfo_9_server 2025-07-23 high7.0 CVE-2025-21006 Out-of-bounds write in handling of macro blocks for MPEG4 codec in libsavsvc.so prior to Android 15 allows local attackers to write out-of-bounds memory. samsung · android 2025-07-08 high7.5 CVE-2025-26780 An issue was discovered in L2 in Samsung Mobile Processor and Modem Exynos 2400 and Modem 5400. samsung · exynos_2400_firmware, samsung · modem_5400_firmware 2025-07-07 high7.5 CVE-2025-23100 An issue was discovered in Samsung Mobile Processor Exynos 1280, 2200, 1380, 1480, 2400. samsung · exynos_1280_firmware, samsung · exynos_2200_firmware, samsung · exynos_1380_firmware +2 2025-06-03 high7.8 CVE-2025-23098 An issue was discovered in Samsung Mobile Processor Exynos 980, 990, 1080, 2100, 1280, 2200, 1380. samsung · exynos_980_firmware, samsung · exynos_990_firmware, samsung · exynos_1080_firmware +4 2025-06-03 high8.8 CVE-2025-23102 An issue was discovered in Samsung Mobile Processor Exynos 980, 990, 1080, 2100, 1280, 2200, 1380, 1480 and 2400. samsung · exynos_980_firmware, samsung · exynos_990_firmware, samsung · exynos_1080_firmware +6 2025-06-03 high8.6 CVE-2025-23107 An issue was discovered in Samsung Mobile Processor Exynos 1480 and 2400. samsung · exynos_1480_firmware, samsung · exynos_2400_firmware 2025-06-03 high8.6 CVE-2025-23103 An issue was discovered in Samsung Mobile Processor Exynos 1480 and 2400. samsung · exynos_1480_firmware, samsung · exynos_2400_firmware 2025-06-03 high7.8 CVE-2025-23105 An issue was discovered in Samsung Mobile Processor Exynos 2200, 1480, and 2400. samsung · exynos_2200_firmware, samsung · exynos_1480_firmware, samsung · exynos_2400_firmware 2025-06-02 high7.5 CVE-2024-49196 An issue was discovered in the GPU in Samsung Mobile Processor Exynos 1480 and 2400. samsung · exynos_1480_firmware, samsung · exynos_2400_firmware 2025-05-27 high7.5 CVE-2025-26783 An issue was discovered in RRC in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 2100, 1280, 2200, 1330, 1380, 1480, 2400, W1000, Modem 5300, a… samsung · exynos_2100_firmware, samsung · exynos_1280_firmware, samsung · exynos_2200_firmware +7 2025-05-14 high7.5 CVE-2024-55569 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_980_firmware, samsung · exynos_990_firmware, samsung · exynos_850_firmware +9 2025-05-14 high8.1 CVE-2024-58101 Samsung Galaxy Buds and Galaxy Buds 2 audio devices are Bluetooth pairable by default without user input nor a way to stop this mode. 2025-05-14 high7.5 CVE-2025-26785 An issue was discovered in NAS in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400,… samsung · exynos_1280_firmware, samsung · exynos_2200_firmware, samsung · exynos_1330_firmware +9 2025-05-14 high7.2 CVE-2025-20968 Improper access control in Samsung Gallery prior to version 14.5.10.3 in Global Android 13, 14.5.09.3 in China Android 13, and 15.5.04.5 in Android 14 allows r… samsung · gallery 2025-05-07 high7.3 CVE-2025-20957 Improper access control in SmartManagerCN prior to SMR May-2025 Release 1 allows local attackers to launch arbitrary activities with SmartManagerCN privilege. samsung · android 2025-05-07 high8.8 CVE-2025-20946 Improper handling of exceptional conditions in pairing specific bluetooth devices in Galaxy Watch Bluetooth pairing prior to SMR Apr-2025 Release 1 allows loca… samsung · wear_os 2025-04-08 high8.8 CVE-2025-20936 Improper access control in HDCP trustlet prior to SMR Apr-2025 Release 1 allows local attackers with shell privilege to escalate their privileges to root. samsung · android 2025-04-08 high8.8 CVE-2025-2233 Samsung SmartThings Improper Verification of Cryptographic Signature Authentication Bypass Vulnerability. samsung · smartthings 2025-03-11 high7.5 CVE-2024-50600 An issue was discovered in Samsung Mobile Processor and Wearable Processor Exynos 980, 850, 1080, 1280, 1330, 1380, 1480, W920, W930, and W1000. samsung · exynos_980_firmware, samsung · exynos_850_firmware, samsung · exynos_1080_firmware +7 2025-03-06 high7.5 CVE-2024-52924 An issue was discovered in NRMM in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 9820, 9825, 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380… samsung · exynos_9820_firmware, samsung · exynos_9825_firmware, samsung · exynos_980_firmware +9 2025-03-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.