NetSight

Security Dashboard

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

Reset
219 matching advisories · page 1 of 8Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2026-48173 In the NAS message handler, improper validation of the length field in NAS message causes memory corruption Samsung Semiconductor · Exynos 850, Samsung Semiconductor · Exynos 2100, Samsung Semiconductor · Exynos 1280 +18 17 days ago critical9.8 CVE-2026-48174 In the NR RRC component, improper handling of messages before authentication triggers a data abort, which leads to a denial‑of‑service condition. Samsung Semiconductor · Exynos 1280, Samsung Semiconductor · Exynos 2200, Samsung Semiconductor · Exynos 1330 +12 17 days ago critical9.1 CVE-2026-48186 Improper handling of messages before AS security activation can cause unexpected behavior Samsung Semiconductor · Exynos 1280, Samsung Semiconductor · Exynos 2200, Samsung Semiconductor · Exynos 1330 +16 17 days ago critical9.1 CVE-2026-48183 Improper permission handling during buffer operations allows untrusted applications to create memory mappings with inappropriate permissions Samsung Semiconductor · Exynos 1480, Samsung Semiconductor · Exynos 2400, Samsung Semiconductor · Exynos 1580 +5 17 days ago critical9.1 CVE-2026-69006 Insufficient validation of length fields in the GNSS firmware loader can result in kernel‑memory corruption. Samsung Semiconductor · Exynos 850, Samsung Semiconductor · Exynos 2100, Samsung Semiconductor · Exynos 1280 +19 17 days ago critical9.1 CVE-2026-69068 Insufficient length validation in the GNSS firmware loader may lead to corruption of kernel memory. Samsung Semiconductor · Exynos Modem 5300, Samsung Semiconductor · Exynos Modem 5400 17 days ago critical9.8 CVE-2026-68991 In the Samsung Exynos ENN NeuralNetworks HAL, improper input validation during request processing can cause memory corruption and lead to a denial of service c… Samsung Semiconductor · Exynos 1480, Samsung Semiconductor · Exynos 2400, Samsung · Exynos 2400 +1 17 days ago critical9.8 CVE-2026-69050 Out-of-bounds memory access in a device driver due to improper resource state tracking. Samsung Semiconductor · Exynos 1480, Samsung Semiconductor · Exynos 2400, Samsung Semiconductor · Exynos 1580 +5 17 days ago critical9.1 CVE-2026-69043 In the Samsung Exynos GPU driver, improper synchronization during buffer object creation and closing can lead to memory corruption Samsung Semiconductor · Exynos 2200, Samsung Semiconductor · Exynos 1480, Samsung Semiconductor · Exynos 2400 +7 17 days ago critical9.8 CVE-2026-33971 In the LTE RRC component, improper handling of messages before authentication triggers a data abort, which leads to a denial‑of‑service condition. Samsung Semiconductor · Exynos 850, Samsung Semiconductor · Exynos 2100, Samsung Semiconductor · Exynos 1280 +19 17 days ago critical9.8 CVE-2026-33972 In the Exynos modem's IMS stack, Out of Bound access occurs due to improper validation. Samsung Semiconductor · Exynos 1080, Samsung Semiconductor · Exynos 9110, Samsung Semiconductor · Exynos Modem 5123 +3 17 days ago critical9.8 CVE-2026-110392 Improper neutralization of special elements used in an OS command ('OS command injection') vulnerability in Samsung Open Source QA-Board allows : OS Command In… 39 days ago critical9.8 CVE-2026-21096 Heap-based buffer overflow in JPEG decoder of libimagecodec.quram.so prior to SMR Sep-2026 Release 1 allows remote attackers to execute arbitrary code. samsung · android 2026-09-09 critical9.8 CVE-2026-21095 Heap-based buffer overflow in DNG decoder of libimagecodec.quram.so prior to SMR Sep-2026 Release 1 allows remote attackers to execute arbitrary code. samsung · android 2026-09-09 critical9.8 CVE-2025-52908 An issue was discovered in the Wi-Fi driver in Samsung Mobile Processor and Wearable Processor Exynos 980, 850, 1280, 1330, 1380, 1480, 1580, W920, W930, and W… samsung · exynos_w1000_firmware, samsung · exynos_w920_firmware, samsung · exynos_w930_firmware +7 2026-04-07 critical9.8 CVE-2025-62818 An issue was discovered in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 1580, … samsung · exynos_990_firmware, samsung · exynos_980_firmware, samsung · exynos_850_firmware +9 2026-04-07 critical9.8 CVE-2025-52909 An issue was discovered in the Wi-Fi driver in Samsung Mobile Processor and Wearable Processor Exynos 980, 850, 1280, 1330, 1380, 1480, 1580, W920, W930, and W… samsung · exynos_w1000_firmware, samsung · exynos_w920_firmware, samsung · exynos_w930_firmware +7 2026-04-07 critical10.0 CVE-2025-54328 An issue was discovered in SMS in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400,… samsung · exynos_980_firmware, samsung · exynos_990_firmware, samsung · exynos_850_firmware +9 2026-04-06 critical9.1 CVE-2025-58349 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, 2400, … samsung · exynos_990_firmware, samsung · exynos_980_firmware, samsung · exynos_850_firmware +9 2026-04-06 critical9.8 CVE-2026-20998 Improper authentication in Smart Switch prior to version 3.7.69.15 allows remote attackers to bypass authentication. samsung · smart_switch 2026-03-16 critical9.8 CVE-2026-20997 Improper verification of cryptographic signature in Smart Switch prior to version 3.7.69.15 allows remote attackers to potentially bypass authentication. samsung · smart_switch 2026-03-16 critical9.8 CVE-2026-25202 The database account and password are hardcoded, allowing login with the account to manipulate the database in MagicInfo9 Server.This issue affects MagicINFO 9… samsung · magicinfo_9_server 2026-02-02 critical9.8 CVE-2026-25200 A vulnerability in MagicInfo9 Server allows authorized users to upload HTML files without authentication, leading to Stored XSS, which can result in account ta… samsung · magicinfo_9_server 2026-02-02 critical9.1 CVE-2025-27807 An issue was discovered in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 1580, … samsung · exynos_990_firmware, samsung · exynos_980_firmware, samsung · exynos_850_firmware +9 2026-01-05 critical9.8 CVE-2025-52910 An issue was discovered in the GPU in Samsung Mobile Processor and Wearable Processor Exynos 1280, 2200, 1330, 1380, 1480, 2400. samsung · exynos_1280_firmware, samsung · exynos_1330_firmware, samsung · exynos_1380_firmware +3 2025-11-04 critical9.1 CVE-2025-54455 Use of Hard-coded Credentials vulnerability in Samsung Electronics MagicINFO 9 Server allows Authentication Bypass.This issue affects MagicINFO 9 Server: less … samsung · magicinfo_9_server 2025-07-23 critical9.1 CVE-2025-54454 Use of Hard-coded Credentials vulnerability in Samsung Electronics MagicINFO 9 Server allows Authentication Bypass.This issue affects MagicINFO 9 Server: less … samsung · magicinfo_9_server 2025-07-23 critical9.8 CVE-2025-54451 Improper Control of Generation of Code ('Code Injection') vulnerability in Samsung Electronics MagicINFO 9 Server allows Code Injection.This issue affects Magi… samsung · magicinfo_9_server 2025-07-23 critical9.8 CVE-2025-54449 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 critical9.8 CVE-2025-54448 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

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.