flowise
Affected
- introduced
0, fixed3.1.3(semver)
Fixed versions
3.1.3
Fix
- Fixed version
3.1.3npm install [email protected]
Advisory
Also known as: CVE-2026-69262
Flowise: DELETE /api/v1/chatflows/:id does not validate resource type, allowing agentflows:delete and chatflows:delete to delete each other’s flow type
summary:
In Flowise, DELETE /api/v1/chatflows/:id authorizes requests with checkAnyPermission('chatflows:delete,agentflows:delete'). Possession of either permission is sufficient to reach the delete path. The delete logic does not validate the target resource type, allowing a caller with only agentflows:delete to delete a CHATFLOW, and a caller with only chatflows:delete to delete an AGENTFLOW.
details:
The delete route accepts either chatflows:delete or agentflows:delete. The subsequent logic only resolves the target record by id and workspaceId, then deletes by id without checking whether the target resource type matches the granted permission domain.
As a result, there is no binding between permission scope and flow type:
agentflows:delete can be used to delete CHATFLOWchatflows:delete can be used to delete AGENTFLOWThis breaks the intended RBAC separation between Chatflows and Agentflows.
impact:
Users authorized to manage only one flow type can delete the other flow type within the same workspace, resulting in unauthorized deletion and configuration loss.
reproduction steps:
CHATFLOW and record its id.agentflows:delete.curl -i -X DELETE \
-H 'Authorization: Bearer <agentflows_delete_only_key>' \
http://localhost:8080/api/v1/chatflows/<chatflow_id>
200 OK response, for example:{"raw":[],"affected":1}
id again and observe 404 Not Found.High Basis: The source's own band: HIGH
0, fixed 3.1.3 (semver)3.1.3
3.1.3npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0