By vendor

N8n vulnerabilities

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

33 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-59257HIGH 8.8

  n8n versions before 1.123.61, 2.27.4, and 2.28.1 are vulnerable to SQL injection through the legacy MySQL v1 node when it processes user-controlled input in SQL queries. If an n8n workflow connects an externally-accessible trigger (like a Webhook) to a MySQL v1 operation, an attacker can inject malicious SQL commands that execute with the privileges of the configured database account. The newer MySQL v2 node is not affected because it properly isolates SQL code from user input.

• 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-56351HIGH 8.2

  n8n, a workflow automation platform, has a SQL injection vulnerability affecting its database query nodes (MySQL, PostgreSQL, and SQL Server). An authenticated user with permission to create workflows can craft malicious table or column names within node configuration to execute arbitrary SQL commands against connected databases. This bypasses normal database access controls and allows an attacker to read, modify, or delete data. The vulnerability requires an authenticated account and specific node configuration privileges, but poses a significant risk to organizations relying on n8n for sensitive data operations.

• 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-56776HIGH 7.4

  n8n versions before 1.123.55, 2.25.7, and 2.26.2 have a permission flaw in their test-run feature that lets authenticated users with read-only access to workflows actually execute those workflows. When someone with restricted permissions triggers a test run, the workflow runs for real, potentially making unintended changes to connected systems, pulling or pushing data where it shouldn't, or calling external APIs on behalf of the organization. This bypasses the intended access controls that should prevent read-only users from executing workflows.

• 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-59206HIGH 7.1

  n8n, an open source workflow automation platform, contains a prototype pollution vulnerability that allows authenticated users with basic workflow creation permissions to corrupt the platform's core object model. By crafting and saving a malicious workflow, an attacker can manipulate how the application handles object properties globally, effectively tricking the system into treating unauthenticated requests as if they came from a privileged user. This bypass exposes sensitive endpoints that list users and projects, compromising confidentiality and potentially enabling further reconnaissance for lateral movement.

• CVE-2026-59208MEDIUM 6.8

  n8n workflow automation instances can be tricked into granting unauthorized access when they trust multiple token issuers for authentication. An attacker with a valid token from one trusted issuer can impersonate users from another trusted issuer if their token's subject identifier matches a victim's username. The flaw stems from n8n only checking the user's identifier in the token while ignoring which issuer provided it, creating a mismatch between authentication sources.

• CVE-2026-59207MEDIUM 6.5

  n8n's AI Agents feature contains a credential access control bypass that allows a member-level user with read-only access to a shared credential to exfiltrate that credential's secret to an attacker-controlled server. The vulnerability exists because the platform fails to enforce domain restrictions on HTTP requests made by MCP (Model Context Protocol) tools used within AI Agents workflows. An attacker with legitimate but limited access to a credential can point an MCP tool at their own server and capture the credential secret during execution. This affects n8n versions prior to 2.27.4 and 2.28.1.

• CVE-2026-59209MEDIUM 6.5

  n8n, an open-source workflow automation platform, contains a vulnerability that allows authenticated users with basic editor access to steal sensitive credentials embedded in HTTP request headers. A user with 'use-only' permissions on a shared workflow can extract secrets through pagination expressions and leak them as part of workflow item data. This affects versions before 1.123.61, 2.27.4, and 2.28.1.

• 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-56778MEDIUM 6.4

  n8n, a popular workflow automation platform, contains a flaw in its Public API that allows users with read-only access to workflows to trigger re-executions of those workflows. The vulnerability stems from an authorization check that uses the wrong permission scope—it verifies read access when it should verify execute access. This means an authenticated user who should only be able to view a shared workflow can actually run it again, circumventing the intended separation between viewing and executing. The issue affects n8n versions before 2.25.7 and 2.26.x before 2.26.2, particularly in multi-user or cross-project setups where workflows are shared.

• CVE-2026-56350MEDIUM 6.3

  n8n versions before 2.8.0 contain an authentication bypass flaw that affects organizations using single sign-on (SSO). Authenticated users can exploit this vulnerability to disable SSO enforcement through the API and create local password credentials, allowing them to circumvent both SSO policies and any multi-factor authentication requirements mandated by your identity provider. This means an attacker with legitimate credentials could establish a persistent backdoor account that sidesteps your organization's centralized identity controls.

• 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.

• CVE-2026-56356MEDIUM 5.4

  n8n's Chat Trigger node has a stored cross-site scripting (XSS) flaw in its Custom CSS field. A workflow creator or editor can inject malicious JavaScript that gets saved in the workflow and executes when anyone visits the public chat page. This affects n8n versions before 1.123.27, versions 2.0.0 through 2.13.2, and version 2.14.0. The vulnerability requires authenticated access to create or modify workflows, so it's limited to users with those permissions, but the actual attack—XSS against chat visitors—happens without further interaction needed from those visitors.

