Skip to main content
Platform security guideReviewed

n8n vulnerabilities: advisories, settings and a register for your workflows

What n8n Cloud and self-hosted n8n each leave to you, the settings that decide who can start a workflow and what it can reach, a dated log of n8n security advisories, and a register to fill in one workflow at a time.

n8n workflow register, advisory log and webhook fixtures

Part A is a register to copy once per workflow: trigger and webhook authentication, data in and out, saved execution data, expressions, high-privilege nodes, credentials and outbound requests, each row with where to look, whether it applies to n8n Cloud, self-hosted or both, and what to record. Part B covers the instance, including queue mode.

How to use it

Part C logs ten n8n security advisories as of 14 November 2026, and Part D is a set of local webhook fixtures with their captured output. The checks in Parts A and B read settings, lists and reports; none records a secret, and Part D sends requests only to 127.0.0.1 or localhost.

n8n.txt

Introduction12 lines

HOW TO USE THIS REGISTER Copy Part A once for each published workflow that a caller outside n8n can start, and for any workflow that holds a credential to a system you care about. Fill Part B once for the instance. Read each value from the place named under "Where to look" and write it under "Record". Every check reads a setting or a list. None changes a setting, reveals a secret or sends a request to a production webhook. Never copy a credential's value, token, password or key into the register. Record the credential's type, what it can reach and who can use it. "Applies to" says where n8n's documentation places the setting: n8n Cloud, self-hosted n8n, or both, where "both" means the cited page is not limited to one of them or lists plans for each. "Source" names the n8n page or advisory each row relies on. The settings were read from n8n's documentation on 14 November 2026. n8n's v2.0 breaking changes page records several defaults that changed in 2.0, so check the source page for your version before relying on a default. What is here: Part A Workflow register: one block per workflow, rows A1 to A8. Part B Instance sheet: rows B1 to B5, including queue mode for self-hosted instances. Part C Advisory log: ten n8n security advisories, each tied to a register row, as read on 14 November 2026. Part D Webhook fixtures: a local sender and an invented receiver on 127.0.0.1, with their captured output. An illustration, not n8n.

What n8n does, and which of your systems it touches

n8n describes itself as a low-code tool.

Trigger nodes can start its workflows, and one of them is the Webhook node, which n8n says creates webhooks that can receive data from apps and services when an event occurs. n8n's page for the node says it can also return the data generated at the end of a workflow, which makes it useful for building a workflow that processes data and returns the results, like an API endpoint.

In practice an n8n instance does two jobs at once. It answers requests from outside, through the URLs its webhooks listen on, and it holds credentials for the other systems its workflows reach: a CRM, a mailbox, a database, an accounting package. n8n's documentation names the places in a workflow where you can use code: expressions, which can use JavaScript, and the Code node, which adds JavaScript or Python.

So the review questions are the same for every workflow. Who can start it? What does it receive, and what does it hand back? What does it keep afterwards? Which credentials does it hold, and what can they reach? Who can change it?

The register on this page asks those questions one workflow at a time, and the advisory log beside it lists n8n security advisories that bear on the same areas. Zapier and Make have their own guides in this library.

n8n Cloud and self-hosted n8n: what each leaves to you

n8n's documentation gives its primary deployment options as n8n Cloud, which it calls fully managed, and self-hosted n8n on your own infrastructure.

In n8n's own comparison, hosting on Cloud is done by n8n, while self-hosting means you provide and manage the infrastructure. Maintenance is handled by n8n on Cloud and is your responsibility when you self-host.

On n8n Cloud, the Updates section of Instance settings in the Cloud console sets the n8n version, the release track, the update cadence and the maintenance window, and only instance owners can change it. n8n's page on updating says it upgrades every Cloud instance at least every two weeks, so security fixes reach everyone, whichever cadence is chosen.

