NetSight

Security Dashboard

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

Reset
438 matching advisories · page 13 of 15Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-fm65-938r-jvjw Malware in n8n-nodes-xml-utilsMalware npm · n8n-nodes-xml-utils 2026-03-16 critical GHSA-m4cr-jqq9-pf5g Malware in n8n-nodes-text-utilsMalware npm · n8n-nodes-text-utils 2026-03-16 critical GHSA-ffvh-hxxc-qgqq Malware in n8n-nodes-csv-parseMalware npm · n8n-nodes-csv-parse 2026-03-16 critical GHSA-r2w7-4rv7-p8wj Malware in n8n-nodes-text-helpersMalware npm · n8n-nodes-text-helpers 2026-03-16 medium4.0 GHSA-38c7-23hj-2wgq n8n has Webhook Forgery on Zendesk Trigger Node npm · n8n, npm · n8n 2026-02-26 medium3.7 GHSA-fvfv-ppw4-7h2w n8n has a Guardrail Node Bypass npm · n8n 2026-02-26 medium4.8 GHSA-jh8h-6c9q-7gmw n8n has an Authentication Bypass in its Chat Trigger Node npm · n8n, npm · n8n, npm · n8n 2026-02-26 medium6.3 GHSA-vjf3-2gpj-233v n8n has an SSO Enforcement Bypass in its Self-Service Settings API npm · n8n 2026-02-26 medium4.0 CVE-2026-56357 n8n before 1.123.15 and 2.5.0 contains a webhook forgery vulnerability in the GitHub Webhook Trigger node that fails to implement HMAC-SHA256 signature verific… npm · n8n 2026-02-26 high8.2 CVE-2026-56351 n8n before version 2.4.0 contains a sql injection vulnerability in MySQL, PostgreSQL, and Microsoft SQL nodes that allows authenticated users to inject arbitra… npm · n8n 2026-02-26 high5.4 CVE-2026-27578 n8n Vulnerable to Stored XSS via Various Nodes npm · n8n 2026-02-25 critical9.9 CVE-2026-27577 n8n: Expression Sandbox Escape Leads to RCE npm · n8n 2026-02-25 critical8.5 CVE-2026-27498 n8n has Arbitrary Command Execution via File Write and Git Operations npm · n8n 2026-02-25 critical9.9 CVE-2026-27497 n8n has Potential Remote Code Execution via Merge Node npm · n8n 2026-02-25 critical9.4 CVE-2026-27495 n8n has a Sandbox Escape in its JavaScript Task Runner npm · n8n 2026-02-25 critical9.9 CVE-2026-27494 n8n has Arbitrary File Read via Python Code Node Sandbox Escape npm · n8n 2026-02-25 critical9.0 CVE-2026-27493 n8n has Unauthenticated Expression Evaluation via Form Node npm · n8n 2026-02-25 medium5.3 CVE-2026-25631 n8n's domain allowlist bypass enables credential exfiltration npm · n8n 2026-02-04 critical9.4 CVE-2026-21893 n8n Vulnerable to Command Injection in Community Package Installation npm · n8n 2026-02-04 critical9.9 CVE-2026-25115 n8n has a Python sandbox escape npm · n8n 2026-02-04 critical9.4 CVE-2026-25056 n8n Merge Node has Arbitrary File Write leading to RCE npm · n8n 2026-02-04 high7.1 CVE-2026-25055 n8n Vulnerable to Arbitrary File Write on Remote Systems via SSH Node npm · n8n 2026-02-04 high8.5 CVE-2026-25054 n8n Has Stored Cross-site Scripting via Markdown Rendering in Workflow UI npm · n8n 2026-02-04 critical9.4 CVE-2026-25053 n8n has OS Command Injection in Git Node npm · n8n 2026-02-04 critical9.4 CVE-2026-25052 n8n's Improper File Access Controls Allow Arbitrary File Read by Authenticated Users npm · n8n 2026-02-04 high8.5 CVE-2026-25051 n8n's Improper CSP Enforcement in Webhook Responses May Allow Stored XSS npm · n8n 2026-02-04 critical9.4 CVE-2026-25049 n8n Has Expression Escape Vulnerability Leading to RCE npm · n8n 2026-02-04 high7.7 CVE-2025-61917 n8n's Unsafe Buffer Allocation Allows In-Process Memory Disclosure in Task Runner npm · n8n 2026-02-04 critical GHSA-h3jq-3362-m28h Malware in n8n-nodes-comfyui-illuMalware npm · n8n-nodes-comfyui-illu 2026-01-29 critical GHSA-xxpx-q438-f7hp Malware in n8n-zalo-fevoxMalware npm · n8n-zalo-fevox 2026-01-28

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.