NetSight

Security Dashboard

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

Reset
757 matching advisories · page 5 of 26Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-5p45-7pjw-475c Malicious code in bafai-sunai-cuma (npm)Malware npm · bafai-sunai-cuma 2026-09-02 critical GHSA-6wm6-rv5m-r56w Malicious code in awk-sun-deploy-key-omega (npm)Malware npm · awk-sun-deploy-key-omega 2026-09-02 critical GHSA-mhp6-fj96-q9r8 Malicious code in authorize-sigma-stub-sun-mock (npm)Malware npm · authorize-sigma-stub-sun-mock 2026-09-02 critical GHSA-rrhx-j8vq-79vv Malicious code in amber-sunset-sha689-project (npm)Malware npm · amber-sunset-sha689-project 2026-09-02 critical GHSA-xjjm-4wwr-3wvx Malicious code in alpha-sun-validate-transpile-bad (npm)Malware npm · alpha-sun-validate-transpile-bad 2026-09-02 critical GHSA-c834-6h33-83m2 Malicious code in albatross-sunset-jfj328-project (npm)Malware npm · albatross-sunset-jfj328-project 2026-08-31 critical GHSA-mmj9-ff7c-jwc2 Malicious code in air-query-sun-void-debug (npm)Malware npm · air-query-sun-void-debug 2026-08-31 critical GHSA-xxp3-7c5j-mqrq Malicious code in afai-sunabi-cufgau (npm)Malware npm · afai-sunabi-cufgau 2026-08-31 critical9.8 CVE-2026-72317 In the Linux kernel, the following vulnerability has been resolved: SUNRPC: pin upper rpc_clnt across the TLS connect_worker The TLS connect path has a use-aft… 2026-08-15 critical9.8 CVE-2026-72222 In the Linux kernel, the following vulnerability has been resolved: sunrpc: pin svc_xprt across the asynchronous TLS handshake callback svc_tcp_handshake() sto… 2026-08-15 critical9.8 CVE-2026-72221 In the Linux kernel, the following vulnerability has been resolved: sunrpc: wait for in-flight TLS handshake callback when cancel loses race When wait_for_comp… 2026-08-15 critical9.8 CVE-2026-72220 In the Linux kernel, the following vulnerability has been resolved: sunrpc: harden rq_procinfo lifecycle to prevent double-free The svc_release_rqst() function… 2026-08-15 critical9.8 CVE-2026-72217 In the Linux kernel, the following vulnerability has been resolved: SUNRPC: Bound-check xdr_buf_to_bvec() stores before writing xdr_buf_to_bvec() writes a bio_… 2026-08-15 critical GHSA-q5x7-xq6c-4cfc Malware in sunpro-3dmodel-rendererMalware npm · sunpro-3dmodel-renderer 2026-07-30 critical9.3 CVE-2026-24727 An unrestricted upload of file with dangerous type vulnerability in the e-paper draft upload function of SUNNET Corporate Training Management System through v1… SUNNET Corporate Training Management System 2026-07-24 critical GHSA-rhgm-phvc-72p9 Malicious code in sunrequests (PyPI)Malware pip · sunrequests 2026-07-21 critical9.1 CVE-2026-64609 Out-of-bounds read via sun.misc.Unsafe in Apache Fory. apache · fory 2026-07-21 critical GHSA-5g9p-p4cq-v6ff Malicious code in g8402sunic (RubyGems)Malware rubygems · g8402sunic 2026-07-18 critical GHSA-cvm3-cf32-fx43 Malicious code in github.com/utilizedsun/layout (Go)Malware go · github.com/utilizedsun/layout 2026-07-13 critical9.8 CVE-2026-32253 Sunshine is a self-hosted game stream host for Moonlight. lizardbyte · sunshine 2026-05-22 critical9.2 CVE-2026-8072 Insecure generation of credentials in the local SAT (Technical Support) access functionality of the Ingecon Sun EMS Board. 2026-05-12 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 critical7.5 CVE-2026-32614 SM9 Infinity-Point Ciphertext Forgery Vulnerability go · github.com/emmansun/gmsm 2026-03-13 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

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.