Self-hosted n8n security is a longer list, because the server, the database, the environment variables and each upgrade are yours to run. n8n's own steps for self-hosted users include a reverse proxy to handle TLS, encryption at rest, running its security audit, weighing the risks of community nodes or disabling them, stopping users importing external modules in the Code node, and excluding nodes such as Execute Command or SSH.

On either option, n8n's privacy and security page on what you can do says it is also your responsibility as a customer to ensure you are securing your code and data. The workflows you build, the credentials you add, who those credentials are shared with and how each webhook is protected are settings inside your instance, and that is where this page's register looks. Where n8n's documentation places the settings this page covers:

  • Plans: n8n's page on choosing how to use n8n lists one plan last in both of its plan tables, after Pro for n8n Cloud and after Business for self-hosted n8n. This page calls it the last-listed plan.
  • Documented with no limit to n8n Cloud or to self-hosted n8n on the pages this guide cites: the Webhook node's authentication methods and options, and the workflow settings that decide which executions are saved. The pages for instance roles, project roles and credential sharing list plans for both. Credential sharing is on all n8n Cloud plans and, for self-hosted n8n, on the Business plan and the last-listed plan.
  • On the last-listed plan only, for both Cloud and self-hosted: execution data redaction and log streaming. n8n's page for each lists where it is available.
  • In n8n's documentation for self-hosted instances: environment variables such as NODES_EXCLUDE and N8N_EXPRESSION_ENGINE, SSRF protection, queue mode with Redis and workers, task runner hardening and the security audit. n8n says you can secure a self-hosted instance to protect credentials and workflow data by running a security audit, setting up SSL and SSO, restricting nodes and the public API, and redacting execution data.
  • The Execute Command node is available on self-hosted n8n and, in n8n's words, isn't available on n8n Cloud.
  • Code node modules: on n8n Cloud the Code node can't import external npm modules, and n8n makes the crypto Node.js module and the moment npm package available. A self-hosted instance can enable built-in and external modules with environment variables.

Testing n8n Cloud itself

n8n's security policy on GitHub asks that a suspected vulnerability be reported through its Vulnerability Disclosure Program. This page makes no statement about what n8n allows a customer to test on n8n Cloud. Read n8n's own terms and that programme before sending test traffic to an instance n8n hosts.

n8n vulnerabilities and CVEs: where they are published and how to read them

n8n publishes security advisories in the Security Advisories area of its GitHub repository, github.com/n8n-io/n8n.

Each of the ten records in this page's log names the affected and patched versions of the n8n package on npm and describes the impact, the patched releases and temporary workarounds. Some carry a CVE id; others show no known CVE.

Two of the ten in this page's log, CVE-2026-86080 and CVE-2026-86083, carry CVE ids and have reviewed entries in the GitHub Advisory Database, each linking the National Vulnerability Database record.

Read the version fields with care. The n8n records in the log list several affected ranges, each written as below a version, with a patched version for each. The GitHub Advisory Database entries give starting versions for some of those ranges, which makes those ranges narrower.

For CVE-2026-86080, n8n's record lists below 1.123.76, below 2.37.7 and below 2.38.2, and the database entry lists below 1.123.76, 2.0.0 to below 2.37.7, and 2.38.0 to below 2.38.2.

This page's advice is to find the patched release on the line you run. If your line is not named, treat the record as not answering the question, not as a clean result.

The log is a working subset as of 14 November 2026: ten advisories, each tied to a row of the register. It leaves out other published n8n advisories, including ones for individual integration and app nodes such as the MongoDB node. Before relying on it, open n8n's Security Advisories page and read anything published since that date.

Read the conditions as well as the versions. Six of the ten records describe someone already signed in to n8n: a member who can create or modify workflows, holds Code node access, can view a workflow's executions, or knows the ID of another user's credential.

Three describe someone with no n8n account: a caller of a webhook path, a sender to a GitHub Trigger's webhook URL, and anyone able to write to Redis in queue mode.

The tenth, CVE-2026-86083, describes an expression that replaced a global, and applied only to the legacy expression engine. On this evidence, who can edit workflows deserves as much attention as who can call them.

