在 n8n 1.123.69 之前的版本、2.x 版本中 2.33.4 之前的版本,以及 2.x 版本中 2.34.1 之前的版本中,GraphQL 节点存在允许的域名绕过漏洞。当节点的“Authentication(身份验证)”参数设置为表达式模式时,所有受身份验证限制的凭据选择器都会被视作有效状态;如果附加了两种不同类型凭据的,节点仅强制执行第一个凭据的 allowed-domains 策略,但同时仍会附加来自两个凭据的材料。因此,具有工作流编写权限的已认证用户可以将受限域名的凭据发送到攻击者控制的端点,从而利
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-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-77069 | 2.3 LOW | n8n before 1.123.69 SSRF Protection Bypass via OAuth2 |
No comments yet