• CVE-2026-56358MEDIUM 5.4

  n8n, a popular workflow automation platform, has a stored cross-site scripting (XSS) vulnerability in its Form Trigger node. Users with permission to create workflows can embed malicious code into form designs that will execute automatically whenever someone visits the form. This affects n8n versions before 1.123.25 (in the 1.x line) and before 2.11.2 (in the 2.x line), with a fix also available in 2.12.0. The vulnerability requires the attacker to already have workflow creation access, limiting the immediate blast radius but creating significant risk for organizations where multiple users can design forms.

• CVE-2026-56359MEDIUM 5.4

  n8n versions prior to 2.8.0 contain a cross-site scripting (XSS) vulnerability in the credential management system. Authenticated users can inject malicious JavaScript into OAuth2 credential fields, specifically the Authorization URL. If a victim clicks the OAuth authorization button while viewing a crafted malicious credential, arbitrary JavaScript executes in their browser with their session privileges. This requires both authentication and user interaction, limiting its scope but creating a meaningful risk in shared or collaborative n8n deployments.

• CVE-2026-56775MEDIUM 5.4

  n8n workflow automation platform versions before 1.123.55, 2.25.7, and 2.26.2 contain an authorization flaw in test-run management endpoints. The vulnerability allows authenticated users with read-only viewer permissions to perform state-changing actions—starting new test runs, canceling active runs, and deleting run records—on workflows they should only be able to view. This affects deployments using n8n's Advanced Permissions feature (Enterprise and Cloud editions) with project-based access controls. The flaw stems from incorrect permission scope validation during endpoint authorization.

• CVE-2026-56777MEDIUM 5.0

  n8n, a popular workflow automation platform, contains a security flaw in its Python Code node that allows authenticated users to bypass safety checks and access underlying system modules. This vulnerability only affects self-hosted instances where Python task execution is enabled and environment variable access is permitted. An attacker with workflow creation permissions could potentially read sensitive environment variables that the task runner process can access, such as API keys or database credentials.

• CVE-2026-59253MEDIUM 5.0

  n8n, a workflow automation platform, contains a flaw in how it checks permissions when users create or modify workflows. An authenticated user can craft specially-formatted requests to place workflows into folders belonging to other projects—even if they shouldn't have access to those projects. This is a logical integrity issue rather than a confidentiality breach; no data is exposed, but folder organization and project boundaries can be violated.

• CVE-2026-58661MEDIUM 4.3

  n8n workflow automation platform versions before 2.28.0 (or 1.123.58 on the legacy 1.x branch) contain a disk space exhaustion vulnerability in file upload functionality. An authenticated attacker can repeatedly upload files through the data-table endpoint without triggering proper quota enforcement, causing files to accumulate in temporary storage until the system's periodic cleanup cycle runs. This can eventually consume all available disk space on the server, leading to service disruption. The vulnerability requires valid user credentials to exploit, limiting exposure to authenticated threat actors.

• CVE-2026-56354MEDIUM 4.1

  n8n, a popular workflow automation platform, contains vulnerabilities in its Form Node that allow authenticated users to inject malicious content. Specifically, two issues exist: unsanitized HTML in description fields can enable stored cross-site scripting (XSS) attacks, and overly permissive iframe sandbox settings can be exploited for phishing redirects. An attacker with workflow creation permissions could craft a malicious form that, when viewed by end users, executes scripts in their browsers or redirects them to attacker-controlled sites. The vulnerability affects versions before 1.123.24 in the 1.x branch and before 2.10.4 and 2.12.0 in the 2.x branch.

• CVE-2026-56357MEDIUM 4.0

  n8n's GitHub Webhook Trigger node accepts webhook requests without verifying their authenticity, allowing attackers to forge webhook events if they know the webhook URL. An attacker could send spoofed GitHub webhook payloads directly to a workflow, potentially triggering unintended automation actions. This is a signature verification bypass rather than a complete authentication failure, meaning the vulnerability requires knowledge of the specific webhook URL but does not require credentials or sophisticated network access.

• CVE-2026-56360MEDIUM 4.0

  n8n workflow automation platform versions before 1.123.18 and 2.6.2 contain a webhook signature verification flaw in the Zendesk integration node. The vulnerability allows attackers to send unauthenticated requests to known webhook URLs, injecting arbitrary data into workflows. While the attack requires knowledge of a specific webhook endpoint URL and cannot directly compromise confidentiality or availability, it creates a path for data tampering and unauthorized workflow execution within an organization's automation infrastructure.