Webhook authentication: a random path is an address, not a lock

The Webhook node's Authentication parameter offers Basic auth, Header auth, JWT auth, n8n User Auth (OAuth2) and None.

Basic, Header and JWT auth use Webhook credentials. With n8n User Auth (OAuth2), only users logged in to that n8n instance can call the webhook, and the caller must send a bearer token the instance issued; a Require Workflow Execute Permission toggle appears and is on by default.

By default the Path field holds a randomly generated path, which n8n's page says is there to avoid conflicts with other webhook nodes. This page's advice is to treat that path as an address and set Authentication on every published webhook.

GHSA-4c7j-qff5-r9cx records a case in which a caller with no credentials could run a workflow: a dynamic-path webhook URL whose server-generated identifier was the only unguessable part, and webhook resolution that matched on the path alone, so a request that left the identifier out still ran the workflow, under that project's credentials.

The record adds that node-level authentication still applies, and its workarounds include node-level webhook authentication (Basic, Header or JWT) on all active Webhook nodes that use dynamic path templates.

Other node options bear on which requests a webhook acts on. IP(s) Allowlist takes a comma-separated list of addresses: a request from outside it gets a 403 error, and if it is left blank, every address can call the URL.

Allowed Origins (CORS) sets the permitted cross-origin domains, with * as the default. Only Run If runs the workflow only when an expression over the request returns true. n8n's page says it runs after the IP allowlist and authentication checks, and that if the expression fails to evaluate, n8n logs a warning and lets the request through. The register treats it as a filter and looks to Authentication for the lock.

App trigger nodes work differently. GHSA-h59h-rf6m-7jp5 says that when a workflow was activated, n8n registered its trigger nodes with the connected services using the credentials set on those nodes. CVE-2026-86080 (GHSA-5m98-cgcr-xx3q) describes the GitHub Trigger generating a signing secret when it registered a webhook and verifying X-Hub-Signature-256 on each delivery.

When GitHub answered with a 422 because a webhook for the URL already existed, the node adopted the remote hook but kept only its id and events, discarding the secret it had generated, and deliveries to that workflow's webhook URL were then accepted from anyone.

Its workarounds include auditing the workflow's static data for a webhookId with no webhookSecret, which is a row in the register.

Public execution data: what a caller gets back, and who reads it later

Execution data leaves a workflow in two directions.

The first is the response to whoever called the webhook, which the Respond setting decides. Immediately returns the response code and the message Workflow got started. When Last Node Finishes returns the data output from the last node executed, and with Response Data set to All Entries that is all the entries of the last node in an array.

Using 'Respond to Webhook' Node hands the response to that node, whose Text option sends HTML by default.

That is how a workflow that looks a customer up can hand back fields the caller never sent. The fixtures in Part D of the asset show the shape: a request carrying an order came back with the order and three fields the caller had not sent, a CRM record id, an assignee and an internal note.

Since n8n 1.103.0, n8n wraps HTML responses to webhooks in a sandboxed iframe. GHSA-mp7q-23hg-35cf records that some response paths, such as error responses and some responses without headers, did not add the sandbox policy.

It says a member who can create and activate workflows can serve HTML that runs as a page on the n8n origin, and that when another user opens the webhook URL, the script can act with that user's session.

The second direction is inward. Workflow settings decide whether n8n saves failed production executions, successful production executions, executions started in the editor, and execution progress for each node. n8n's redaction page names what redaction hides: the input and output data of workflow executions, the data payload processed by each node.

Project roles decide who can read it. n8n calls a Project Viewer effectively a read-only role with access to all workflows, credentials and executions in a project, and lists that role on the last-listed plan only.

A Project Editor, which n8n lists on n8n Cloud Pro and on the last-listed self-hosted plan, can view, create, update and delete them.

