CVE-2026-70475: 
Flowise vulnerability analysis and mitigation

CVE-2026-70475 is a Missing Authorization vulnerability in FlowiseAI Flowise, a drag-and-drop UI for building customized LLM workflows. The PUT /api/v1/executions/:id endpoint in packages/server/src/routes/executions/index.ts lacks the checkAnyPermission() middleware present on all other execution endpoints, allowing any authenticated user to modify execution records regardless of their assigned role. It affects Flowise versions up to and including 3.1.2, and was fixed in version 3.1.3. The vulnerability was discovered by researcher Dimpal Jadhav on 2026-03-17, published to the GitHub Advisory Database on 2026-08-04, and carries a CVSS v4.0 base score of 7.1 (High) (Github Advisory, Flowise Security Advisory).

The root cause is CWE-862 (Missing Authorization): the route definition for PUT /api/v1/executions/:id in packages/server/src/routes/executions/index.ts omits the checkAnyPermission() middleware call that guards the GET (executions:view) and DELETE (executions:delete) routes on the same resource. An attacker with any valid, low-privileged API key can send a crafted HTTP PUT request directly to this endpoint over the network, supplying arbitrary JSON to overwrite execution state, data, and metadata — no additional conditions or user interaction are required. The fix introduced a new executions:update RBAC permission and applied checkAnyPermission('executions:update') to the PUT route (Flowise Security Advisory, Fix PR #6409, Fix Commit).

Successful exploitation allows a low-privileged authenticated user to perform unauthorized modification of any execution record within their workspace, constituting a privilege escalation. An attacker can alter execution state (e.g., marking a running workflow as FINISHED), inject or overwrite execution data and metadata, and manipulate workflow results — undermining the integrity of LLM-driven automation pipelines. There is no direct confidentiality or availability impact, but falsified execution records could be used to deceive administrators, cover tracks, or corrupt downstream processes that rely on execution output (Github Advisory, Flowise Security Advisory).

The NVD SSVC assessment classifies exploitation status as "poc" (proof-of-concept available), with the reproduction steps published directly in the security advisory (Flowise Security Advisory). The EPSS score is 0.0, indicating low current probability of widespread exploitation. No in-the-wild exploitation or threat actor attribution has been reported, and the vulnerability is not listed in the CISA KEV catalog. Exploitation requires only a valid low-privileged API key and knowledge of a target execution ID, making it straightforward for any insider or compromised account (Github Advisory).

1. Obtain credentials: Acquire any valid low-privileged API key for the target Flowise workspace (e.g., via a free trial account, compromised credentials, or insider access).
2. Enumerate execution IDs: Use the authenticated GET /api/v1/executions endpoint (which requires executions:view permission) or observe execution IDs from the UI to identify target execution records.
3. Craft the malicious PUT request: Construct an HTTP PUT request targeting PUT /api/v1/executions/<EXECUTION_ID> with the low-privileged API key and a JSON body containing the desired manipulated values.
4. Send the request: Execute the request — for example:

curl -X PUT https://TARGET/api/v1/executions/EXECUTION_ID \
  -H "Authorization: Bearer LOW_PRIV_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"state": "FINISHED", "data": "MANIPULATED"}'

5. Verify manipulation: Confirm the execution record has been updated by querying GET /api/v1/executions/<EXECUTION_ID> or checking the Flowise UI, observing the falsified state or data (Flowise Security Advisory).

• Network: Unexpected HTTP PUT requests to /api/v1/executions/<id> originating from accounts that do not normally perform update operations; PUT requests from low-privileged API keys that typically only perform read actions.
• Logs: Server access logs showing PUT /api/v1/executions/ requests authenticated with low-privilege tokens, especially if the same token has never previously issued PUT requests; repeated PUT requests to multiple execution IDs in a short timeframe.
• Application Data: Execution records with unexpected state changes (e.g., FINISHED for workflows that should still be running), altered data or metadata fields inconsistent with normal workflow output, or timestamps that do not align with actual workflow activity.

Upgrade Flowise to version 3.1.3 or later, which adds the executions:update RBAC permission and applies checkAnyPermission('executions:update') middleware to the PUT /api/v1/executions/:id route (Flowise Release 3.1.3, Fix Commit). As a temporary workaround for deployments that cannot immediately upgrade, restrict network-level access to the Flowise API to trusted users only (e.g., via firewall rules or API gateway policies), and audit API key assignments to minimize the number of accounts with any authenticated access. Review execution records for unexpected modifications as part of incident response.