n8n-io n8n Chat Hub authorization bypass lets chat-only users register restricted tools

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-118640?

CVE-2026-118640 is a vulnerability classified as Incorrect Authorization, affecting n8n (affected versions: < 1.123.85, 2.44.0 – < 2.44.1, and other affected versions). This vulnerability is rated Medium, with a CVSS score of 5.3. Current sources do not report this vulnerability as exploited.

Overview

Original source data

n8n before 1.123.85, 2.43.5, and 2.44.1 contains an authorization bypass vulnerability in Chat Hub that allows chat-only users to register restricted tool types. Users with the global:chatUser role can add and run tools through chat to execute sandboxed code, access permitted files, and use instance workflows, Data Tables, and agents.

Affected products and scope

  • n8n-io n8n: affected from 0 to less than 1.123.85; fixed in 1.123.85.
  • n8n-io n8n: affected from 2.0.0 to less than 2.43.5; fixed in 2.43.5.
  • n8n-io n8n: affected from 2.44.0 to less than 2.44.1; fixed in 2.44.1.

Branches and statuses outside these explicitly listed ranges are not established by the available evidence.

Technical details

Chat Hub blocked only a limited set of tool types for users with the global:chatUser role. The authorization bypass lets those users register restricted tools even though the role does not allow them to create or edit workflows. They can then run the tools through chat to execute code in the task runner sandbox, read and write files in directories allowed by n8n, or use the instance's workflows, Data Tables, and agents. This is CWE-863 Incorrect Authorization, where the authorization check does not adequately constrain tool registration by role. The attack is network-reachable and requires an authenticated low-privilege chat user; no additional interaction from another user is indicated by the supplied attack characteristics. The advisory does not disclose the specific endpoint, handler, authorization condition, or exploit request, so those implementation details remain unknown.

Exploitability

The attack is reachable over the network through Chat Hub. An attacker must already hold the global:chatUser role, so the vulnerability is not unauthenticated. The supplied attack characteristics indicate low complexity, no additional attack requirements, and no user interaction. The supplied record does not identify a public exploit, and its known_exploited field does not provide an exploited status. This does not prove that exploitation has not occurred in practice.

Technical impact

Successful exploitation can extend a chat-only user's effective capabilities beyond the intended role boundary. Depending on the enabled tools and the file paths allowed by n8n, the user may execute code in the sandbox, read or write permitted files, and invoke instance workflows, Data Tables, or agents. This may expose data or enable unauthorized actions within the capabilities provided by those tools, but the evidence does not establish arbitrary host code execution, access outside permitted directories, or compromise of another system. The available assessment does not identify a direct availability impact or subsequent-system impact.

Business impact

The vulnerability weakens the intended boundary between chat-only users and n8n's tool execution capabilities.

  • Chat-only users may perform actions beyond the limits intended for their role.
  • Files in directories allowed by n8n may be read or written through suitable tools.
  • Instance workflows, Data Tables, and agents may be used through Chat Hub, depending on the tools enabled and the deployment's available access.
  • Code execution in the task runner sandbox may increase the effective capability of the affected account.

The available evidence does not establish unrestricted host access, access outside permitted directories, or a direct availability impact on the service.

Remediation

  1. Upgrade each affected branch to its corresponding fixed release: the 1.x branch to 1.123.85, the branch starting at 2.0.0 and below 2.43.5 to 2.43.5, or the 2.44.0 branch to 2.44.1.
  2. If an upgrade cannot be completed immediately, restrict instance access to fully trusted users.
  3. Temporarily avoid assigning the global:chatUser role to users who are not fully trusted.
  4. Disable Chat Hub if the instance does not require it.
  5. Use the NODES_EXCLUDE environment variable to remove high-risk node types if they are not needed.
  6. Enable N8N_SSRF_PROTECTION_ENABLED=true to reduce the potential impact of outbound request abuse.

Steps 2 through 6 are temporary mitigations and do not replace upgrading.

Detection

  1. Inventory n8n instances and compare deployed versions with the affected and fixed branches listed in the affected summary.
  2. Determine whether Chat Hub is enabled and reachable by chat users.
  3. Review assignments of the global:chatUser role, especially for accounts that are not fully trusted.
  4. Review tools registered or run through Chat Hub by these users, focusing on tools that use the task runner sandbox, file access, workflows, Data Tables, or agents.
  5. Review available audit and application records for unusual tool registration or execution. Treat this as precautionary monitoring, not as a confirmed indicator of compromise.
  6. The advisory does not name a specific log event, IOC, or endpoint. The absence of matching records does not establish that an instance is safe.
Sources (16)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.