n8n 版本低于 1.123.69、2.33.4 和 2.34.1 的 Form 节点完成页面存在存储型跨站脚本(XSS)漏洞。该完成页面仅在 未设置为 时才应用沙箱化的内容安全策略(Content-Security-Policy),而 始终被渲染为原始 HTML。经过身份验证的用户可以通过表达式将 设置为 ,同时保留 的值,从而导致完成页面从 n8n 源站点提供未过滤的 HTML 和脚本。任何提交该公共表单的访问者,其浏览器都会在同源上下文中执行该脚本,从而影响其会话安全。
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-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-77085 | 6.3 MEDIUM | n8n before 2.34.1 SSRF Protection Bypass via SearXNG Tool |
| 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