在 n8n 1.123.69 之前版本、2.x 系列 2.33.4 之前版本,以及 2.34.x 系列 2.34.1 之前版本中,存在一个表达式注入漏洞,该漏洞出现在“资源定位器”字段链接预览渲染过程中。编辑器未对字段存储值进行表达式语法校验,便将其直接拼接到节点类型的 URL 模板中。经过身份验证的用户可以存储恶意构造的值,当其他用户在编辑器中打开受影响节点时,注入的表达式将在受害用户的已认证会话中被当作 JavaScript 执行,从而导致跨用户脚本执行(Cross-User Script Execution)
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-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-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