Quick answers
- Is CVE-2026-118677 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118677 being exploited in the wild.
- How severe is CVE-2026-118677?
- Medium severity, with a CVSS score of 5.9, published 28 October 2026.
- Which products and versions are affected?
- N8n before 2.41.4, 2.42.x before 2.42.1.
- Is there a fix for CVE-2026-118677?
- Yes: fixed in 2.42.1, 2.41.4. Until then: Do not open unsolicited links using the n8n-computer-use:// scheme. Quit the Local Gateway app when not actively in use. Restrict the allowedOrigins setting to the specific instance URL rather than using the default wildcard. Disable the Computer Use / Local Gateway feature if it is not required. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118677 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-118677?
- 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.42.1, 2.41.4
Do not open unsolicited links using the n8n-computer-use:// scheme. Quit the Local Gateway app when not actively in use. Restrict the allowedOrigins setting to the specific instance URL rather than using the default wildcard. Disable the Computer Use / Local Gateway feature if it is not required.
Technical details
The Local Gateway's deep-link handler (n8n-computer-use:// scheme) fails to require user confirmation before re-pairing to a different n8n instance. The vulnerability is triggered when an attacker-controlled URI is opened by a user, causing the app to silently reconnect and preserve all previously granted permissions. Attack requires the Local Gateway app to be installed and running, user interaction to open a crafted link, and a network connection; a fix is available in versions 2.42.1 and 2.41.4.
Affected products
- n8n n8n before 2.41.4, 2.42.x before 2.42.1
Timeline
- 2026-10-14: disclosed
- 2026-10-28: advisory