CVE-2026-110846: n8n: Send-and-Wait signature bypass enables forged approvals
HIGHCISA: TRACK*n8n before 2.41.4 and 2.42.x before 2.42.1 has a flaw in its waiting-webhook endpoint. It picks Send-and-Wait HMAC validation before it normalises an alternate node reference form, so an attacker who holds an execution's resume token can approve waiting executions meant for someone else. Approved executions run downstream actions under the workflow owner's credentials, which may include command execution, so human-in-the-loop approval gates for AI agent workflows can be bypassed. The record has no CVSS or EPSS score yet. It is not in CISA KEV, and no public exploit or Nuclei template is listed. Exploitation needs a leaked or guessed resume token, which limits likelihood, but the impact on agentic automations is high. Upgrade to 2.41.4 or 2.42.1 or later, and review which workflows use Send-and-Wait approvals to gate privileged actions.
What is the risk?
Severity is not yet scored (no CVSS or EPSS), so this is a provisional assessment. Likelihood is moderate to low because the attacker needs a valid resume token, and no public exploit, KEV listing or scanner template is known. Impact can be high: forged approvals run downstream nodes with the workflow owner's stored credentials and may reach command execution. Exposure is greatest for internet-reachable n8n instances whose waiting-webhook URLs are shared by email, chat or logs, where tokens can leak. Re-assess when NVD or vendor scoring is published.
How does the attack unfold?
What systems are affected?
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| n8n | npm | — | No patch |
Do you use n8n? You're affected.
How severe is it?
What should I do?
1 step1) Upgrade n8n to 2.41.4 or 2.42.1 or later. 2) Until patched, restrict network access to the waiting-webhook endpoint (for example by IP allowlist or VPN, or by blocking external access at the reverse proxy). 3) Treat resume URLs and tokens as secrets: avoid posting them to shared channels, tickets or logs, and rotate pending ones where possible. 4) Inventory workflows that use Send-and-Wait and remove or tighten the privileges behind them, using least-privilege credentials and avoiding command-execution nodes. 5) Detect: review webhook-waiting requests and execution logs for approvals from unexpected IPs, with unusual timing, or with no matching approver activity. 6) Rotate credentials used by workflows that may have been approved by an attacker.
What does CISA's SSVC say?
Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2026-110846?
n8n before 2.41.4 and 2.42.x before 2.42.1 has a flaw in its waiting-webhook endpoint. It picks Send-and-Wait HMAC validation before it normalises an alternate node reference form, so an attacker who holds an execution's resume token can approve waiting executions meant for someone else. Approved executions run downstream actions under the workflow owner's credentials, which may include command execution, so human-in-the-loop approval gates for AI agent workflows can be bypassed. The record has no CVSS or EPSS score yet. It is not in CISA KEV, and no public exploit or Nuclei template is listed. Exploitation needs a leaked or guessed resume token, which limits likelihood, but the impact on agentic automations is high. Upgrade to 2.41.4 or 2.42.1 or later, and review which workflows use Send-and-Wait approvals to gate privileged actions.
Is CVE-2026-110846 actively exploited?
No confirmed active exploitation of CVE-2026-110846 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-110846?
1) Upgrade n8n to 2.41.4 or 2.42.1 or later. 2) Until patched, restrict network access to the waiting-webhook endpoint (for example by IP allowlist or VPN, or by blocking external access at the reverse proxy). 3) Treat resume URLs and tokens as secrets: avoid posting them to shared channels, tickets or logs, and rotate pending ones where possible. 4) Inventory workflows that use Send-and-Wait and remove or tighten the privileges behind them, using least-privilege credentials and avoiding command-execution nodes. 5) Detect: review webhook-waiting requests and execution logs for approvals from unexpected IPs, with unusual timing, or with no matching approver activity. 6) Rotate credentials used by workflows that may have been approved by an attacker.
What systems are affected by CVE-2026-110846?
This vulnerability affects the following AI/ML architecture patterns: agent frameworks, workflow automation, human-in-the-loop approval pipelines, LLM tool orchestration.
What is the CVSS score for CVE-2026-110846?
No CVSS score has been assigned yet.
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0049Exploit Public-Facing ApplicationAML.T0050Command and Scripting InterpreterAML.T0053AI Agent Tool InvocationAML.T0091.000Application Access TokenCompliance Controls Affected
What are the technical details?
Original Advisory
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.
Exploitation Scenario
An attacker obtains a resume token for a pending n8n execution, for example from a leaked approval link in a chat channel, a log file or a forwarded email. They send a crafted request to the waiting-webhook endpoint using the alternate node reference form, so the Send-and-Wait HMAC validation is skipped. The execution resumes as approved, and the AI agent workflow carries out its privileged downstream steps, such as running a shell command, calling cloud APIs or reading databases. All of this uses the workflow owner's credentials, and it looks like a normal approval.
Weaknesses (CWE)
CWE-180Incorrect Behavior Order: Validate Before CanonicalizePrimaryCWE-180Incorrect Behavior Order: Validate Before CanonicalizeCWE-180 — Incorrect Behavior Order: Validate Before Canonicalize: The product validates input before it is canonicalized, which prevents the product from detecting data that becomes invalid after the canonicalization step.
- [Implementation] Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.
Source: MITRE CWE corpus.
References
Timeline
Related Vulnerabilities
CVE-2026-3366310.0n8n: member role steals plaintext HTTP credentials
Same package: n8nCVE-2026-3366010.0TensorFlow: type confusion NPD in tensor conversion
Same package: n8nCVE-2026-2185810.0n8n: Input Validation flaw enables exploitation
Same package: n8nCVE-2026-275779.9n8n: Code Injection enables RCE
Same package: n8nCVE-2026-274949.9n8n: security flaw enables exploitation
Same package: n8n