Quick answers
- Is CVE-2026-118675 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118675 being exploited in the wild.
- How severe is CVE-2026-118675?
- High severity, with a CVSS score of 7.1, published 28 October 2026.
- Which products and versions are affected?
- N8n before 1.123.85, 2.43.5, and 2.44.1.
- Is there a fix for CVE-2026-118675?
- Yes: fixed in n8n 1.123.85, 2.43.5, 2.44.1. Until then: Restrict n8n instance access to fully trusted users only. Audit shared workflows for Execute Sub-workflow nodes using source: url or source: localFile parameters and remove or restrict them. Remove editor access from untrusted users until patched. Apply network-level controls to prevent the n8n process from reaching attacker-controlled infrastructure.</anigation> <parameter name="timeline">[{"kind":"disclosed","at":"2026-10-14"},{"kind":"advisory","at":"2026-10-28"},{"kind":"patched","at":"2026-10-28"}] Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118675 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-118675?
- 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 1.123.85, 2.43.5, 2.44.1
Restrict n8n instance access to fully trusted users only. Audit shared workflows for Execute Sub-workflow nodes using source: url or source: localFile parameters and remove or restrict them. Remove editor access from untrusted users until patched. Apply network-level controls to prevent the n8n process from reaching attacker-controlled infrastructure.</anigation> <parameter name="timeline">[{"kind":"disclosed","at":"2026-10-14"},{"kind":"advisory","at":"2026-10-28"},{"kind":"patched","at":"2026-10-28"}]
Technical details
The vulnerability exploits insufficient validation of sub-workflow content in the Execute Sub-workflow node, which can load workflows from URLs or local files at runtime. The shared-workflow credential guard only validates the saved workflow content but does not inspect dynamically loaded sub-workflows, allowing an authenticated editor to configure nodes with source: url or source: localFile parameters that resolve and decrypt project credentials. This is an authorization bypass (CWE-863) that requires the attacker to have editor-level privileges on a shared workflow and network access to serve malicious content.
Affected products
- n8n n8n before 1.123.85, 2.43.5, and 2.44.1