Is CVE-2026-118679 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-118679 being exploited in the wild.

How severe is CVE-2026-118679?

High severity, with a CVSS score of 7.5, published 28 October 2026.

Which products and versions are affected?

N8n before 1.123.83, 2.41.4, and 2.42.1.

How is CVE-2026-118679 attacked?

It is attacked over the network.

Am I affected by CVE-2026-118679?

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.

CVE-2026-118679: n8n Slack Trigger SSRF and token exfiltration

CVE-2026-118679 · Severity: high · CVSS 7.5 · Published 2026-10-28

n8n is a workflow automation platform that integrates with services like Slack. The Slack Trigger webhook component accepts unauthenticated requests when no signing secret is configured, allowing attackers to trigger file downloads and intercept the workspace access token. An attacker who knows the webhook URL can exfiltrate Slack credentials and read arbitrary responses from the integration, compromising Slack workspace security.

Technologies: N8n. Vendors: N8n.

Quick answers

Is CVE-2026-118679 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-118679 being exploited in the wild.
How severe is CVE-2026-118679?: High severity, with a CVSS score of 7.5, published 28 October 2026.
Which products and versions are affected?: N8n before 1.123.83, 2.41.4, and 2.42.1.
Is there a fix for CVE-2026-118679?: Yes: fixed in 1.123.83, 2.41.4, 2.42.1. Until then: Set a Signature Secret on all Slack API credentials used with the Slack Trigger node, disable the "Download Files" option on any active Slack Trigger nodes, restrict network-level access to the webhook endpoint to Slack's published IP ranges, and enable SSRF protection by setting N8N_SSRF_PROTECTION_ENABLED=true. Rotate any Slack OAuth tokens associated with Slack Trigger workflows that may have been exposed. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-118679 attacked?: It is attacked over the network.
Am I affected by CVE-2026-118679?: 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: 1.123.83, 2.41.4, 2.42.1

Set a Signature Secret on all Slack API credentials used with the Slack Trigger node, disable the "Download Files" option on any active Slack Trigger nodes, restrict network-level access to the webhook endpoint to Slack's published IP ranges, and enable SSRF protection by setting N8N_SSRF_PROTECTION_ENABLED=true. Rotate any Slack OAuth tokens associated with Slack Trigger workflows that may have been exposed.

Technical details

The Slack Trigger webhook fails to validate request signatures when the signing secret credential field is not set, permitting unauthenticated SSRF attacks. An attacker can craft a request specifying an arbitrary file to download, causing the node to send the workspace access token to an attacker-controlled host and return the HTTP response. The vulnerability requires knowledge of the webhook URL but no authentication or user interaction.

Affected products

n8n n8n before 1.123.83, 2.41.4, and 2.42.1

Timeline

2026-10-14: disclosed
2026-10-28: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.