CVE-2026-110846
7.0HighPublished 14 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Impact
- Limited impact
- Weakness
- CWE-180
Impact
Remote attackers with an execution resume token can approve waiting executions intended for other users and execute downstream actions under the workflow owner's credentials. This can lead to unauthorized actions and potential remote command execution.
Root cause
The waiting-webhook endpoint performs Send-and-Wait signature verification prior to normalizing alternate node reference forms, allowing validation bypass.
Affected systems
n8n before 2.41.4, and 2.42.x before 2.42.1
CVSS v4.0 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Fix & remediation
Upgrade n8n to version 2.41.4, 2.42.1, or later. No interim mitigation is provided, so restrict network access to the waiting-webhook endpoint or pause sensitive workflows until patched.
$ npm install -g n8n@latestAI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
n8n before 2.41.4 and 2.42.x before 2.42.1 contains a signature bypass in the waiting-webhook endpoint, which selects Send-and-Wait validation before normalising an alternate node reference form. Attackers holding an execution's resume token can approve waiting executions meant for others, running downstream actions under the workflow owner's credentials, potentially including command execution.