Chat Hub chat-only users: n8n’s October 14 security advisory
What n8n’s October 14, 2026 advisory says about Chat Hub chat-only users, affected versions, published fixes and temporary mitigation.
Checked against the cited sources on .
What the Chat Hub announcement disclosed
Chat Hub chat-only users are the subject of n8n’s October 14, 2026 security advisory, GHSA-43v8-hjhm-chjp. The announcement discloses a permissions vulnerability and published fixes; it does not introduce an intended capability for these users. The advisory does not state when the vulnerable behavior began.
The issue concerns users with the chat user role, who cannot create or edit workflows but could exceed their role’s limits through tools. We think the key distinction is permission: a restricted chat role should be assessed by what it can invoke, as well as what it can edit.
Chat Hub tool types and the sandbox boundary
According to the advisory, Chat Hub chat-only users could add and run tools that execute code in the task runner sandbox, access files within n8n-allowed directories, or use instance workflows, Data Tables and agents. These are the capabilities described in the disclosure, rather than evidence that customers experienced those actions.
The Chat Hub sandbox disclosure does not establish a sandbox escape or give exploitation frequency.
Published fixes and what administrators should do now
For teams administering instances with chat users, n8n recommends upgrading to a fixed version or later. Its October 14, 2026 advisory lists the following affected-version expressions and fixes without assigning release-channel labels to them.
| Affected expression | Published fix |
|---|---|
| < 1.123.85 | 1.123.85 |
| < 2.43.5 | 2.43.5 |
| < 2.44.1 | 2.44.1 |
If administrators cannot upgrade immediately, the advisory includes temporarily disabling Chat Hub when it is unnecessary. It explicitly warns that its workarounds do not fully remediate the risk. This article covers that one temporary measure, rather than the full workaround list.
Our practical recommendation is to give an administrator ownership of comparing the deployed version with the published fixes and arranging the upgrade. As an additional editorial suggestion, review which tool capabilities the team intends chat users to have; that review is separate from the advisory’s remediation.
What the advisory leaves unspecified
The announcement does not state edition coverage, handling for other editions or hosted plans, n8n Cloud patch status, or deployment-specific handling. It also provides no upgrade commands, verification procedures or procedure for disabling Chat Hub. Those details should not be inferred from the version list.
As an additional editorial suggestion, ask how upgrade completion will be checked.
