By vendor

N8n vulnerabilities

Known CVEs affecting N8n products, prioritized by severity, with SEC.co remediation and detection guidance.

14 published vulnerabilities

• CVE-2026-44790HIGH 8.8

  n8n, a popular workflow automation platform, contains a critical vulnerability that allows authenticated users to execute unauthorized commands on the server. Someone with legitimate access to create or modify workflows can craft malicious Git operations that inject command-line flags, potentially extracting sensitive files or taking over the entire n8n installation. The flaw affects multiple versions and has been patched in the latest releases.

• CVE-2026-49444HIGH 8.5

  n8n is a popular workflow automation platform that lets teams build integrations and automations without extensive coding. A vulnerability in versions before 1.123.48, 2.21.8, and 2.22.4 allows authenticated users who can create or modify workflows to bypass Python Code Node sandbox protections and execute arbitrary code directly on the task runner container. This requires valid credentials but no special privileges beyond workflow creation rights, making it a significant risk in shared or multi-tenant environments.

• CVE-2026-54312HIGH 8.5

  n8n, a popular open source workflow automation platform, contains a prototype pollution vulnerability in its Microsoft SQL node that allows authenticated users to corrupt the JavaScript prototype chain across the entire application. When a user with permission to create or modify workflows supplies a malicious value in the table parameter, it permanently poisons Object.prototype for the running process, breaking validation logic application-wide and rendering the n8n instance unusable until restart. The vulnerability affects versions before 2.24.0 and requires an authenticated account but no additional user interaction.

• CVE-2026-45732HIGH 8.1

  n8n, an open-source workflow automation platform, contains a permission-escalation vulnerability in its OAuth credential reconnect endpoints. An authenticated user with read-only access to a shared OAuth credential can hijack that credential's stored tokens by initiating a reconnect flow and supplying tokens from their own external account. This allows the attacker to redirect workflows that depend on the credential to execute under their identity, potentially exfiltrating data to attacker-controlled services or taking over shared integrations permanently. The issue affects versions prior to 1.123.43, 2.22.1, and 2.20.7.

• CVE-2026-49465HIGH 7.7

  n8n workflow automation platform contains a path traversal vulnerability affecting versions before 1.123.48, 2.21.8, and 2.22.4. An authenticated user with workflow creation or modification permissions can bypass file sandbox restrictions by supplying a local filesystem path in Git node operations. This allows an attacker to read the contents of any git repository accessible to the n8n process, even if those paths are normally blocked by the N8N_RESTRICT_FILE_ACCESS_TO sandbox configuration. The vulnerability requires authentication and workflow modification privileges but could expose sensitive repository data to unauthorized access.

• CVE-2026-54304HIGH 7.7

  n8n, an open source workflow automation platform, contains a credential exfiltration vulnerability affecting versions prior to 1.123.55, 2.25.7, and 2.26.1. An authenticated user with workflow creation or modification permissions can misconfigure the SecurityScorecard node to send API credentials to attacker-controlled URLs, bypassing the platform's domain allowlist protections. This requires the attacker to have valid n8n access and knowledge of the target's SecurityScorecard credential configuration, but once exploited, directly exposes sensitive API tokens to external parties.

• CVE-2026-54311HIGH 7.7

  n8n versions before 2.25.7 and 2.26.2 contain a cross-user data leak vulnerability in the Merge node's SQL Query mode. An authenticated user can craft a malicious workflow that modifies the shared sandbox environment, poisoning it for all subsequent SQL queries executed by other users on the same instance. This means workflows belonging to different users or projects can inadvertently expose sensitive data to attackers who have created a polluted sandbox. The vulnerability requires authenticated access and only impacts multi-user deployments where multiple users can create workflows with the Merge node.

• CVE-2026-54313HIGH 7.7

  n8n, an open-source workflow automation platform, contains a flaw in how it validates filter parameters passed to MongoDB operations. A user with permission to edit workflows can inject malicious filter values into the MongoDB node's Find And Replace operation, causing the system to match and overwrite unintended documents. The vulnerability exists in versions prior to 2.24.0 and is resolved in version 2.24.0 and later.

• CVE-2026-54314HIGH 7.5

  n8n, an open-source workflow automation platform, has a vulnerability in its Compression node that allows an attacker to crash the entire n8n instance by uploading a malicious compressed file. Before version 2.24.0, the decompression feature did not limit how much data it would expand in memory, so a small file can balloon into gigabytes once decompressed, exhausting available RAM and forcing the process to restart. Since this can be triggered through a public webhook without authentication, any organization running a vulnerable n8n instance accessible over the network faces availability risk.

• CVE-2026-54308HIGH 7.2

  n8n, an open source workflow automation platform, contains a vulnerability in two specific trigger node types—MicrosoftAgent365Trigger and StripeTrigger—that fail to authenticate inbound webhook requests. An attacker who discovers the webhook URL can send forged data to trigger workflows with malicious payloads, potentially causing unauthorized actions or data manipulation. The vulnerability affects versions prior to 2.25.7 and 2.26.2.

• CVE-2026-54306MEDIUM 6.4

  n8n, a popular open-source workflow automation platform, contains a prototype pollution vulnerability that allows attackers to inject malicious data through public webhooks. If a workflow accepts external webhook input and uses that data in action nodes—such as updating records or making API calls—an attacker can manipulate those downstream actions by poisoning the data stream. The attacker essentially tricks the workflow into performing unintended operations, like modifying the wrong records or sending requests using the workflow owner's credentials. This flaw affects versions before 2.25.7 and 2.26.2.

• CVE-2026-54301MEDIUM 5.4

  n8n, an open source workflow automation platform, contains a cross-site scripting (XSS) vulnerability in its Respond to Webhook node. An authenticated user with workflow edit permissions can configure the node to serve binary content with a malicious Content-Type header. Because the binary response path bypasses n8n's Content-Security-Policy protections, this allows arbitrary JavaScript to execute in the n8n web application origin—meaning attackers can access the authenticated user's session and credentials when that user visits a specially crafted public webhook URL. The vulnerability requires an authenticated attacker and user interaction, but the damage is confined to the victim's n8n account and the data it can access.

• CVE-2026-54302MEDIUM 5.4

  n8n, a popular open-source workflow automation platform, contains a stored cross-site scripting (XSS) vulnerability in its Chat Trigger feature. An authenticated user with permission to edit workflows can inject malicious JavaScript code by manipulating the webhookId parameter. When another logged-in user visits the generated chat URL, that injected code executes within the n8n application context, giving the attacker access to the victim's session and permissions. The vulnerability requires both authentication and user interaction to exploit, limiting its immediate blast radius but remaining a meaningful risk in multi-tenant or shared n8n deployments.

• CVE-2026-54303MEDIUM 5.4

  n8n, an open source workflow automation platform, contains a reflected cross-site scripting (XSS) vulnerability in its Meta and Microsoft Teams trigger node endpoints. When a logged-in n8n user clicks a specially crafted link, the endpoint reflects unsanitized query parameters directly into the HTTP response. Because the application lacks Content-Security-Policy headers, an attacker's malicious JavaScript executes in the context of the n8n application, potentially allowing session hijacking, credential theft, or unauthorized workflow modifications. The vulnerability affects all versions prior to 2.24.0.