CVE-2026-69258
Received Received - Intake

Authentication Bypass in Flowise AI via Config Override

Publication date: 2026-08-04

Last updated on: 2026-08-04

Assigner: GitHub, Inc.

Description
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, the unauthenticated POST /api/v1/prediction/:id endpoint accepted an overrideConfig object and unconditionally spread it into internal flowConfig and flowData objects in packages/server/src/utils/buildChatflow.ts and packages/server/src/utils/index.ts without checking apiOverrideStatus. This allowed unauthenticated attackers to inject arbitrary properties into the flow execution context of any public chatflow, overwrite values such as chatId, sessionId, and chatHistory, and control values resolved through $flow.* template variables consumed by flow nodes. This issue is fixed in version 3.1.3.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-04
Last Modified
2026-08-04
Generated
2026-08-04
AI Q&A
2026-08-04
EPSS Evaluated
N/A
NVD
CVE-2026-69258
EUVD
EUVD-2026-52762

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
flowise flowise 3.1.3
flowiseai flowise 3.1.3
flowiseai flowise to 3.1.3 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
CWE-915 The product receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Flowise allows unauthenticated attackers to inject arbitrary properties into the flow execution context of any public chatflow by exploiting the unauthenticated POST /api/v1/prediction/:id endpoint. The issue occurs because the overrideConfig object is unconditionally spread into internal flowConfig and flowData objects without checking apiOverrideStatus, enabling control over values like chatId, sessionId, and chatHistory.

Detection Guidance

Check Flowise logs for POST requests to /api/v1/prediction/:id with overrideConfig parameters. Monitor for unauthorized modifications to chatId, sessionId, or chatHistory in flow execution contexts.

Impact Analysis

This vulnerability can lead to session hijacking by overwriting chatId or sessionId, allowing access to another user's conversation history. Attackers can inject malicious chat history to perform prompt injection attacks or control $flow.* template variables to manipulate node configurations, API endpoints, or file paths.

Compliance Impact

This vulnerability could violate GDPR by enabling unauthorized access to user data through session hijacking and chat history manipulation. For HIPAA, it risks exposing protected health information if chatflows handle such data. Compliance may be impacted due to potential breaches of confidentiality and integrity requirements.

Mitigation Strategies

Upgrade Flowise to version 3.1.3 or later to apply the security fix. If upgrading is not possible, remove the overrideConfig spread operations in buildChatflow.ts and index.ts manually.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-69258. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart