Sm1Ee

**Name of the Vulnerable Software and Affected Versions** n8n versions prior to 2.25.7 n8n versions prior to 2.26.2 **Description** An authenticated user with permissions to create or modify workflows can pollute the sandbox used by the Merge node's SQL Query mode. Since the sandbox context is cached and reused across all workflow executions on an instance, prototype mutations introduced by one user persist in subsequent Merge SQL executions for other users or projects. This allows a low-privileged attacker to intercept workflow data processed by other users on the same instance. This issue specifically affects multi-user instances where multiple users have permission to create and execute workflows using the Merge node in SQL Query mode. **Recommendations** Update to version 2.25.7. Update to version 2.26.2. Limit workflow creation and editing permissions to fully trusted users only. Disable the Merge node by adding `n8n-nodes-base.merge` to the `NODES EXCLUDE` environment variable.

**Name of the Vulnerable Software and Affected Versions** n8n versions prior to 2.24.0 **Description** An endpoint in the Meta and Microsoft Teams trigger nodes reflects a query parameter into the HTTP response without sanitization or Content-Security-Policy headers. This allows for reflected Cross-Site Scripting (XSS), where an attacker can execute malicious scripts in the n8n origin if a logged-in user visits a specially crafted URL. **Recommendations** Update to version 2.24.0 or later. Limit workflow creation and activation permissions to fully trusted users only. Disable the affected nodes by adding `n8n-nodes-base.facebookTrigger`, `n8n-nodes-base.whatsAppTrigger`, `n8n-nodes-base.facebookLeadAdsTrigger`, and `n8n-nodes-base.microsoftTeamsTrigger` to the `NODES EXCLUDE` environment variable.

**Name of the Vulnerable Software and Affected Versions** n8n versions prior to 2.25.7 n8n versions prior to 2.26.2 **Description** A prototype pollution issue allows a crafted public webhook payload to inject attacker-controlled fields into workflow data during internal object copying. Prototype pollution occurs when an attacker can manipulate the prototype of an object, potentially altering the behavior of the application. These injected fields can be consumed as normal values by downstream built-in nodes. In workflows combining a public webhook with action nodes, this can lead to a confused deputy scenario, where the workflow targets unintended records or issues outbound requests using the workflow owner's configured credentials. **Recommendations** Update to version 2.25.7 or later. Update to version 2.26.2 or later. Avoid exposing public unauthenticated webhook workflows that pass incoming data through transform nodes into action nodes with sensitive credentials or database operations. Limit workflow creation and editing permissions to fully trusted users only.

**Name of the Vulnerable Software and Affected Versions** n8n versions prior to 2.25.7 n8n versions prior to 2.26.2 **Description** An authenticated user with permissions to create or modify workflows can provide crafted parameters to the TimescaleDB and legacy Postgres v1 nodes. This allows arbitrary SQL injection and execution against the connected database, operating under the privileges of the configured database account. **Recommendations** Update to version 2.25.7 or later. Update to version 2.26.2 or later. Limit workflow creation and editing permissions to fully trusted users only. Disable the Postgres and TimescaleDB nodes by adding `n8n-nodes-base.postgres` and `n8n-nodes-base.timescaleDb` to the `NODES EXCLUDE` environment variable.

**Name of the Vulnerable Software and Affected Versions** n8n versions prior to 2.24.0 **Description** An authenticated user with workflow edit access can provide a malicious filter value within the MongoDB node's Find And Replace operation. Because the value is not validated before being used as a query filter in MongoDB, it allows unintended documents to be matched and overwritten with content controlled by the attacker. **Recommendations** Update to version 2.24.0 or later. Limit workflow creation and editing permissions to fully trusted users only. Disable the MongoDB node by adding `n8n-nodes-base.mongoDb` to the `NODES EXCLUDE` environment variable.

**Name of the Vulnerable Software and Affected Versions** n8n versions prior to 1.123.55 n8n versions prior to 2.25.7 n8n versions prior to 2.26.2 **Description** An authenticated user with workflow edit access can inject arbitrary JavaScript into the page generated by the Chat Trigger by providing a malicious `webhookId`. This allows the injected code to execute within the n8n origin using the session privileges of any logged-in user who visits the chat URL. **Recommendations** Update to version 1.123.55. Update to version 2.25.7. Update to version 2.26.2. Limit workflow creation and editing permissions to fully trusted users only. Disable the Chat Trigger node by adding `@n8n/n8n-nodes-langchain.chatTrigger` to the `NODES EXCLUDE` environment variable.

