Ce mail provient de l'extérieur, restons vigilants ===================================================================== CERT-Renater Note d'Information No. 2026/VULN228 _____________________________________________________________________ DATE : 27/02/2026 HARDWARE PLATFORM(S): / OPERATING SYSTEM(S): Systems running n8n (npm) versions prior to 2.10.1, 2.9.3, 1.123.22. ===================================================================== https://github.com/n8n-io/n8n/security/advisories/GHSA-wxx7-mcgf-j869 https://github.com/n8n-io/n8n/security/advisories/GHSA-vpcf-gvg4-6qwr https://github.com/n8n-io/n8n/security/advisories/GHSA-jjpj-p2wh-qf23 https://github.com/n8n-io/n8n/security/advisories/GHSA-2p9h-rqjw-gm92 https://github.com/n8n-io/n8n/security/advisories/GHSA-75g8-rv7v-32f7 https://github.com/n8n-io/n8n/security/advisories/GHSA-f3f2-mcxc-pwjx https://github.com/n8n-io/n8n/security/advisories/GHSA-jh8h-6c9q-7gmw https://github.com/n8n-io/n8n/security/advisories/GHSA-vjf3-2gpj-233v https://github.com/n8n-io/n8n/security/advisories/GHSA-fvfv-ppw4-7h2w https://github.com/n8n-io/n8n/security/advisories/GHSA-38c7-23hj-2wgq https://github.com/n8n-io/n8n/security/advisories/GHSA-mqpr-49jj-32rc _____________________________________________________________________ Remote Code Execution via Merge Node Critical Jubke published GHSA-wxx7-mcgf-j869 Feb 25, 2026 Package n8n (npm) Affected versions < 1.123.22, >= 2.0.0 < 2.9.3, >= 2.10.0 < 2.10.1 Patched versions 2.10.1, 2.9.3, 1.123.22 Description Impact An authenticated user with permission to create or modify workflows could leverage the Merge node's SQL query mode to execute arbitrary code and write arbitrary files on the n8n server. Patches The issues have been fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22. Users should upgrade to one of these versions or later to remediate all known vulnerabilities. Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: 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. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures. n8n has adopted CVSS 4.0 as primary score for all security advisories. CVSS 3.1 vector strings are provided for backwards compatibility. CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H Severity Critical 9.4/ 10 CVSS v4 base metrics Exploitability Metrics Attack Vector Network Attack Complexity Low Attack Requirements None Privileges Required Low User interaction None Vulnerable System Impact Metrics Confidentiality High Integrity High Availability High Subsequent System Impact Metrics Confidentiality High Integrity High Availability High CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H CVE ID CVE-2026-27497 Weaknesses No CWEs Credits @allsmog allsmog Reporter @nil340 nil340 Reporter _____________________________________________________________________ Expression Sandbox Escape Leading to RCE Critical Jubke published GHSA-vpcf-gvg4-6qwr Feb 25, 2026 Package n8n (npm) Affected versions < 1.123.22, >= 2.0.0 < 2.9.3, >= 2.10.0 < 2.10.1 Patched versions 2.10.1, 2.9.3, 1.123.22 Description Impact Additional exploits in the expression evaluation of n8n have been identified and patched following CVE-2025-68613. An authenticated user with permission to create or modify workflows could abuse crafted expressions in workflow parameters to trigger unintended system command execution on the host running n8n. Patches The issues have been fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22. Users should upgrade to one of these versions or later to remediate all known vulnerabilities. Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only. Deploy n8n in a hardened environment with restricted operating system privileges and network access to reduce the impact of potential exploitation. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures. References Best practices for securing n8n Initial vulnerability advisory: CVE-2025-68613 n8n has adopted CVSS 4.0 as primary score for all security advisories. CVSS 3.1 vector strings are provided for backwards compatibility. CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H Severity Critical 9.4/ 10 CVSS v4 base metrics Exploitability Metrics Attack Vector Network Attack Complexity Low Attack Requirements None Privileges Required Low User interaction None Vulnerable System Impact Metrics Confidentiality High Integrity High Availability High Subsequent System Impact Metrics Confidentiality High Integrity High Availability High CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H CVE ID CVE-2026-27577 Weaknesses No CWEs Credits @eilonc-pillar eilonc-pillar Reporter @nil340 nil340 Reporter @ediklab ediklab Reporter @hackerman70000 hackerman70000 Reporter @zolbooo zolbooo Reporter _____________________________________________________________________ Sandbox Escape in JavaScript Task Runner Critical Jubke published GHSA-jjpj-p2wh-qf23 Feb 25, 2026 Package n8n (npm) Affected versions < 1.123.22, >= 2.0.0 < 2.9.3, >= 2.10.0 < 2.10.1 Patched versions 2.10.1, 2.9.3, 1.123.22 Description Impact An authenticated user with permission to create or modify workflows could exploit a vulnerability in the JavaScript Task Runner sandbox to execute arbitrary code outside the sandbox boundary. On instances using internal Task Runners (default runner mode), this could result in full compromise of the n8n host. On instances using external Task Runners, the attacker might gain access to or impact other task executed on the Task Runner. Task Runners must be enabled using N8N_RUNNERS_ENABLED=true. Patches The issue has been fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22. Users should upgrade to one of these versions or later to remediate the vulnerability. Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only. Use external runner mode (N8N_RUNNERS_MODE=external) to limit the blast radius. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures. References n8n Documentation — Task Runners n8n has adopted CVSS 4.0 as primary score for all security advisories. CVSS 3.1 vector strings are provided for backwards compatibility. CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H Severity Critical 9.4/ 10 CVSS v4 base metrics Exploitability Metrics Attack Vector Network Attack Complexity Low Attack Requirements None Privileges Required Low User interaction None Vulnerable System Impact Metrics Confidentiality High Integrity High Availability High Subsequent System Impact Metrics Confidentiality High Integrity High Availability High CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H CVE ID CVE-2026-27495 Weaknesses Weakness CWE-94 Credits @c0rydoras c0rydoras Finder _____________________________________________________________________ Stored XSS via Various Nodes High Jubke published GHSA-2p9h-rqjw-gm92 Feb 25, 2026 Package n8n (npm) Affected versions < 1.123.22, >= 2.0.0 < 2.9.3, >= 2.10.0 < 2.10.1 Patched versions 2.10.1, 2.9.3, 1.123.22 Description Impact An authenticated user with permission to create or modify workflows could inject arbitrary scripts into pages rendered by the n8n application using different techniques on various nodes (Form Trigger node, Chat Trigger node, Send & Wait node, Webhook Node, and Chat Node). Scripts injected by a malicious workflow execute in the browser of any user who visits the affected page, enabling session hijacking and account takeover. Patches The issues have been fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22. Users should upgrade to one of these versions or later to remediate the vulnerability. Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only. Disable the Webhook node by adding n8n-nodes-base.webhook to the NODES_EXCLUDE environment variable. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures. Credit Reporters: @ori-ron @Aikido-Security @nil340 Pawel Bednarz from the NATO Cyber Security Centre (NCSC) n8n has adopted CVSS 4.0 as primary score for all security advisories. CVSS 3.1 vector strings are provided for backwards compatibility. CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N Severity High 8.5/ 10 CVSS v4 base metrics Exploitability Metrics Attack Vector Network Attack Complexity Low Attack Requirements None Privileges Required Low User interaction Passive Vulnerable System Impact Metrics Confidentiality High Integrity High Availability None Subsequent System Impact Metrics Confidentiality Low Integrity Low Availability None CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N CVE ID CVE-2026-27578 Weaknesses No CWEs Credits @ori-ron ori-ron Reporter @Aikido-Security Aikido-Security Reporter @nil340 nil340 Reporter _____________________________________________________________________ Unauthenticated Expression Evaluation via Form Node High Jubke published GHSA-75g8-rv7v-32f7 Feb 25, 2026 Package n8n (npm) Affected versions < 1.123.22, >= 2.0.0 < 2.9.3, >= 2.10.0 < 2.10.1 Patched versions 2.10.1, 2.9.3, 1.123.22 Description Impact A second-order expression injection vulnerability existed in n8n's Form nodes that could allow an unauthenticated attacker to inject and evaluate arbitrary n8n expressions by submitting crafted form data. When chained with an expression sandbox escape, this could escalate to remote code execution on the n8n host. The vulnerability requires a specific workflow configuration to be exploitable: A form node with a field interpolating a value provided by an unauthenticated user, e.g. a form submitted value. The field value must begin with an = character, which caused n8n to treat it as an expression and triggered a double-evaluation of the field content. For example, a workflow uses a multi-step Form where a downstream Form node renders user-provided input back in an HTML field and precedes it with an = sign: =

