Advisory details:
github_osv / GHSA-p5w8-m249-4r4v
| Advisory ID | github_osv/GHSA-p5w8-m249-4r4v |
| Aliases |
CVE-2026-69262
|
| Summary | 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 `CHATFLOW` - `chatflows:delete` can be used to delete `AGENTFLOW` This 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: 1. Log in as a user who can create API keys. 2. Create a normal `CHATFLOW` and record its `id`. 3. Create an API key with only `agentflows:delete`. 4. Use that API key to send: ```bash curl -i -X DELETE \ -H 'Authorization: Bearer <agentflows_delete_only_key>' \ http://localhost:8080/api/v1/chatflows/<chatflow_id> ``` 5. Observe a `200 OK` response, for example: ```json {"raw":[],"affected":1} ``` 6. Read the same `id` again and observe `404 Not Found`. |
| Status | Published |
| Exploitability | 0.5 |
| Weighted Severity | 6.4 |
| Risk | 3.2 |
| Affected and Fixed Packages | Package Details |
| Introduced and Fixed Package Commit Patches | Package Commit Patches Details |
| CWE-863 | Incorrect Authorization |
| System | Score | Found at |
|---|---|---|
| cvssv4 | 7.1 | https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/08/GHSA-p5w8-m249-4r4v/GHSA-p5w8-m249-4r4v.json |
| generic_textual | HIGH |
| Reference id | Reference type | URL |
|---|---|---|
| https://github.com/FlowiseAI/Flowise | ||
| 2f528ceced74afaa95fc7a282965e7788796448b | Other | https://github.com/FlowiseAI/Flowise/commit/2f528ceced74afaa95fc7a282965e7788796448b |
| 6445 | Other | https://github.com/FlowiseAI/Flowise/pull/6445 |
| flowise@3.1.3 | Other | https://github.com/FlowiseAI/Flowise/releases/tag/flowise@3.1.3 |
| GHSA-p5w8-m249-4r4v | Other | https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-p5w8-m249-4r4v |
No EPSS data available for this advisory.
| Patch URL | |
|---|---|
| There are no known patches. | |
| Attack Vector (AV) | Attack Complexity (AC) | Attack Requirements (AT) | Privileges Required (PR) | User Interaction (UI) | Vulnerable System Impact Confidentiality (VC) | Vulnerable System Impact Integrity (VI) | Vulnerable System Impact Availability (VA) | Subsequent System Impact Confidentiality (SC) | Subsequent System Impact Integrity (SI) | Subsequent System Impact Availability (SA) |
|---|---|---|---|---|---|---|---|---|---|---|
network adjacent local physical |
low high |
none present |
none low high |
none passive active |
high low none |
high low none |
high low none |
high low none |
high low none |
high low none |
Vector: SSVCv2/E:P/A:Y/T:P/P:M/B:A/M:M/D:T/2026-08-05T13:43:28Z/
Decision: Track
Source URL: https://github.com/cisagov/vulnrichment/blob/develop/2026/69xxx/CVE-2026-69262.json
Source Advisory: vulnrichment/CVE-2026-69262
[{'Exploitation': 'poc'},
{'Automatable': 'yes'},
{'Technical Impact': 'partial'},
{'Mission Prevalence': 'minimal'},
{'Public Well-being Impact': 'material'},
{'Mission & Well-being': 'medium'}]