Unauthenticated Slack Token Exfiltration and Full-Response SSRF via the Slack Trigger Webhook
GHSA-3c3p-5959-3ghr · published 2026-10-14
- Severity
- Medium
- CVSS score
- 6.3
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 2.42.1
The Slack Trigger webhook accepted a request whose signature could not be verified, because the signing secret is an optional credential field and the check returned success when it was absent. Such a request could name the file the node then downloaded, and the credential attached the workspace access token to that request whatever the destination. An unauthenticated caller who knows the webhook URL could have the token sent to a host of their choosing and read the response back.
Upgrade n8n to 2.42.1 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
The issue has been fixed in n8n versions 1.123.83, 2.41.4, and 2.42.1. Users should upgrade to one of these versions or later to remediate the vulnerability.
If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Set a Signature Secret on all Slack API credentials used with the Slack Trigger node so that the signature check does not fail open. Disable the "Download Files" option on any active Slack Trigger nodes. Restrict network-level access to the n8n webhook endpoint to Slack's published IP ranges only. 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. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- CriticalFlowise NodeVM sandbox escape via puppeteer allowlist - authenticated RCE and arbitrary file read via Chromiumflowise, flowise-components
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- Criticaln8n Has an Arbitrary File Read via Git Noden8n, n8n, n8n
- Criticaln8n: HTTP Request Node Pagination Prototype Pollution to RCEn8n, n8n, n8n
- Criticaln8n Has an XML Node Prototype Pollution Patch Bypassn8n, n8n, n8n
- Criticaln8n has XML Node Prototype Pollution that to RCEn8n, n8n, n8n
- Criticaln8n has Prototype Pollution in XML Webhook Body Parser that Leads to RCEn8n, n8n, n8n
The impact, patch and workaround text comes from the advisory, shortened (published by n8n). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.