**Name of the Vulnerable Software and Affected Versions** n8n versions prior to 1.123.43 n8n versions prior to 2.20.7 n8n versions prior to 2.22.1 **Description** An authenticated user with permissions to create or modify workflows can achieve global prototype pollution through an unvalidated pagination parameter in the HTTP Request node. Prototype pollution occurs when an application allows an attacker to modify the prototype of a base object, potentially altering the behavior of all objects created from that prototype. This issue can be combined with other techniques to result in Remote Code Execution (RCE) on the instance. **Recommendations** Update to version 1.123.43 or later. Update to version 2.20.7 or later. Update to version 2.22.1 or later. Limit workflow creation and editing permissions to fully trusted users only. Disable the HTTP Request node by adding `n8n-nodes-base.httpRequest` to the `NODES EXCLUDE` environment variable.

**Name of the Vulnerable Software and Affected Versions** n8n versions prior to 1.123.43 n8n versions prior to 2.20.7 n8n versions prior to 2.22.1 **Description** An attacker with write access to a git repository connected to an n8n Source Control configuration can commit a malicious Data Table JSON file containing a crafted column name. When an administrator performs a Source Control Pull, the application imports the file, which can lead to SQL injection on the internal PostgreSQL instance. SQL injection is a technique where malicious SQL statements are inserted into entry fields for execution. This issue requires the instance to use PostgreSQL as its database backend, the Source Control feature to be enabled and connected to a repository the attacker can write to, and an administrator to trigger the Source Control Pull. **Recommendations** Update to version 1.123.43 or later. Update to version 2.20.7 or later. Update to version 2.22.1 or later. Disable the Source Control feature if it is not actively required. Restrict write access to the connected git repository to fully trusted users only. Avoid pulling from repositories that may have been modified by untrusted parties.

**Name of the Vulnerable Software and Affected Versions** n8n versions prior to 1.123.32 n8n versions prior to 2.17.4 n8n versions prior to 2.18.1 **Description** A flaw in the SeaTable node's 'row:search' and 'row:get' operations allows user-controlled input to be concatenated directly into SQL query strings without escaping or parameterization. In workflows where external user input is passed via expressions into the search or row retrieval parameters, an attacker could manipulate the constructed query to retrieve unintended rows from the connected SeaTable base, bypassing row-level filtering logic. **Recommendations** Update to version 1.123.32. Update to version 2.17.4. Update to version 2.18.1.

Name of the Vulnerable Software and Affected Versions Rack::Session versions 2.0.0 through 2.1.1 Description Rack::Session is a session management implementation for Rack. Versions 2.0.0 through 2.1.1 incorrectly handle decryption failures when configured with secrets. If cookie decryption fails, the implementation falls back to a default decoder instead of rejecting the cookie. This allows an unauthenticated attacker to supply a crafted session cookie that is accepted as valid session data without knowledge of any configured secret. An attacker can manipulate session contents and potentially gain unauthorized access. Recommendations Update Rack::Session to version 2.1.2 or later.

**Name of the Vulnerable Software and Affected Versions** Traefik versions prior to 2.11.38 and 3.6.9 **Description** Traefik, an HTTP reverse proxy and load balancer, has a potential issue in how it manages responses from the ForwardAuth middleware. When configured to use ForwardAuth, the response body from the authentication server is read entirely into memory without any size limit. The absence of a `maxResponseBodySize` configuration allows an attacker to send an unexpectedly large or unbounded response body, potentially causing Traefik to allocate unlimited memory and crash due to an out-of-memory (OOM) condition. This results in a denial of service for all routes served by the affected Traefik instance. A proof-of-concept demonstrates that a malicious authentication server can cause Traefik to allocate gigabytes of memory, leading to a complete service outage. **Recommendations** Traefik versions prior to 2.11.38 must be updated. Traefik versions prior to 3.6.9 must be updated.

**Name of the Vulnerable Software and Affected Versions** n8n versions prior to 1.123.22 n8n versions 2.0.0 through 2.9.2 n8n version 2.10.0 **Description** An authentication bypass exists in the Chat Trigger node when configured with n8n User Auth. This issue allows the authentication check on the Chat Trigger webhook endpoint to be circumvented, enabling access without valid credentials. **Recommendations** Update to version 1.123.22 or later. Update to version 2.9.3 or later. Update to version 2.10.1 or later.