n8n: N8n versions before 2.32.1 contain a server-side request forgery protection bypass vulnerability…
n8n
- Severity
- High, CVSS 8.3
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
- Record
- CVE-2026-72768
- Affects
- n8n
- Known exploited
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Published
- Record first published by the source
- August 11, 2026
- Source last modified
- October 24, 2026
Description
n8n versions before 2.32.1 contain a server-side request forgery protection bypass vulnerability in the MCP Client node that allows authenticated users to bypass SSRF protections. Attackers can craft workflows that send requests to internal or blocked hosts without routing through SSRF protection, exposing internal services and reading responses back through the workflow.
Description quoted from the NVD record.
Who is affected
This flaw affects n8n, a tool for automating tasks by connecting apps and services into step-by-step workflows. It affects n8n versions before 2.32.1, in the MCP Client building block that workflows can use. Someone who already has a login to your n8n can build a workflow that slips past the safeguards meant to stop it from contacting internal or blocked systems. That person could then reach services on your internal network that should be off limits and read what those services send back. This flaw is rated High.
What to do
- Find out who installed or runs n8n for your organization: a staff member, a volunteer, or an IT provider or vendor who manages it for you.
- If your organization runs n8n itself, have the person who looks after it update it to version
2.32.1or later, which fixes this flaw. Do this soon, since anyone with a login to n8n could take advantage of it. - If an IT provider or vendor runs n8n for you, send them this advisory and ask when the update to version
2.32.1or later will be done.
Analysis written from the source record as of October 24, 2026 and reviewed before publishing.