Read access to executions can include read access to secrets. GHSA-qmvv-q3c9-wpp7 records that, when an operation failed, the Git, MongoDB Atlas Vector Store and Google Cloud Storage nodes stored an error containing a secret from their credential, and that a user who could view the workflow's executions, but not read the credential, could recover the secret from the execution data. Its workarounds include limiting execution read access to the minimum set of users who require it.

Execution data redaction hides that input and output data from people viewing executions while keeping status, timing and node names visible. n8n lists it on the last-listed plan, for both n8n Cloud and self-hosted, per workflow from n8n 2.16.0 and as an instance-wide floor from 2.26.0. n8n's page is plain about its limits: a webhook response is the raw data, not a redacted version; data a Code node logs with console.log is not redacted; and redaction doesn't change execution data in the database, so anyone with direct database access can read it.

In n8n's documentation for self-hosted instances, pruning deletes finished executions on a schedule, and n8n enables it by default. n8n prunes executions that finished more than EXECUTIONS_DATA_MAX_AGE hours ago (default 336 hours, 14 days), and when the total exceeds EXECUTIONS_DATA_PRUNE_MAX_COUNT (default 10,000) it deletes executions from oldest to newest.

Annotated executions are never pruned. n8n's privacy page says self-hosted users are responsible for deleting user data, and recommends configuring n8n to prune execution data automatically every few days.

Expressions, the Code node and nodes that reach the host

Expressions are the JavaScript snippets n8n evaluates at runtime to set node parameters dynamically.

On a self-hosted instance, N8N_EXPRESSION_ENGINE chooses the engine the server uses: vm runs expressions in a sandboxed V8 isolate and is the default from n8n 2.35.0, quickjs runs them in a QuickJS sandbox, and legacy runs them without isolation. Earlier versions default to legacy. The editor has its own setting, N8N_EXPRESSION_ENGINE_FRONTEND, available from n8n 2.41.0, which defaults to legacy; n8n strongly recommends quickjs for it.

Expression sandboxes have their own advisories. GHSA-gx3v-3x3v-f8r5 says an authenticated user with permission to create or modify workflows could escape the isolation applied to workflow expression evaluation and execute arbitrary code on the n8n host. CVE-2026-86083 applied only to instances running the legacy engine, and its workarounds include setting N8N_EXPRESSION_ENGINE to vm.

Expressions also carry incoming data into other systems. n8n's security audit reports expressions used in the Execute Query and Query Parameters fields of SQL nodes. The register asks, for each workflow, which parameters take values from a webhook or form, and where those values end up: a query, a filter, a command, a URL or a message.

The Code node runs JavaScript or Python as a step in a workflow. n8n's v2.0 breaking changes page says task runners are enabled by default from 2.0 and that all Code node executions run on them.

For self-hosted instances, n8n's hardening page recommends external mode, which launches runners as separate containers, along with a distroless image, the unprivileged nobody user, a read-only root filesystem and an AppArmor profile. GHSA-m3hg-p5r9-fg9h says an authenticated user with Code node access could execute arbitrary commands within the runner container, and that on v1.x instances that have not enabled task runners, Code node JavaScript executes directly in the main n8n process instead.

Whether expressions and the Code node can read the server's environment variables is set by N8N_BLOCK_ENV_ACCESS_IN_NODE, and n8n's documentation gives two answers for its default. The v2.0 breaking changes page says the default is now true, blocking access from the Code node; the table of security environment variables lists false. The register records the value set on your instance instead of relying on either page.

n8n's security audit also reports official risky nodes, which its documentation describes as built-in nodes that can be used to fetch and run any code on the host system. On 14 November 2026 the list in the audit's source code named the node types executeCommand, code, function, functionItem, httpRequest, ssh and ftp.

The Execute Command node runs shell commands on the host machine that runs n8n, or in the n8n container under Docker, and in queue mode on the worker that executes the production run. n8n disables it by default from 2.0.

