NetSight

Security Dashboard

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

Reset
438 matching advisories · page 9 of 15Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.1 GHSA-88c4-pcqm-3r9p Duplicate Advisory: GraphQL Node Bypasses "Allowed HTTP Request Domains" Restriction npm · n8n 2026-07-22 medium5.5 GHSA-4v35-78jc-648r Duplicate Advisory: computer-use Shell Sandbox Not Enforced on Linux and Windows npm · @n8n/computer-use 2026-07-22 medium6.3 GHSA-h9fm-xcv2-qfw3 Duplicate Advisory: Unauthenticated Endpoint Allows Cancellation of Any User's Active Test Webhook npm · n8n 2026-07-22 medium6.3 GHSA-38fj-36m5-783c Duplicate Advisory: Authenticated SSRF via Dynamic Node Parameters Endpoints Allows Internal Network Access npm · n8n 2026-07-22 high7.7 GHSA-mwq7-vcmc-cm4q Duplicate Advisory: SSO Instance-Role Provisioning Allows Privilege Escalation to Instance Owner npm · n8n 2026-07-22 medium5.1 GHSA-5vfw-jc4p-fj39 Duplicate Advisory: Member-Level Users Can Execute Other Users' MCP Server Trigger Workflows via Missing OAuth Authorization Check npm · n8n 2026-07-22 high8.9 GHSA-m7jc-p4hf-xhwq Duplicate Advisory: Legacy Expression Evaluator Sanitizer Bypass Leads to Authenticated Code Execution npm · n8n 2026-07-22 medium5.1 GHSA-fmvg-vhqq-r2mj Duplicate Advisory: Custom Header Credential Values Leaked in Plaintext into LLM Node Execution Data npm · n8n 2026-07-22 medium6.5 CVE-2026-65599 n8n versions before 1.123.64, 2.29.8, and 2.30.1 contain a credential exposure vulnerability: when configured with a Google Service Account key, the full PEM p… npm · n8n 2026-07-22 high7.5 CVE-2026-65598 n8n before 1.123.64, 2.29.8, and 2.30.1 contains a TOCTOU race condition in the Git node's clone operation that allows authenticated users to bypass path restr… npm · n8n 2026-07-22 high8.2 CVE-2026-65597 n8n before 1.123.64, 2.x before 2.29.8, and before 2.30.1 contains a DOM-based cross-site scripting vulnerability in the HTML preview, which renders execution … npm · n8n 2026-07-22 high8.1 CVE-2026-65596 n8n before 1.123.64, 2.29.8, and 2.30.1 fails to enforce the "Allowed HTTP Request Domains" restriction on HTTP-based credentials (Header Auth, Basic Auth, Que… npm · n8n 2026-07-22 high8.8 CVE-2026-65595 n8n before 2.30.1 and 2.29.8 assigns all Public API key scopes to JWTs issued through the Token Exchange module regardless of the acting user's role. npm · n8n 2026-07-22 medium6.5 CVE-2026-65594 n8n before 2.29.8 and 2.30.x before 2.30.1 (affected from 2.27.0, when the OAuth 2.1 consent and token-issuance flow was introduced) does not verify that the a… npm · n8n 2026-07-22 medium5.4 CVE-2026-65593 n8n versions before 1.123.64, 2.29.8, and 2.30.1 contain a server-side request forgery vulnerability in the dynamic-node-parameters endpoints that lack authori… npm · n8n 2026-07-22 high8.4 CVE-2026-65592 n8n before 1.123.64, 2.29.8, and 2.30.1 contains a stored DOM cross-site scripting vulnerability in the Resource Locator component, which passes the workflow-p… npm · n8n 2026-07-22 high8.8 CVE-2026-65591 n8n contains a sanitizer bypass vulnerability in the legacy expression evaluator's computed-member handler. npm · n8n 2026-07-22 critical9.8 CVE-2026-65590 n8n before 2.29.8 and 2.30.x before 2.30.1 does not enforce shell sandbox restrictions on Linux and Windows in the @n8n/computer-use package (sandboxing was ap… npm · n8n 2026-07-22 medium6.5 CVE-2026-65589 n8n versions before 1.123.64 fail to properly mask custom HTTP header credentials in LLM sub-node execution data, writing plaintext API keys and secrets to wor… npm · n8n 2026-07-22 high8.8 CVE-2026-65016 n8n versions before 1.123.64, 2.29.8, and 2.30.1 contain a privilege escalation vulnerability in Enterprise SSO instance-role provisioning. npm · n8n 2026-07-22 high8.8 CVE-2026-65015 n8n versions before 2.30.1 contain a privilege escalation vulnerability in the AI Agents feature where the node-execution tool lacks proper authorization check… npm · n8n 2026-07-22 medium5.3 CVE-2026-65014 n8n before 2.28.0 (and before 2.27.4 on the 2.27.x branch) registers the DELETE /${restEndpoint}/test-webhook/:id endpoint before authentication middleware is … npm · n8n 2026-07-22 critical GHSA-f4f3-9g54-864m Malware in n8n-nodes-rce-pocMalware npm · n8n-nodes-rce-poc 2026-07-16 medium6.3 GHSA-3j7v-fhjg-6rh2 Duplicate Advisory: n8n: External Secrets Accessible via Workflow Expressions Outside Credentials npm · n8n 2026-07-15 medium6.5 GHSA-q6mx-qvhp-fqmg Duplicate Advisory: External Secrets Permission Bypass via Expression Parser Mismatch npm · n8n 2026-07-15 medium6.5 CVE-2026-59259 n8n before versions 1.123.61, 2.27.4, and 2.28.1 contains a permission bypass vulnerability in external secrets handling caused by a mismatch between the stati… npm · n8n 2026-07-15 medium6.3 CVE-2026-59254 n8n before 2.28.1 contains an information disclosure vulnerability where external secrets are incorrectly resolved in workflow node expressions outside credent… npm · n8n 2026-07-15 medium4.8 CVE-2026-56353 n8n contains an authentication bypass in the Chat Trigger node when configured with n8n User Auth (a non-default configuration). n8n · n8n 2026-07-15 medium6.4 CVE-2026-56352 n8n before 2.19.3 contains a file path restriction bypass in the legacy ExecuteWorkflow node's localFile source option, which reads workflow files from disk wi… n8n 2026-07-15 medium6.3 CVE-2026-56349 n8n before version 2.10.0 contains an input validation vulnerability in the Guardrail node that allows attackers to bypass default guardrail instructions. 2026-07-15

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.