# CVE-2026-119408: n8n remote code execution in deprecated Function nodes

Source: https://junglewise.ai/threats/cve-2026-119408-n8n-before-2-42-6-2-43-x-before-2-43-3-and-3-x-before-3-0-1  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-30. Updated: 2026-10-30  
License: CC BY 4.0 with a link back

CVE-2026-119408 · Severity: high · CVSS 8.8 · Published 2026-10-30

n8n is a workflow automation platform that allows users to build and execute automated processes. A vulnerability in deprecated Function, Function Item, and LangChain Code nodes allows authenticated users to execute arbitrary JavaScript code in the n8n main process by creating or modifying workflows, potentially compromising the entire platform and any connected systems.

Technologies: [N8n](https://junglewise.ai/threats/technologies/n8n). Vendors: [N8n](https://junglewise.ai/threats/vendors/n8n).

## 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

## References

- [https://abraxaslabs.tech/research/n8n-function-vm2](https://abraxaslabs.tech/research/n8n-function-vm2)
- [https://github.com/n8n-io/n8n](https://github.com/n8n-io/n8n)

## Related threats

- [n8n path traversal in Databricks node](https://junglewise.ai/threats/cve-2026-119557-n8n-from-2-14-0-through-2-46-3-contains-a-path-traversal)
- [n8n Slack Trigger SSRF and token exfiltration](https://junglewise.ai/threats/cve-2026-118679-n8n-before-1-123-83-2-41-4-and-2-42-1-contains-a-server-side)
- [n8n prototype pollution in workflow history compaction](https://junglewise.ai/threats/cve-2026-118678-n8n-before-2-41-4-and-2-42-x-before-2-42-1-contains-a-prototype)
- [n8n Local Gateway deep-link missing confirmation re-pairing](https://junglewise.ai/threats/cve-2026-118677-n8n-before-2-41-4-and-2-42-x-before-2-42-1-contains-a-missing)
- [n8n authorization bypass in credential access control](https://junglewise.ai/threats/cve-2026-118676-n8n-before-1-123-85-2-43-5-and-2-44-1-contains-an-authorization)