Thank you, {{ $input.first().json[\"Name\"] }}!

There is no practical reason for a workflow designer to prefix a field with = intentionally — the character is not rendered in the output, so the result would not match the designer's expectations. If added accidentally, it would be noticeable and very unlikely to persist. An unauthenticated attacker would need to either know about this specific circumstance on a target instance or discover a matching form by chance. Even when the preconditions are met, the expression injection alone is limited to data accessible within the n8n expression context. Escalation to remote code execution requires chaining with a separate sandbox escape vulnerability. Due to these real-world constraints — the unlikely workflow configuration, the need for an additional sandbox escape, and the difficulty of discovery — we have assessed the severity as High rather than Critical, diverging from the base CVSS score to better reflect actual exploitability. Patches The issue has been fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22. Users should upgrade to one of these versions or later to remediate the vulnerability. Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Review usage of form nodes manually for above mentioned preconditions. Disable the Form node by adding n8n-nodes-base.form to the NODES_EXCLUDE environment variable. Disable the Form Trigger node by adding n8n-nodes-base.formTrigger to the NODES_EXCLUDE environment variable. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures. n8n has adopted CVSS 4.0 as primary score for all security advisories. CVSS 3.1 vector strings are provided for backwards compatibility. CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H Severity High CVE ID CVE-2026-27493 Weaknesses Weakness CWE-94 Weakness CWE-95 Credits @eilonc-pillar eilonc-pillar Reporter _____________________________________________________________________ SQL Injection in MySQL, PostgreSQL, and Microsoft SQL nodes Moderate Jubke published GHSA-f3f2-mcxc-pwjx Feb 25, 2026 Package n8n (npm) Affected versions < 2.4.0 Patched versions 2.4.0 Description Impact An authenticated user with permission to create or modify workflows and access to a database credential could unknowingly create a workflow that was vulnerable to SQL injection, even while expecting inputs to be handled safely through escaped parameters. By supplying specially crafted table or column names, an attacker could inject arbitrary SQL because the MySQL, PostgreSQL, and Microsoft SQL nodes did not escape identifier values when constructing queries, enabling injection through node configuration parameters. Patches The issue has been fixed in n8n version 2.4.0. Users should upgrade to this version or later to remediate the vulnerability. Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only. Disable the MySQL, PostgreSQL, and Microsoft SQL nodes by adding n8n-nodes-base.mySql, n8n-nodes-base.postgres, and n8n-nodes-base.microsoftSql to the NODES_EXCLUDE environment variable. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures. Credit Reporter: Pawel Bednarz from the NATO Cyber Security Centre (NCSC) n8n has adopted CVSS 4.0 as primary score for all security advisories. CVSS 3.1 vector strings are provided for backwards compatibility. CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N Severity Moderate 5.3/ 10 CVSS v4 base metrics Exploitability Metrics Attack Vector Network Attack Complexity Low Attack Requirements Present Privileges Required Low User interaction None Vulnerable System Impact Metrics Confidentiality None Integrity None Availability None Subsequent System Impact Metrics Confidentiality High Integrity High Availability None CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N CVE ID No known CVE Weaknesses No CWEs _____________________________________________________________________ Authentication Bypass in Chat Trigger Node Moderate Jubke published GHSA-jh8h-6c9q-7gmw Feb 25, 2026 Package n8n (npm) Affected versions < 1.123.22, >= 2.0.0 < 2.9.3, >= 2.10.0 < 2.10.1 Patched versions 2.10.1, 2.9.3, 1.123.22 Description Impact When the Chat Trigger node is configured with n8n User Auth authentication, the authentication check could be circumvented. This issue requires the Chat Trigger node to be configured with n8n User Auth authentication (non-default). Patches The issue has been fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22. Users should upgrade to one of these versions or later to remediate the vulnerability. Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only. Use a different authentication method for the Chat Trigger node, or restrict network access to the webhook endpoint to trusted origins. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures. n8n has adopted CVSS 4.0 as primary score for all security advisories. CVSS 3.1 vector strings are provided for backwards compatibility. CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N Severity Moderate 6.3/ 10 CVSS v4 base metrics Exploitability Metrics Attack Vector Network Attack Complexity Low Attack Requirements Present Privileges Required None User interaction None Vulnerable System Impact Metrics Confidentiality Low Integrity Low Availability None Subsequent System Impact Metrics Confidentiality None Integrity None Availability None CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N CVE ID No known CVE Weaknesses Weakness CWE-287 Credits @sm1ee sm1ee Reporter _____________________________________________________________________ SSO Enforcement Bypass Moderate Jubke published GHSA-vjf3-2gpj-233v Feb 25, 2026 Package n8n (npm) Affected versions < 2.8.0 Patched versions 2.8.0 Description Impact An authenticated user signed in through Single Sign-On (SSO) could disable SSO enforcement for their own account through the n8n API. This allowed the user to create a local password and authenticate directly with email and password, completely bypassing the organization's SSO policy, centralized identity management, and any identity-provider-enforced multi-factor authentication. Patches The issue has been fixed in n8n version 2.8.0. Users should upgrade to this version or later to remediate the vulnerability. Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Monitor audit logs for users who create local credentials after authenticating via SSO. Restrict the n8n instance to fully trusted users only. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures. n8n has adopted CVSS 4.0 as primary score for all security advisories. CVSS 3.1 vector strings are provided for backwards compatibility. CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:N Severity Moderate 6.0/ 10 CVSS v4 base metrics Exploitability Metrics Attack Vector Network Attack Complexity Low Attack Requirements Present Privileges Required Low User interaction None Vulnerable System Impact Metrics Confidentiality None Integrity High Availability None Subsequent System Impact Metrics Confidentiality None Integrity None Availability None CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N CVE ID No known CVE Weaknesses Weakness CWE-269 Weakness CWE-284 Weakness CWE-287 Credits @stanislavfortaisle stanislavfortaisle Reporter _____________________________________________________________________ n8n Guardrail Node Bypass Moderate Jubke published GHSA-fvfv-ppw4-7h2w Feb 25, 2026 Package n8n (npm) Affected versions < 2.10.0 Patched versions 2.10.0 Description Impact An end user interacting with a workflow that uses the Guardrail node could craft an input that bypasses the default guardrail instructions. Patches The issue has been fixed in n8n version 2.10.0. Users should upgrade to this version or later to remediate the vulnerability. Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit access to trusted users. Review asses the practical impact of guardrail bypasses in your usecase and adjust your workflow accordingly. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures. n8n has adopted CVSS 4.0 as primary score for all security advisories. CVSS 3.1 vector strings are provided for backwards compatibility. CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N Severity Moderate 6.0/ 10 CVSS v4 base metrics Exploitability Metrics Attack Vector Network Attack Complexity Low Attack Requirements Present Privileges Required None User interaction None Vulnerable System Impact Metrics Confidentiality None Integrity Low Availability None Subsequent System Impact Metrics Confidentiality None Integrity None Availability None CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N CVE ID No known CVE Weaknesses No CWEs Credits @akirilov akirilov Reporter _____________________________________________________________________ Webhook Forgery on Zendesk Trigger Moderate Jubke published GHSA-38c7-23hj-2wgq Feb 25, 2026 Package n8n (npm) Affected versions < 1.123.18, >= 2.0.0 < 2.6.2 Patched versions 2.6.2, 1.123.18 Description Impact An attacker who knows the webhook URL of a workflow using the ZendeskTrigger node could send unsigned POST requests and trigger the workflow with arbitrary data. The node does not verify the HMAC-SHA256 signature that Zendesk attaches to every outbound webhook, allowing any party to inject crafted payloads into the connected workflow. Patches The issue has been fixed in n8n versions 2.6.2 and 1.123.18. Users should upgrade to one of these versions or later to remediate the vulnerability. Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only. Restrict network access to the n8n webhook endpoint to known Zendesk IP ranges. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures. n8n has adopted CVSS 4.0 as primary score for all security advisories. CVSS 3.1 vector strings are provided for backwards compatibility. CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N Severity Moderate 6.3/ 10 CVSS v4 base metrics Exploitability Metrics Attack Vector Network Attack Complexity Low Attack Requirements Present Privileges Required None User interaction None Vulnerable System Impact Metrics Confidentiality None Integrity Low Availability None Subsequent System Impact Metrics Confidentiality None Integrity Low Availability None CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N CVE ID No known CVE Weaknesses Weakness CWE-290 Credits @nkoorty nkoorty Reporter @jjjutla jjjutla Reporter _____________________________________________________________________ Webhook Forgery on Github Webhook Trigger Moderate Jubke published GHSA-mqpr-49jj-32rc Feb 25, 2026 Package n8n (npm) Affected versions < 1.123.15, >= 2.0.0 < 2.5.0 Patched versions 2.5.0, 1.123.15 Description Impact An attacker who knows the webhook URL of a workflow using the GitHub Webhook Trigger node could send unsigned POST requests and trigger the workflow with arbitrary data. The node did not implement the HMAC-SHA256 signature verification that GitHub provides to authenticate webhook deliveries, allowing any party to spoof GitHub webhook events. Patches The issue has been fixed in n8n versions 2.5.0 and 1.123.15. Users should upgrade to one of these versions or later to remediate the vulnerability. Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only. Restrict network access to the n8n webhook endpoint to known GitHub webhook IP ranges. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures. n8n has adopted CVSS 4.0 as primary score for all security advisories. CVSS 3.1 vector strings are provided for backwards compatibility. CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N Severity Moderate 6.3/ 10 CVSS v4 base metrics Exploitability Metrics Attack Vector Network Attack Complexity Low Attack Requirements Present Privileges Required None User interaction None Vulnerable System Impact Metrics Confidentiality None Integrity Low Availability None Subsequent System Impact Metrics Confidentiality None Integrity Low Availability None CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N CVE ID No known CVE Weaknesses Weakness CWE-290 Credits @simonkoeck simonkoeck Reporter ========================================================= + CERT-RENATER | tel : 01-53-94-20-44 + + 23/25 Rue Daviel | fax : 01-53-94-20-41 + + 75013 Paris | email:cert@support.renater.fr + =========================================================