On a self-hosted instance, NODES_EXCLUDE stops n8n loading a node at all, and n8n suggests Execute Command and Read/Write Files from Disk as nodes you might start with.

GHSA-9p7v-45m2-wxgj concerns deprecated nodes. It says the Function and Function Item nodes run user code in the vm2 sandbox and the LangChain Code node runs it in the n8n main process, and that an authenticated user with permission to create or modify workflows could use these nodes to execute arbitrary code in the main process, outside the task runner isolation that applies to the Code node.

In the versions its patch text names, these nodes are deprecated and blocked by default: saving a workflow that adds or modifies one is rejected, while workflows already saved with them continue to run unchanged. The register therefore asks you to list any that remain.

Three of the four records in this section start from someone who can create or modify workflows or holds Code node access. The register therefore records who can edit each workflow, and treats edit access to a workflow that holds an Execute Command, Code or HTTP Request node as access to whatever that node can reach.

Nodes that make outbound requests raise the server-side request forgery question. From n8n 2.12.0, a self-hosted instance can set N8N_SSRF_PROTECTION_ENABLED to true, and n8n then validates outbound HTTP requests from user-controllable nodes, such as the HTTP Request node, against blocked and allowed ranges, including redirect targets. n8n describes it as an additional application-level defence and says network-level protections should always be the primary line of defence. The SSRF guide in this library covers the wider problem.

Credential scope: what each credential reaches, and who can use it

On a self-hosted instance, n8n creates a random encryption key on first launch, saves it in the ~/.n8n folder and uses it to encrypt credentials before they are saved to the database.

In queue mode the same key has to be set on every worker.

A credential can be shared with a user or with a project, and the people it is shared with get the Can use role: they can run and publish workflows with it, but can't see or edit its details. Instance owners and instance admins can view and share all credentials on an instance, and a credential's Sharing tab lists everyone with access and every project that uses it.

The register records who can use each credential, not only who owns it. GHSA-h59h-rf6m-7jp5 records that workflow activation did not check whether the user publishing a workflow had access to the credentials on its trigger nodes, so a member who knew the ID of another user's credential could have n8n create or delete webhooks on the connected service with that credential's privileges. Its workarounds include auditing active workflows for trigger nodes that use credentials owned by another user.

For each credential, the register records its type, the system it reaches and the scope or role it holds there, its owner, who and which projects it is shared with, and which workflows use it. It never records the value. The credential's type, its Sharing tab and the connected service's own settings answer the register's questions, so nothing in it asks you to open, reveal or copy a secret. If a credential's value has already been exposed, the secrets exposure guide covers revoking and rotating it.

Self-hosted n8n security in queue mode: Redis, workers and the shared key

n8n's documentation for self-hosted instances says queue mode provides the best scalability.

The main instance handles timers and webhook calls and generates each execution without running it, Redis holds the queue, and a worker picks the execution up, reads the workflow from the database, runs it and writes the results back. Optional webhook processors add a layer that handles incoming webhook requests.

n8n's queue mode page gives the facts that decide who can reach what. By default, Redis runs on localhost on port 6379 with no password, and a username and password are optional settings. The main instance's encryption key must be shared with every worker and webhook processor so they can access credentials stored in the database.

And each worker runs a server with optional endpoints: health checks when QUEUE_HEALTH_CHECK_ACTIVE is enabled, a credentials overwrite endpoint, and /metrics.

GHSA-fmmv-p585-7c8x records what write access to Redis meant in one case. In queue mode, the internal handler that installs a community package applied none of the checks the normal install path performs, so anyone able to write to that Redis instance could have n8n download, install and load any npm package on every instance in the cluster, with no n8n account.

Its first workaround is restricting access to the Redis instance to only trusted n8n components, using authentication and network-level controls.

The register's queue mode block records where Redis runs, whether it asks for a password (yes or no, never the value), which machines and networks can reach it, which machines hold the encryption key, and whether worker endpoints can be reached from outside your private network.

