CVE-2026-118679

n8n before 1.123.83, 2.41.4, and 2.42.1 Slack Token Exfiltration via Slack Trigger

Published Oct 28, 2026 CVSS 4.0 · 6.9 Medium EPSS < 1% KEV · Not listed
Description
n8n before 1.123.83, 2.41.4, and 2.42.1 contains a server-side request forgery vulnerability in the Slack Trigger webhook that allows unauthenticated attackers to exfiltrate Slack tokens by bypassing signature verification when no signing secret is set. Attackers who know the webhook URL can name a file to download, causing the node to send the workspace access token to an attacker host and return the response.

Analysis

AI-generated

Technical impact

The vulnerability is a server‑side request forgery in the Slack Trigger webhook of n8n. When no signing secret is configured, an unauthenticated attacker can submit a request with a custom file‑name parameter that causes the node to download the workspace access token and forward it to the attacker’s host. The affected token grants bearer access to Slack resources, allowing an attacker to intercept or misuse the token. This flaw falls under CWE‑918 (Server‑Side Request Forgery).

Affected Systems

n8n-io’s n8n workflow automation platform is affected. Versions prior to 1.123.83, 2.41.4, and 2.42.1 contain the flaw. The flaw is specific to the Slack Trigger webhook component.

Risk and Exploitability

The CVSS score of 6.9 indicates a moderate severity. The exploit requires knowledge of the Slack trigger webhook URL but does not require any authentication. EPSS data is unavailable and the vulnerability is not listed in the CISA KEV catalog, so the current present exploitation risk is moderate but potentially increased if the webhook URL is publicly known. The presence of a user‑configurable signing secret is an important mitigator.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade n8n to 1.123.83 or newer, or to 2.41.4/2.42.1 or later where the bug is fixed.
  • Configure a signing secret for the Slack Trigger webhook to enforce request authenticity and prevent request forgery.
  • If an upgrade is not immediately possible, restrict external network access to the Slack Trigger endpoint or require authentication before the endpoint can be invoked.

Generated by OpenCVE AI on October 28, 2026 at 20:29 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description n8n before 1.123.83, 2.41.4, and 2.42.1 contains a server-side request forgery vulnerability in the Slack Trigger webhook that allows unauthenticated attackers to exfiltrate Slack tokens by bypassing signature verification when no signing secret is set. Attackers who know the webhook URL can name a file to download, causing the node to send the workspace access token to an attacker host and return the response.
Title n8n before 1.123.83, 2.41.4, and 2.42.1 Slack Token Exfiltration via Slack Trigger
First Time appeared N8n
N8n n8n
Weaknesses CWE-918
CPEs cpe:2.3:a:n8n:n8n:*:*:*:*:*:*:*:*
Vendors & Products N8n
N8n n8n
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N'}

cvssV4_0

{'score': 6.9, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:H/SI:L/SA:N'}

Weaknesses
  • CWE-918

    Server-Side Request Forgery (SSRF)

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 4, 2026, 8:18 PM
Reserved
Oct 28, 2026, 5:28 PM
Status
Deferred
Published
Oct 28, 2026, 7:17 PM
Modified
Nov 4, 2026, 9:17 PM