Enable SSRF protection

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.

Enable SSRF protection

N8N_SSRF_PROTECTION_ENABLED=true

When 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.

Default blocked ranges

When SSRF protection is enabled, the following IP ranges are blocked by default:

You can extend this list with N8N_SSRF_BLOCKED_IP_RANGES=default,100.0.0.0/8.

Allow access to internal services

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):

N8N_SSRF_ALLOWED_HOSTNAMES=*.n8n.internal,*.company.local

Allow by IP range:

N8N_SSRF_ALLOWED_IP_RANGES=10.0.1.0/24,10.0.2.50/32

Related resources

Refer to SSRF protection environment variables for the full list of configuration options.

Refer to Configuration methods for more information on setting environment variables.