INCIDENT MAP

Browse / MCP and Tool Server Flaws / CVE-2026-72768

n8n: SSRF Protection Bypass via MCP Client Node

CVE-2026-72768 ยท 2026-07-22 moderate

Class
MCP and Tool Server Flaws (filed by a model that read the advisory)
Technique
Server-side request forgery
Affected
n8n (npm)
Gets past
SSRF protection
CVSS
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:H/SI:H/SA:L
EPSS
0.4% chance of exploitation in 30 days

How it works, in short

The MCP Client node sends requests to user-supplied endpoints without applying SSRF checks or pinning resolved addresses, letting workflow users reach internal hosts. (Our summary, written by a model. The source text is below.)

Details

Impact

On an n8n instance with SSRF protection enabled, the MCP Client node sent requests to a user-supplied endpoint without routing them through that protection and without pinning the resolved address. An authenticated user who could create or edit a workflow could therefore cause the server to connect to internal or otherwise blocked hosts and read the responses back through the workflow, exposing internal services the SSRF protection was meant to protect.

Patches

The issue has been fixed in n8n versions 2.31.5 and 2.32.1. Users should upgrade to one of these versions or later to remediate the vulnerability.

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Restrict n8n instance access to fully trusted users only.
- Disable the MCP Client node by adding it to the NODES_EXCLUDE environment variable.
- Restrict network egress from the n8n host to block access to internal and link-local address ranges at the network level.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

References

Source: GitHub Advisory Database, used under CC BY 4.0.