Where Execute Command is enabled, n8n's page for the node says that in queue mode it runs on the worker executing the task in production mode, so a worker's own access belongs in the same block.

How to use the register and the advisory log

The asset on this page has four parts.

Fill Part A once for each published workflow that a caller outside n8n can start, and for any workflow that holds a credential to a system you care about. Fill Part B once for the instance. Then compare the version in Part B with the ranges in Part C.

  • Work from the screens and settings each row names. Every row reads a value, and none asks you to change a setting, reveal a secret or send a request to a production webhook.
  • On a self-hosted instance, run n8n's security audit first. n8n documents running it with n8n audit from the command line, with a POST call to the public API's /audit endpoint authenticated as the instance owner, or with the n8n node. It produces risk reports on credentials, database, file system, nodes and instance. The instance report covers unprotected webhooks, missing security settings and whether the instance is outdated.
  • Start with workflows whose trigger has Authentication set to None, then those holding Execute Command, Code or HTTP Request nodes, then those whose credentials reach customer or financial data.
  • Mark each Part C row affected, not affected or not applicable for your version, with the reason. A row whose release line is not named stays unanswered until the release notes for your line settle it.
  • Use Part D only against its own invented receiver or a local test instance holding a copy of the workflow that sends nothing on to other systems. An accepted request runs the workflow it reaches.
  • Fill the register again after an upgrade, a new published workflow, or a change to who can edit workflows or use credentials.

The webhook fixtures, and what running them showed

Part D is an illustration, not n8n and not a copy of n8n's code.

It is four small files: the invented values the two sides share, a receiver, a sender and a script that runs them. Apart from each other, they import only node:http and node:crypto, and they install no packages. The receiver asks for port 0 on 127.0.0.1. Node.js's net documentation says that when server.listen() is given port 0, the operating system will assign an arbitrary unused port.

It stands in for four webhook-triggered workflows: one with no check, one that needs a token in a header, one that needs an HMAC-SHA256 signature of the body, and one that needs the token and then answers with every field its last step produced.

It was written and run on Node.js v26.0.0, the only version it was run on, and every output in Part D was copied from the captured files by a script.

In the run Part D prints as RUN 1, the webhook with no check accepted a request that carried no credential and started an execution. The header webhook refused a request with no token header (401) and one with the wrong value (403), and accepted the lab token.

The signed webhook refused a missing signature (401), a signature made with the wrong secret (403) and a body changed after it was signed (403), and accepted the correctly signed body. The receiver started four executions in all, one for each accepted request.

The ninth request sent the lab token to the webhook that answers with every field, and the response carried crmContactId, assignedTo and internalNote, three fields the caller had not sent.

The receiver hashes both values with SHA-256 before comparing them with crypto.timingSafeEqual. The Node.js crypto documentation says timingSafeEqual compares the underlying bytes using a constant-time algorithm, and that an error is thrown if the two values have different byte lengths.

To make the same checks on an n8n instance of your own, you need a local test instance holding a copy of the workflow whose later steps send nothing to other systems, and whose Webhook node uses a Header auth credential made from the lab's invented header name and value in fixtures.mjs, so no real secret is involved.

Then run node sender.mjs with the copy's webhook URL and the word header. Record the status code and body of each response, and read the copy's executions list. This page does not state which status codes n8n returns for a refused credential, so record what your instance returns.

The sender refuses any host other than 127.0.0.1 and localhost, and in the run Part D prints as RUN 2 it refused a non-loopback address before sending anything.

What the register leaves open

The register is a record of settings and access.

