CVE-2026-69252 FlowiseAI CVE debrief

Who should care

Flowise administrators, users with API keys, and security teams responsible for monitoring and protecting large language model deployments should assess their exposure and verify that their deployments are updated to version 3.1.3 or later.

Why it matters

CVE-2026-69252 is a high-severity vulnerability in Flowise that allows unauthorized file access and deletion. Defenders should verify Flowise deployments, restrict API key permissions, and monitor for unusual activities to prevent data breaches and integrity loss.

• Unrestricted file access and deletion can lead to data breaches and integrity loss.
• Low-privileged users can exploit this vulnerability to affect other workspaces.
• Verification of user permissions and API key restrictions is necessary to prevent exploitation.
• Remediation priority is high due to the potential for significant data impact.

Technical summary

The /api/v1/files route in Flowise versions prior to 3.1.3 was not properly secured, allowing low-privileged authenticated API keys to list and delete files across workspaces within the same organization. This was due to the lack of proper permission checks and reliance on the feat:files feature gate alone. A low-privileged authenticated API key with unrelated permissions could call GET /api/v1/files to list files under the organization storage root and DELETE /api/v1/files?path=... to delete files belonging to other workspaces in the same organization because getAllFiles and deleteFile used activeOrganizationId and a user-controlled path without restricting access by permissions or activeWorkspaceId. The issue

Defensive priority

Defenders should prioritize verifying Flowise deployments, especially those with multiple workspaces or sensitive data, and ensure all users have the correct permissions.

Recommended defensive actions

• Verify Flowise deployments to ensure version 3.1.3 or later is used.
• Review and restrict API key permissions to prevent unauthorized file access.
• Monitor for unusual file access or deletion activities.
• Implement additional access controls, such as IP restrictions or multi-factor authentication, for sensitive Flowise deployments.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, its impact, and the fix in version 3.1.3. However, additional information on affected versions, exploitation, or specific attack scenarios is limited.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.