Intel

AIKIDO-2026-10739

n8n-mcp is vulnerable to Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF)GHSA-8g7g-hmwm-6rv2 Published May 6, 2026

83

High Risk

This Affects:

JSn8n-mcp
0.0.1 - 2.50.0
Fixed in 2.50.1
Are you affected? Scan for Free

TL;DR

Caller-controlled fragments were interpolated into outbound n8n API paths without strict segment validation and encoding, which opens route manipulation and traversal-style pivots against backend endpoints. Outbound webhook and related HTTP calls still followed redirects by default, so an allowed URL could bounce toward internal or unintended hosts during SSRF checks. Telemetry payloads could retain sensitive fields before persistence. The release validates or encodes path segments, disables redirect following for those outbound flows, and redacts telemetry content before storage.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range.

Background info

n8n-mcp is vulnerable to Server-Side Request Forgery (SSRF) in versions 0.0.1 - 2.50.0.

How to fix this

Upgrade the n8n-mcp library to the patch version.