Quick answers
- Is CVE-2026-119408 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119408 being exploited in the wild.
- How severe is CVE-2026-119408?
- High severity, with a CVSS score of 8.8, published 30 October 2026.
- Which products and versions are affected?
- N8n before 2.42.6, 2.43.x before 2.43.3, 3.x before 3.0.1.
- Is there a fix for CVE-2026-119408?
- Yes: fixed in n8n 2.42.6, 2.43.3, 3.0.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-119408 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-119408?
- 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.42.6, 2.43.3, 3.0.1
Technical details
The vulnerability exists in deprecated node types (Function, Function Item, and LangChain Code) that run outside task runner isolation, allowing authenticated users to execute arbitrary JavaScript in the n8n main process. An attacker with workflow creation or modification permissions can exploit this by naming workflows with hidden node types to bypass restrictions. The issue affects versions before 2.42.6, 2.43.x before 2.43.3, and 3.x before 3.0.1.
Affected products
- n8n n8n before 2.42.6, 2.43.x before 2.43.3, 3.x before 3.0.1
Timeline
- 2026-10-30: disclosed