NetSight

Security Dashboard

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

Reset
4,692 matching advisories · page 3 of 157Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.7 CVE-2026-124684 This issue can cause a heap-use-after-free when an embedder unloads a ReloadableString buffer while a previously returned raw character pointer remains in use. Samsung Open Source · Escargot 12 days ago critical9.3 CVE-2026-124493 SunEditor before 3.4.0 contains a stored cross-site scripting vulnerability in the DocumentType constructor that injects header textContent into innerHTML with… JiHong88 · suneditor 13 days ago critical9.3 CVE-2026-124494 SunEditor before 3.4.0 contains a stored cross-site scripting vulnerability because the html.clean() sanitizer's _normalizeURL() function decodes named entitie… JiHong88 · suneditor 13 days ago high8.3 CVE-2026-124492 SunEditor before 3.4.0 contains a stored cross-site scripting vulnerability in ModalAnchorEditor's #createBookmarkList, which inserts entity-decoded h1-h6 head… JiHong88 · suneditor 13 days ago medium6.4 CVE-2026-124491 SunEditor before 3.4.0 contains a stored cross-site scripting vulnerability in the FileUpload plugin create() method that assigns server-returned file names to… JiHong88 · suneditor 13 days ago medium6.1 CVE-2026-124422 SunEditor from 3.0.0 before 3.4.0 contains a stored cross-site scripting vulnerability in html.clean() that rebuilds iframes from data-se-iframe-holder-attrs J… jihong88 · suneditor, JiHong88 · suneditor 14 days ago 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 high7.5 CVE-2026-35494 In the baseband, memory corruption during NAS packet processing can cause a denial of service. Samsung Semiconductor · Exynos 1280, Samsung Semiconductor · Exynos 2200, Samsung Semiconductor · Exynos 1330 +13 17 days ago high8.8 CVE-2026-48178 Out of bound access in PPC due to race condition in global variable access Samsung Semiconductor · Exynos 2200, Samsung Semiconductor · Exynos 2400, Samsung Semiconductor · Exynos 2500 +3 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 medium6.3 CVE-2026-68993 A double free vulnerability in NPU driver due to improper pointer management (940) Samsung Semiconductor · Exynos 1480, Samsung Semiconductor · Exynos 2400, Samsung · Exynos 1480 +1 17 days ago high7.3 CVE-2026-68994 A double free vulnerability in NPU driver due to improper pointer management (941) Samsung Semiconductor · Exynos 1480, Samsung Semiconductor · Exynos 2400, Samsung Semiconductor · Exynos 1580 +3 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 high8.1 CVE-2026-68984 In the Samsung Exynos NPU kernel driver, an integer overflow allows an unprivileged application to trigger memory corruption. Samsung Semiconductor · Exynos 2100, Samsung Semiconductor · Exynos 1280, Samsung Semiconductor · Exynos 2200 +13 17 days ago high7.3 CVE-2026-69005 Integer overflow in NPU driver parameter processing due to insufficient bounds checking. Samsung Semiconductor · Exynos 1480, Samsung Semiconductor · Exynos 2400, Samsung Semiconductor · Exynos 1580 +5 17 days ago high7.5 CVE-2026-68985 In the Samsung Exynos NPU driver, improper validation of user input in the ioctl handler can lead to an out-of-bounds write, which causes a denial of service. Samsung Semiconductor · Exynos 1280, Samsung Semiconductor · Exynos 2200, Samsung Semiconductor · Exynos 1380 +3 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 high7.5 CVE-2026-69025 In the Exynos NPU driver, improper validation of user input in the ioctl handler can lead to an out-of-bounds write, which causes a denial of service Samsung Semiconductor · Exynos 1480, Samsung Semiconductor · Exynos 2400, Samsung · Exynos 2400 +1 17 days ago high7.8 CVE-2026-68990 In the Samsung Exynos H-Arx DRM plugin, improper input validation during buffer operations can cause memory corruption, potentially leading to denial of servic… Samsung Semiconductor · Exynos 1480, Samsung Semiconductor · Exynos 2400, Samsung Semiconductor · Exynos 1580 +5 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 high7.5 CVE-2026-69002 Incorrect authorization in Samsung framework services due to missing permission checks Samsung Semiconductor · Exynos 1580, Samsung Semiconductor · Exynos 2500, Samsung Semiconductor · Exynos 2600 +1 17 days ago high8.4 CVE-2026-69066 Memory corruption in GPU driver due to improper validation of VMID reservation. Samsung Semiconductor · Exynos 2200, Samsung Semiconductor · Exynos 1480, Samsung Semiconductor · Exynos 2400 +5 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 high8.4 CVE-2026-69044 In the Samsung GPU driver, improper reference count handling during command submission can lead to memory corruption. Samsung Semiconductor · Exynos 1580, Samsung Semiconductor · Exynos 2500, Samsung Semiconductor · Exynos 2600 +1 17 days ago high7.5 CVE-2025-66366 Incorrect handling of unauthenticated downlink RRC Setup messages can cause the baseband to crash Samsung Semiconductor · Exynos 1280, Samsung Semiconductor · Exynos 1330, Samsung Semiconductor · Exynos 1380 +12 17 days ago medium5.3 CVE-2026-33965 An attacker may send a malicious IMS message to the target device, potentially leading to information exposure through the SIP message flow. Samsung Semiconductor · Exynos 1080, Samsung Semiconductor · Exynos 9110, Samsung Semiconductor · Exynos Modem 5123 +3 17 days ago high7.5 CVE-2025-66367 Improper handling of NAS DLTransport messages may lead to a baseband crash. Samsung Semiconductor · Exynos 850, Samsung Semiconductor · Exynos 2100, Samsung Semiconductor · Exynos 1280 +19 17 days ago

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.