NetSight

Security Dashboard

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

Reset
40 matching advisories · page 1 of 2Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.5 CVE-2026-119291 Zuke is a code-first, strongly typed build automation system for Deno. zuke-build · zuke 22 days ago medium5.3 CVE-2026-19337 A vulnerability was determined in adenot mcp-google-search up to 0.3.1. adenot mcp-google-search 2026-08-09 medium6.5 CVE-2026-54164 API Platform Core: Relation IRIs are not type-checked: a related resource can be denormalised as the wrong resource type (type confusion) composer · api-platform/core 2026-07-01 medium4.3 CVE-2026-55517 Deno: Denial of service via non-ASCII bytes in WebSocket response headers rust · deno 2026-06-17 medium5.5 CVE-2026-49406 Deno: BYONM module resolution allows `package.json` main path traversal to bypass `--allow-read` restrictions rust · deno 2026-06-16 medium6.5 CVE-2026-49411 Deno: Node TCPWrap numeric hostname aliases bypass --deny-net resolved-IP deny checks rust · deno 2026-06-16 medium5.2 CVE-2026-49983 Deno: process.loadEnvFile() bypasses env permission checks and mutates process.env with only read access rust · deno 2026-06-16 medium5.2 CVE-2026-49860 Deno: WebSocket API sandbox bypass via missing post-DNS check rust · deno 2026-06-16 medium5.2 CVE-2026-49859 Deno: `fetch()` API sandbox bypass via missing DNS resolution check rust · deno 2026-06-16 medium6.5 CVE-2026-41885 i18next-locize-backend is a simple i18next backend for locize.com which can be used in Node.js, in the browser and for Deno. npm · i18next-locize-backend 2026-04-22 medium5.5 CVE-2026-30936 ImageMagick has Heap Buffer Overflow in WaveletDenoiseImage nuget · Magick.NET-Q16-AnyCPU, nuget · Magick.NET-Q16-HDRI-AnyCPU, nuget · Magick.NET-Q16-HDRI-OpenMP-arm64 +16 2026-03-10 medium4.0 CVE-2026-27798 ImageMagick: Heap Buffer Over-read in WaveletDenoise when processing small images nuget · Magick.NET-Q16-AnyCPU, nuget · Magick.NET-Q16-HDRI-AnyCPU, nuget · Magick.NET-Q16-HDRI-OpenMP-arm64 +16 2026-02-25 medium5.8 CVE-2026-25904 MCP Run Python Deno Sandbox Misconfiguration Allows SSRF Attacks via Localhost Access pip · mcp-run-python 2026-02-09 medium5.3 CVE-2024-21486 Deno vulnerable to Exposure of Sensitive Information to an Unauthorized Actor rust · deno 2025-06-05 medium5.3 CVE-2025-48934 Deno.env.toObject() ignores the variables listed in --deny-env and returns all environment variables rust · deno, rust · deno_runtime 2025-06-04 medium5.3 CVE-2025-48888 Deno run with --allow-read and --deny-read flags results in allowed rust · deno, rust · deno_runtime 2025-06-04 medium5.5 CVE-2025-21898 In the Linux kernel, the following vulnerability has been resolved: ftrace: Avoid potential division by zero in function_stat_show() Check whether denominator … linux · linux_kernel 2025-04-01 medium5.5 CVE-2024-57950 In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Initialize denominator defaults to 1 [WHAT & HOW] Variables, used as denom… linux · linux_kernel 2025-02-10 medium5.4 CVE-2024-32468 deno_doc's HTML generator vulnerable to Cross-site Scripting rust · deno_doc 2024-11-25 medium5.1 CVE-2024-52793 The Deno Standard Library provides APIs for Deno and the Web. 2024-11-22 medium5.5 CVE-2024-49899 In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Initialize denominators' default to 1 [WHAT & HOW] Variables used as denom… linux · linux_kernel 2024-10-21 medium5.5 CVE-2024-49892 In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Initialize get_bytes_per_element's default to 1 Variables, used as denomin… linux · linux_kernel 2024-10-21 medium5.5 CVE-2024-46773 In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check denominator pbn_div before used [WHAT & HOW] A denominator cannot be… linux · linux_kernel 2024-09-18 medium5.5 CVE-2024-46772 In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check denominator crb_pipes before used [WHAT & HOW] A denominator cannot … linux · linux_kernel 2024-09-18 medium5.3 CVE-2024-32869 Hono vulnerable to Restricted Directory Traversal in serveStatic with deno npm · hono 2024-04-23 medium4.6 CVE-2024-27932 Deno's improper suffix match testing for DENO_AUTH_TOKENS rust · deno 2024-03-06 medium5.8 CVE-2024-27931 Insufficient permission checking in `Deno.makeTemp*` APIs rust · deno 2024-03-05 medium4.3 CVE-2023-6633 The Site Notes WordPress plugin through 2.0.0 does not have CSRF checks in some of its functionalities, which could allow attackers to make logged in users per… sidenotesproject · side_notes 2024-01-29 medium5.3 CVE-2023-30858 The Denosaurs emoji package provides emojis for dinosaurs. denosaurs · emoji 2023-04-28 medium5.3 CVE-2023-26103 Regular Expression Denial of Service in Deno.upgradeWebSocket API rust · deno 2023-02-25

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.