The security intelligence platform for AI teams
AI security threats move fast and get buried under hype and noise. Built by an Information Systems Security researcher to help security teams and developers stay ahead of vulnerabilities, privacy incidents, safety research, and policy developments.
Independent research. No sponsors, no paywalls, no conflicts of interest.
No new AI/LLM security issues were identified today.
Fix: Upgrade to n8n-mcp 2.47.4 or later (no configuration changes required). If you cannot upgrade immediately, the source explicitly mentions three workarounds: (1) use egress filtering to block outbound traffic from the n8n-mcp container to private IP ranges (RFC1918: 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) and link-local 169.254.0.0/16; (2) disable multi-tenant headers by unsetting ENABLE_MULTI_TENANT and not accepting x-n8n-url / x-n8n-key headers at the reverse proxy if per-request instance switching is not needed; (3) restrict AUTH_TOKEN distribution to fully trusted operators only until you can upgrade.
GitHub Advisory Database