It leaves several things open, and each needs a different kind of work.

  • How a workflow behaves when an incoming field holds hostile input, such as a value an expression drops into a query or a URL. That takes testing on a copy of the workflow, not reading its settings.
  • Whether an advisory was used against your instance before you upgraded. A patched version closes the flaw from the upgrade onwards and says nothing about the time before it.
  • What sits outside the screens the register reads: the database itself, which n8n's redaction page says anyone with direct database access can read, server and runner logs, and the systems your workflows send data to.
  • n8n Cloud's own infrastructure, and the services your credentials reach. Their owners answer for those.
  • Events over time. Where log streaming is on your plan, the audit events n8n can stream include failed logins, credential sharing and workflow activation, and the security logging guide covers what to keep and what to alert on.
  • If you think a workflow or credential has already been misused, call an incident response specialist first. Clever Ops does not provide emergency incident response or round-the-clock monitoring.

Where a Clever Ops test fits

This guide is for owners checking their own n8n instance.

Clever Ops tests what customers reach through a browser or an API. Where your web application or its API sends data to an n8n webhook, or acts on what a workflow returns, testing your application's side of that exchange is work for a scoped web application and API penetration test. n8n Cloud is run by another business, and the methodology keeps such services out of scope unless their owner agrees.

Where Clever Ops built or hosts your application, the work counts as a security review, not an independent test, and its report names who built the application and who hosts it. Load and denial-of-service testing is referred to a load-testing specialist and needs your host's written approval, and this guide includes no destructive workflow test.

A report is evidence for a decision, such as a customer's or an auditor's, and it is not a certificate.

Bring the filled-in register to the scoping call. It shows which workflows your application depends on, what each one receives and returns, and which credentials sit behind them, which is what a scope needs to decide what is in and what stays out.

Frequently asked questions

In the Security Advisories area of the n8n repository on GitHub, github.com/n8n-io/n8n. Each of the ten records in this page's log lists the affected and patched versions of the n8n package, the impact and temporary workarounds. Some records carry a CVE id and have a reviewed GitHub Advisory Database entry that links the National Vulnerability Database record; others show no known CVE. A search by CVE id alone can therefore miss some. The log on this page is a dated subset, not a replacement for that list.

Yes, on a schedule the instance owner can shape. n8n's page says it upgrades every Cloud instance at least every two weeks, so security fixes reach everyone whichever cadence is chosen. In the Cloud console, the instance owner picks the version, a Beta or Stable release track, the update cadence and a maintenance window, and an update to a major version, or one that runs a database migration, can't be rolled back. On self-hosted n8n, upgrades are yours, and n8n's v2.0 notes recommend pinning to a specific version number.

Set the Webhook node's Authentication to Basic auth, Header auth, JWT auth or n8n User Auth (OAuth2) rather than None, and don't rely on the generated path, which n8n creates to avoid conflicts between webhook nodes. IP(s) Allowlist can limit callers to listed addresses, and a request from anywhere else gets a 403 error. Only Run If is a filter: n8n's page says that if its expression fails to evaluate, n8n logs a warning and lets the request through.

That is your decision, made with what the node does in view. It runs shell commands on the host machine that runs n8n, n8n says it can introduce significant security risks in environments that operate with untrusted users, and it is disabled by default from n8n 2.0. It isn't available on n8n Cloud. If you enable it by removing it from NODES_EXCLUDE, this page's advice is to record who can edit workflows on that instance, and to list every workflow that uses the node in row A6 of the register.

No. Redaction hides each node's input and output data from people viewing executions, and users with the reveal scope, which instance owners and admins hold by default, can still reveal it, with the action logged. What n8n's page says it does not cover includes the raw response sent back to a webhook caller, console.log output from the Code node, authentication headers in outbound requests, and the database itself, which anyone with direct database access can read. n8n lists redaction on the last-listed plan.

It produces risk reports, one each for credentials, database, file system, nodes and instance. Credentials: credentials not used in a workflow, in an active workflow or in a recently active workflow. Database: expressions in the Execute Query and Query Parameters fields of SQL nodes. File system: nodes that interact with the file system. Nodes: official risky nodes, community nodes and custom nodes. Instance: unprotected webhooks, missing security settings and whether the instance is outdated. n8n documents running it as n8n audit from the command line, through the public API as the instance owner, or with the n8n node.

Scope the right test for your application

Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.