Tr4Ce-Ju

**Name of the Vulnerable Software and Affected Versions** n8n versions prior to 1.123.69 n8n versions prior to 2.33.4 n8n versions prior to 2.34.1 **Description** A NoSQL injection issue exists in the MongoDB node's Find, Delete, and Aggregate operations. The software parses the `Query` parameter as JSON after expression resolution without sanitizing MongoDB operators. An attacker capable of influencing the resolved query through externally-controlled data can inject operators like `$ne` or `$where`. This can result in full-collection disclosure, full-collection deletion, or other unauthorized operations on the database server. **Recommendations** Update to version 1.123.69 or later. Update to version 2.33.4 or later. Update to version 2.34.1 or later.

**Name of the Vulnerable Software and Affected Versions** n8n versions prior to 1.123.69 n8n versions prior to 2.33.4 n8n versions prior to 2.34.1 **Description** A PostgREST filter injection issue exists in the Supabase node during Row Get Many, Delete, and Update operations. The system constructs filter queries by concatenating expression-bindable values without proper escaping. This allows an attacker to inject conditions that expand the filter to match all rows, potentially resulting in full-table data disclosure, deletion, or modification. **Recommendations** Update to version 1.123.69 or later. Update to version 2.33.4 or later. Update to version 2.34.1 or later.

**Name of the Vulnerable Software and Affected Versions** n8n versions prior to 1.123.48 n8n versions prior to 2.21.8 n8n versions prior to 2.22.4 **Description** An authenticated user with permissions to create or modify workflows can bypass the `N8N RESTRICT FILE ACCESS TO` file sandbox. By providing a local filesystem path as the source repository in the Git node's Clone operation or as the target repository in the Push operation, the user can clone the contents of any local git repository accessible to the n8n process into an allowed path. This allows the reading of files that are otherwise blocked by direct file read access restrictions. **Recommendations** Update to version 1.123.48. Update to version 2.21.8. Update to version 2.22.4. Limit workflow creation and editing permissions to fully trusted users only. Disable the Git node by adding `n8n-nodes-base.git` to the `NODES EXCLUDE` environment variable.

**Name of the Vulnerable Software and Affected Versions** n8n versions prior to 1.123.25 n8n versions prior to 2.11.2 **Description** An authenticated user with permissions to create or modify workflows can exploit a flaw in the CSS sanitization of the Form Trigger node to store a cross-site scripting (XSS) payload. XSS is a type of security issue where malicious scripts are injected into trusted websites. The injected script executes persistently for every visitor of the published form, which enables phishing and the hijacking of form submissions. While the Content Security Policy prevents the theft of n8n session cookies, it does not stop script execution or the manipulation of form actions. **Recommendations** Update to version 1.123.25 or later. Update to version 2.11.2 or later. Limit workflow creation and editing permissions to fully trusted users only. Disable the Form Trigger node by adding `n8n-nodes-base.formTrigger` to the `NODES EXCLUDE` environment variable.

**Name of the Vulnerable Software and Affected Versions** n8n versions prior to 1.123.27 n8n versions prior to 2.13.3 n8n versions prior to 2.14.1 **Description** An authenticated user with the `global:member` role could exploit authorization flaws in n8n's credential pipeline to obtain plaintext secrets from generic HTTP credentials (`httpBasicAuth`, `httpHeaderAuth`, `httpQueryAuth`) belonging to other users on the same instance. The attack exploits a name-based credential resolution path that lacks ownership or project scope enforcement, combined with a bypass in the credentials permission checker that skips validation for generic HTTP credential types. This allows a user with the `global:member` role to resolve another user's credential ID and execute a workflow that decrypts and uses that credential without authorization. Native integration credential types (e.g., `slackApi`, `openAiApi`, `postgres`) are not affected. This issue impacts only the Community Edition of n8n. **Recommendations** Upgrade to n8n version 1.123.27 or later. Upgrade to n8n version 2.13.3 or later. Upgrade to n8n version 2.14.1 or later. If upgrading is not immediately possible, restrict instance access to fully trusted users only. If upgrading is not immediately possible, audit credentials stored on the instance and rotate any generic HTTP credentials (`httpBasicAuth`, `httpHeaderAuth`, `httpQueryAuth`) that may have been exposed.

**Name of the Vulnerable Software and Affected Versions** BlackSheep versions prior to 2.4.6 **Description** BlackSheep, an asynchronous web framework for building event-based web applications with Python, has an issue in its HTTP Client implementation. Missing validation of headers allows an attacker to modify HTTP requests, potentially inserting new headers or creating entirely new requests. Exploitation requires passing unsanitized user input directly into headers. The server component is not affected as BlackSheep relies on an underlying ASGI server for handling response headers. The attack vector involves applications using user input in HTTP client requests related to the method, URL, or headers. **Recommendations** Upgrade to version 2.4.6. If handling headers from untrusted sources, reject values for header names and values that contain carriage returns.