Enable SSRF protection
Last updated
Was this helpful?
Available since 2.12.0
Server-Side Request Forgery (SSRF) attacks abuse workflow nodes to make requests to internal network resources, cloud metadata endpoints, or localhost services that shouldn't be accessible.
SSRF protection is an additional application-level defense. You should always configure network-level protections (firewalls, security groups, network policies) on your infrastructure as your primary line of defense. n8n's SSRF protection adds defense-in-depth on top of those controls.
N8N_SSRF_PROTECTION_ENABLED=trueWhen enabled, n8n validates all outbound HTTP requests from user-controllable nodes (such as the HTTP Request node) against the configured blocked and allowed ranges. This includes redirect targets and DNS resolution to prevent bypass techniques like DNS rebinding.
When SSRF protection is enabled, the following IP ranges are blocked by default:
10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16
RFC 1918 private addresses
127.0.0.0/8, ::1/128
Loopback
169.254.0.0/16, fe80::/10
Link-local
fc00::/7, fd00::/8
IPv6 unique local
0.0.0.0/8, 192.0.0.0/24, 192.0.2.0/24, 198.18.0.0/15, 198.51.100.0/24, 203.0.113.0/24
Reserved/special purpose
You can extend this list with N8N_SSRF_BLOCKED_IP_RANGES=default,100.0.0.0/8.
If your workflows need to reach legitimate internal services, use allowlists. Allowlists take precedence over blocklists, following this order: hostname allowlist > IP allowlist > IP blocklist.
Allow by hostname pattern (supports wildcards like *.n8n.internal):
Allow by IP range:
Only allowlist hostnames within your control (internal DNS zones). Hostname allowlists bypass IP blocklist checks.
Refer to SSRF protection environment variables for the full list of configuration options.
Refer to Configuration methods for more information on setting environment variables.
Last updated
Was this helpful?
Was this helpful?
N8N_SSRF_ALLOWED_HOSTNAMES=*.n8n.internal,*.company.localN8N_SSRF_ALLOWED_IP_RANGES=10.0.1.0/24,10.0.2.50/32