NetSight

Security Dashboard

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

Reset
4,692 matching advisories · page 6 of 157Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-5hfp-jjv9-69q8 Malicious code in @hrmony/belegerfassung-pladddform (npm)Malware npm · @hrmony/belegerfassung-pladddform 53 days ago unscored CVE-2026-97952 In the Linux kernel, the following vulnerability has been resolved: sunvdc: unmap LDC cookies when the descriptor send fails __send_request() maps the request'… 57 days ago unscored CVE-2026-93219 In the Linux kernel, the following vulnerability has been resolved: clocksource/drivers/timer-sun4i: Advertise a real minimum delta sun4i_clkevt_next_event() c… 58 days ago critical9.8 CVE-2026-93207 In the Linux kernel, the following vulnerability has been resolved: SUNRPC: Zero rpc_gss_wire_cred at svcauth_gss_decode_credbody() entry svcauth_gss_decode_cr… 58 days ago critical10.0 CVE-2026-59167 SunEditor is a lightweight and powerful WYSIWYG editor in vanilla JavaScript with no dependencies. npm · suneditor 59 days ago medium5.3 CVE-2026-63386 js-toml allows uncontrolled recursion in `load()` leading `RangeError` (stack exhaustion) on deeply nested input npm · js-toml 2026-09-22 unscored CVE-2026-90298 In the Linux kernel, the following vulnerability has been resolved: drm/sun4i: tcon: Drop TCON TOP device reference of_find_device_by_node() takes a device ref… 2026-09-17 unscored CVE-2026-90297 In the Linux kernel, the following vulnerability has been resolved: drm/sun4i: crtc: Propagate layer initialization error sun4i_crtc_init() returns plain NULL … 2026-09-17 unscored CVE-2026-90287 In the Linux kernel, the following vulnerability has been resolved: phy: sunplus: fix error handling in sp_uphy_init() Fix the error paths of sp_uphy_init() to… 2026-09-17 critical9.8 CVE-2026-90235 In the Linux kernel, the following vulnerability has been resolved: sunrpc: xprtsock: annotate shared socket callbacks with READ_ONCE/WRITE_ONCE xprtsock repla… 2026-09-17 unscored CVE-2026-90208 In the Linux kernel, the following vulnerability has been resolved: clocksource/drivers/samsung_pwm: Switch to raw_spinlock_t type Samsung PWM timer might be u… 2026-09-17 critical GHSA-gpvc-cfhx-hccp Malicious code in lagoon-sunset-iea408-project (npm)Malware npm · lagoon-sunset-iea408-project 2026-09-17 critical GHSA-5hc3-cmgw-frqx Malicious code in kuinsu-luki-nasunbaubi (npm)Malware npm · kuinsu-luki-nasunbaubi 2026-09-17 critical GHSA-2jqm-fv9g-5h42 Malicious code in kuinsu-luki-nasunaubi (npm)Malware npm · kuinsu-luki-nasunaubi 2026-09-17 critical GHSA-hx8c-f849-3f4f Malicious code in kuinsu-luki-nasunbi (npm)Malware npm · kuinsu-luki-nasunbi 2026-09-17 critical GHSA-w2ff-qv4h-wr5j Malicious code in kuinsu-luki-nasununabaubi (npm)Malware npm · kuinsu-luki-nasununabaubi 2026-09-17 critical GHSA-gmr6-h6rc-9rmq Malicious code in kuinsu-luki-nasunnabaubi (npm)Malware npm · kuinsu-luki-nasunnabaubi 2026-09-17 critical GHSA-v2x2-977m-p262 Malicious code in kuinsu-luki-nasunabaubi (npm)Malware npm · kuinsu-luki-nasunabaubi 2026-09-17 critical GHSA-xxw8-269x-8566 Malicious code in kuinsu-luki-nasunabi (npm)Malware npm · kuinsu-luki-nasunabi 2026-09-17 critical GHSA-hmjr-xjwr-p8pv Malicious code in kuinsu-lubki-nasunaubi (npm)Malware npm · kuinsu-lubki-nasunaubi 2026-09-17 critical GHSA-hxwc-2vh2-f937 Malicious code in kuinsu-lubki-nasunaui (npm)Malware npm · kuinsu-lubki-nasunaui 2026-09-17 critical GHSA-p3ch-5jmc-8p3h Malicious code in kuinsu-lubki-nasununabaubi (npm)Malware npm · kuinsu-lubki-nasununabaubi 2026-09-17 critical GHSA-j754-gh9q-xw87 Malicious code in kuinsu-lubki-nasunnbaubi (npm)Malware npm · kuinsu-lubki-nasunnbaubi 2026-09-17 critical GHSA-c2mm-hj9j-g362 Malicious code in ksunu-uyilu-vanmiun (npm)Malware npm · ksunu-uyilu-vanmiun 2026-09-17 critical GHSA-6p3c-pvm2-cqg2 Malicious code in ksunsu-uyilu-vanmiun (npm)Malware npm · ksunsu-uyilu-vanmiun 2026-09-17 high7.8 CVE-2026-89883 In the Linux kernel, the following vulnerability has been resolved: media: rc: sunxi-cir: Unregister rc device on probe failure After rc_register_device() succ… 2026-09-16 unscored CVE-2026-89784 In the Linux kernel, the following vulnerability has been resolved: SUNRPC: check rpc_sockaddr2uaddr() return value in rpcb_register_inet4/6 rpcb_register_inet… 2026-09-16 medium5.5 CVE-2026-92259 Integer overflow or wraparound vulnerability in Samsung Opensource Escargot allows attackers with write access to the bytecode-cache directory to cause a heap-… 2026-09-15 medium4.4 CVE-2026-91826 Stack-based buffer overflow vulnerability in Samsung Opensource rLottie allows attackers to overflow buffers, leading to memory corruption when rendering craft… 2026-09-15 low2.8 CVE-2023-37366 An issue was discovered in Samsung Exynos Mobile Processor, Automotive Processor, and Modem Exynos 9810, Exynos 9610, Exynos 9820, Exynos 980, Exynos 850, Exyn… 2026-09-14

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.