Flowise 3.1.4 之前的版本未能将企业组织和工作区成员资格 API 限制在调用者所属的租户范围内,使得经过身份验证的用户可以提供任意的组织 ID。攻击者可以利用组织和用户端点以及工作区端点中不充分的租户隔离缺陷,将自身添加为组织所有者、创建工作区,并获取受害组织的行政访问权限。
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-91934 | 8.8 HIGH | Flowise before 3.1.4 Remote Code Execution via SQL Database Chain |
| CVE-2026-91931 | 8.5 HIGH | Flowise before 3.1.4 Remote Code Execution via Custom MCP npx |
| CVE-2026-91932 | 8.5 HIGH | Flowise before 3.1.4 Remote Code Execution via cwd Parameter |
| CVE-2026-91935 | 8.3 HIGH | Flowise before 3.1.4 SSRF and API Key Exfiltration via Chat Model Nodes |
| CVE-2026-91937 | 7.5 HIGH | Flowise before 3.1.4 NoSQL Injection via sessionId |
| CVE-2026-91933 | 7.1 HIGH | Flowise before 3.1.4 Authorization Bypass via openai-realtime |
| CVE-2026-91929 | 7.1 HIGH | Flowise before 3.1.4 Cross-Tenant Authorization Bypass |
| CVE-2026-91938 | 7.1 HIGH | Flowise before 3.1.4 Server-Side Request Forgery via document loaders |
| CVE-2026-91936 | 6.8 MEDIUM | Flowise before 3.1.4 Script Injection via Docker Workflows |
No comments yet