Cross-workspace evaluator takeover via protected-field mass assignment
Published Jun 8, 2026 · Updated Jun 8, 2026
Mass assignment in Flowise before 3.1.2 allows remote authenticated users to take over evaluator records across workspaces. EvaluatorDTO.toEntity copies the request body into an Evaluator with Object.assign, allowing protected id and workspaceId fields to reach persistence. Any authenticated workspace member with evaluator edit permission can move a record into another workspace, where members can view, modify, or use its scoring rubric.
Summary
What happened
Mass assignment in Flowise before 3.1.2 allows remote authenticated users to take over evaluator records across workspaces. EvaluatorDTO.toEntity copies the request body into an Evaluator with Object.assign, allowing protected id and workspaceId fields to reach persistence. Any authenticated workspace member with evaluator edit permission can move a record into another workspace, where members can view, modify, or use its scoring rubric.
The record
- CVE
- CVE-2026-46480
- Published
- Jun 8, 2026
- Updated
- Jun 8, 2026
- Vendor
- FlowiseAI
- Product
- Flowise
- Classifications
- CWE-915, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 8, 2026CVE publishedPublication date reported by the CVE source.
- Jun 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.1.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-wxrr-jp8m-qq7f exploit chainproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo