Quick answers
- Is CVE-2026-110841 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-110841 being exploited in the wild.
- How severe is CVE-2026-110841?
- Informational severity, published 14 October 2026.
- Which products and versions are affected?
- N8n before 2.41.4 and 2.42.0.
- Is there a fix for CVE-2026-110841?
- Yes: fixed in 2.41.4, 2.42.0. Until then: Restrict n8n instance access to fully trusted users. Disable the Agents module by removing it from N8N_ENABLED_MODULES. Limit team project membership to the minimum required. Avoid using tools with "Require approval" enabled on agents accessible to multiple project members. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-110841 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-110841?
- 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: 2.41.4, 2.42.0
Restrict n8n instance access to fully trusted users. Disable the Agents module by removing it from N8N_ENABLED_MODULES. Limit team project membership to the minimum required. Avoid using tools with "Require approval" enabled on agents accessible to multiple project members.
Technical details
The agent chat resume endpoint fails to validate that a suspended checkpoint belongs to the authenticated caller, accepting any run identifier from the request body. Combined with project-scoped read endpoints that lack per-user restrictions, an authenticated project member can enumerate and read arbitrary project members' agent conversations, then hijack pending tool approvals. Exploitation requires prior authentication and project membership, and results in confidentiality breach and unauthorized tool execution.
Affected products
- n8n n8n before 2.41.4 and 2.42.0
Timeline
- 2026-09-30: disclosed
- 2026-10-14: advisory