Quick answers
- Is CVE-2026-110846 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-110846 being exploited in the wild.
- How severe is CVE-2026-110846?
- Informational severity, published 14 October 2026.
- Which products and versions are affected?
- N8n before 2.41.4 and 2.42.0 before 2.42.1.
- Is there a fix for CVE-2026-110846?
- Yes: fixed in n8n 2.41.4, 2.42.1. Until then: Restrict n8n instance access to fully trusted users only. Avoid using Send-and-Wait nodes that gate high-consequence actions in workflows where unauthenticated trigger nodes expose resumeTokens to external callers. Disable or restrict public webhook and chat trigger endpoints that precede Send-and-Wait approval nodes.</anigation> <parameter name="timeline">[{"kind": "disclosed", "at": "2026-09-30"}, {"kind": "advisory", "at": "2026-10-14"}] Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-110846 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-110846?
- Check whether you run N8n at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: n8n 2.41.4, 2.42.1
Restrict n8n instance access to fully trusted users only. Avoid using Send-and-Wait nodes that gate high-consequence actions in workflows where unauthenticated trigger nodes expose resumeTokens to external callers. Disable or restrict public webhook and chat trigger endpoints that precede Send-and-Wait approval nodes.</anigation> <parameter name="timeline">[{"kind": "disclosed", "at": "2026-09-30"}, {"kind": "advisory", "at": "2026-10-14"}]
Technical details
The waiting-webhook endpoint validates Send-and-Wait node references and applies signature checks, but performs validation before normalizing alternate node reference forms, allowing requests using that form to bypass HMAC signature verification. An attacker holding an execution's resume token can exploit this to approve waiting executions belonging to other users and trigger downstream workflow actions with the workflow owner's privileges.
Affected products
- n8n n8n before 2.41.4 and 2.42.0 before 2.42.1