CVE-2026-118679 — Slack Trigger webhook that — CWE-918
CVE-2026-118679 is a HIGH severity Server-Side Request Forgery (SSRF) vulnerability (CWE-918) (CVSS 7.5/10) affecting Slack Trigger webhook that. Technical vector analysis shows that an attacker can exploit this flaw remotely over the network without authentication (PR:N) with zero user interaction (UI:N), triggering a scope change (S:C) across connected components and allowing unauthorized disclosure of sensitive data (C:H).
📄 Official NVD / MITRE Original Record Text
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.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-118679
CVSS 7.5/10 · HIGH · 28.10.2026
CWE: CWE-918
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🎯 WHAT IS THIS VULNERABILITY?
Authentication Bypass
Summary: 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 ret…
⚡ ATTACK CHAIN
1. JWT: change alg to none, remove signature.
2. SQL bypass: ' OR '1'='1'-- in login form.
3. Direct API endpoint access without auth headers.
4. Password reset token prediction or race condition.
5. Credential stuffing with default creds.
🔧 Tools: jwt_tool, Burp Suite, Hydra, sqlmap --forms
🗺️ MITRE ATT&CK: T1078 (Valid Accounts), T1110 (Brute Force)
🌍 REAL WORLD IMPACT
All confidential data readable/stealable; pivot to other systems possible.
🛡️ REMEDIATION
→ Apply the vendor-released patch immediately.
→ Add MFA, strengthen sessions, implement rate limiting.
→ Pre-patch: put service behind VPN or apply IP allowlist.
→ Add WAF rule, create IDS alert for anomalous traffic.
⚠️ URGENCY
⚠️ This week (7 days) — High risk, anonymous remote.
────────────────────────────────────────
[Kural Tabanlı Otomatik Güvenlik Analizi]