Products / n8n
n8n
156 records.
- n8n: Prototype Pollution in XML and GSuiteAdmin node parameters lead to RCE A crafted node parameter in a workflow pollutes Object.prototype, and the pollution can be escalated to code execution on the server.
- n8n Vulnerable to XSS via Binary Data Inline HTML Rendering Binary data without a filename is served inline on the main origin without download or CSP headers, so crafted HTML runs script in a victim's session.
- n8n Vulnerable to LDAP Filter Injection in LDAP Node Unescaped LDAP metacharacters in user input reach the search filter of the n8n LDAP node, letting attackers alter queries and bypass workflow checks.
- n8n's Source Control SSH Configuration Uses StrictHostKeyChecking=no Source control SSH disables host key verification, which lets a network attacker impersonate the Git server and intercept repository data.
- n8n has Multiple Remote Code Execution Vulnerabilities in Merge Node AlaSQL SQL Mode The AlaSQL sandbox behind the Merge node's SQL mode fails to block certain statements, letting an authenticated workflow editor read host files and run code.
- n8n: LDAP Email-Based Account Linking Allows Privilege Escalation and Account Takeover LDAP login automatically links an identity to any local account with a matching email, so a user who controls their LDAP email can take over an admin account.
- n8n Has External Secrets Authorization Bypass in Credential Saving Saving a credential that references an external secret by name returns its plaintext value without the external-secret list permission being checked.
- n8n is Vulnerable to Credential Theft via Name-Based Resolution and Permission Checker Bypass in Community Edition A member user resolves another user's credential by ID, and a permission check skips generic HTTP credential types, letting a workflow decrypt and use them.
- n8n Has Authorization Bypass in OAuth Callback via N8N_SKIP_AUTH_ON_OAUTH_CALLBACK With an environment flag set, the OAuth callback skips verifying that the state belongs to the current user, so tokens are stored in an attacker-controlled credential.
- n8n has In-Process Memory Disclosure in its Task Runner An authenticated user can allocate uninitialised buffers in the task runner, exposing leftover in-process memory such as tokens and secrets.
- n8n has Webhook Forgery on Zendesk Trigger Node Requests to a Zendesk trigger webhook URL are accepted without verifying the HMAC signature, so anyone knowing the URL can start the workflow with forged data.
- n8n: SQL Injection in MySQL, PostgreSQL, and Microsoft SQL nodes Database workflow nodes do not escape table and column identifiers, so a crafted name in node configuration injects arbitrary SQL.
- n8n has a Guardrail Node Bypass Crafted user input in an n8n workflow gets past the default instructions of the Guardrail node, defeating its safety checks.
- n8n has an Authentication Bypass in its Chat Trigger Node The Chat Trigger's n8n user authentication can be circumvented, letting unauthenticated requests reach the webhook workflow.
- n8n: Webhook Forgery on Github Webhook Trigger The GitHub trigger never checks HMAC signatures, so anyone who knows the webhook URL can send forged events that start the workflow.
- n8n has an SSO Enforcement Bypass in its Self-Service Settings API An SSO-authenticated user can disable SSO enforcement on their own account through a settings endpoint, then set a local password and log in directly.
- n8n Vulnerable to Stored XSS via Various Nodes A workflow author embeds script in node-rendered pages such as forms and chat, which then runs for any visitor.
- n8n has Unauthenticated Expression Evaluation via Form Node Unauthenticated form submissions with a leading equals sign make n8n evaluate the field as an expression, which can be chained with a sandbox escape to run code.
- n8n has a Sandbox Escape in its JavaScript Task Runner A workflow author can break out of the JavaScript task runner sandbox and execute code on the host outside its boundary.
- n8n has Arbitrary File Read via Python Code Node Sandbox Escape The Python Code node sandbox fails to restrict certain built-in objects, letting a workflow author read host files or execute code outside the sandbox.
- n8n: Expression Sandbox Escape Leads to RCE Crafted expressions in workflow parameters escape the expression sandbox and run system commands on the host for users who can edit workflows.
- n8n has Potential Remote Code Execution via Merge Node The Merge node's SQL query mode lets an authenticated workflow author run code and write files on the n8n host.
- n8n has Arbitrary Command Execution via File Write and Git Operations A user who can edit workflows chains file-write nodes with git operations to run arbitrary shell commands on the host.
- n8n's domain allowlist bypass enables credential exfiltration Wildcard domain patterns in the credential allowlist fail to restrict domains correctly, so credentials are attached to requests sent to unintended hosts.
- n8n's Unsafe Buffer Allocation Allows In-Process Memory Disclosure in Task Runner Untrusted task runner code can call unsafe buffer allocation and receive uninitialized memory that may hold residual data from the same process.
- n8n Has Expression Escape Vulnerability Leading to RCE Crafted expressions in workflow parameters escape the expression evaluator's restrictions and run operating system commands on the host.
- n8n Vulnerable to Command Injection in Community Package Installation An administrator can inject shell metacharacters into the community package installation flow, so the n8n host runs attacker-chosen commands.
- n8n's Improper CSP Enforcement in Webhook Responses May Allow Stored XSS The CSP sandbox is not applied to some webhook and HTTP responses, so an author's HTML runs with the origin's privileges for other users.
- n8n has a Python sandbox escape An authenticated user can break out of the Python code node sandbox when task runners are enabled, running code outside the intended boundary.
- n8n has OS Command Injection in Git Node Workflow editors can pass input to the n8n Git node that reaches shell commands, letting them run OS commands or read host files.
- n8n's Improper File Access Controls Allow Arbitrary File Read by Authenticated Users Workflow authors can read sensitive files on the host, such as configuration and stored credentials, through file access nodes.
- n8n Merge Node has Arbitrary File Write leading to RCE The Merge node's SQL query mode lets authenticated workflow editors write arbitrary files to the server, which can lead to code execution.
- n8n Vulnerable to Arbitrary File Write on Remote Systems via SSH Node Unauthenticated file uploads routed through workflows to SSH transfers do not validate metadata, letting filenames write to unintended remote paths.
- n8n Has Stored Cross-site Scripting via Markdown Rendering in Workflow UI Markdown rendering in workflow sticky notes lets a stored script run in other users' sessions when they open the workflow.
- n8n Unsafe Workflow Expression Evaluation Allows Remote Code Execution User-authored workflow expressions run in an insufficiently isolated runtime, letting authenticated users execute code as the n8n process.
- n8n: Webhook Node IP Whitelist Bypass via Partial String Matching The n8n webhook IP whitelist used substring matching, so a client whose address merely contains a trusted entry is accepted.
- n8n's Missing Stripe-Signature Verification Allows Unauthenticated Forged Webhooks The Stripe Trigger never checks incoming webhook requests against the stored signing secret, so anyone who knows the URL can start workflows with forged events.
- n8n Vulnerable to Unauthenticated File Access via Improper Webhook Request Handling A publicly reachable form workflow in n8n lets unauthenticated requests read files on the underlying server.
- n8n Vulnerable to RCE via Arbitrary File Write An authenticated user can make n8n write files that lead to untrusted code running on the server.
- n8n's Possible Stored XSS in "Respond to Webhook" Node May Execute Outside iframe Sandbox HTML returned by the Respond to Webhook node escapes the iframe sandbox meant to contain it, so injected scripts run in the editor's top-level window.
- n8n Vulnerable to Arbitrary Command Execution in Pyodide based Python Code Node An authenticated user who can edit workflows writes Python in the Pyodide-based Code node and escapes its sandbox to run commands as the n8n process.
- Self-hosted n8n has Legacy Code node that enables arbitrary file read/write In legacy Code node mode, internal helper functions remain reachable from workflow scripts, letting editors read and write host files outside the intended restrictions.
- n8n Vulnerable to Remote Code Execution via Expression Injection Workflow expressions from authenticated users are evaluated in an insufficiently isolated context, letting them run code as the n8n process.
- n8n vulnerable to Remote Code Execution via Git Node Custom Pre-Commit Hook A workflow can point Git's hooks path at a repository directory containing a pre-commit script, which Git then runs as a local command on the n8n host.
- n8n Vulnerable to Remote Code Execution via Git Node Pre-Commit Hook Committing from a workflow's Git node after cloning an untrusted repository runs that repository's pre-commit hook, executing attacker code in n8n.
- n8n: Execute Command Node Allows Authenticated Users to Run Arbitrary Commands on Host Any user who can build workflows can run arbitrary shell commands on the host through the Execute Command node when it is enabled.
- Stored XSS in n8n LangChain Chat Trigger Node via initialMessages Parameter A script stored in the initial messages setting runs in the browser of every visitor to the public chat page.
- n8n symlink traversal vulnerability in "Read/Write File" node allows access to restricted files A user who can create symlinks, for example through a command node, can point the file node past its directory restrictions to read or write protected paths.
- Stored XSS in n8n Form Trigger allows Account Takeover via injected iframe and video/source An authenticated user stores HTML in a form trigger using iframe srcdoc or video and source onerror payloads, which run in victims' browsers and steal session tokens.
- n8n is vulnerable to Improper Authorization through its `/stop` endpoint The execution stop endpoint does not check workflow ownership, so an authenticated user can halt runs belonging to other users.