在 n8n 2.34.1 之前的版本以及 2.33.x 系列中低于 2.33.4 的版本中,SearXNG Agent 工具存在一个 SSRF(服务端请求伪造)保护绕过漏洞。该工具通过一个原始 HTTP 客户端向用户提供 API URL 发送请求,而未将请求路由至 n8n 集中式的 SSRF 防护机制。在启用了 的环境中,拥有创建 SearXNG 凭据和配置个人代理权限的已认证用户,可以将 API URL 设置为内部主机地址,从而导致 n8n 服务器连接到该内部主机,并通过代理聊天输出返回响应内容。
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-77080 | 8.7 HIGH | n8n before 1.123.69 Arbitrary File Read and Write via Snowflake |
| CVE-2026-77068 | 8.7 HIGH | n8n before 2.34.1 Remote Code Execution via Path Traversal |
| CVE-2026-77075 | 8.4 HIGH | n8n before 1.123.69 Expression Injection via Resource Locator |
| CVE-2026-77072 | 8.4 HIGH | n8n before 1.123.69 Stored XSS via Form Completion Page |
| CVE-2026-77084 | 7.7 HIGH | n8n before 1.123.69 Remote Code Execution via Git Node Configuration Values |
| CVE-2026-77079 | 7.4 HIGH | n8n before 2.34.1 Authorization Bypass via Custom Role Deletion |
| CVE-2026-77077 | 7.2 HIGH | n8n before 1.123.69 Remote Code Execution via EventEmitter Prototype Pollution |
| CVE-2026-77071 | 7.1 HIGH | n8n before 1.123.69 PostgREST Filter Injection via Supabase |
| CVE-2026-77076 | 7.1 HIGH | n8n before 1.123.69 Credential Leak via GraphQL Node Error |
| CVE-2026-77070 | 7.1 HIGH | n8n before 1.123.69 NoSQL Injection via MongoDB Node |
| CVE-2026-77083 | 6.0 MEDIUM | n8n before 1.123.69 Code Node Sandbox Escape via Function.prototype Pollution |
| CVE-2026-77074 | 6.0 MEDIUM | n8n before 1.123.69 SSRF via Edit Image Node |
| CVE-2026-77073 | 5.3 MEDIUM | n8n before 2.34.1 Cross-Project Credential Access via MCP |
| CVE-2026-77082 | 5.3 MEDIUM | n8n before 1.123.69 ReDoS via Filter and Switch Node |
| CVE-2026-77081 | 5.1 MEDIUM | n8n before 1.123.69 Allowed-Domains Bypass via GraphQL Node |
| CVE-2026-77069 | 2.3 LOW | n8n before 1.123.69 SSRF Protection Bypass via OAuth2 |
No comments yet