CVE-2026-69258 FlowiseAI CVE debrief

Who should care

Flowise users and administrators, security teams monitoring for potential attacks on chatflows and large language models, and operators managing affected deployments should review and apply the patch in version 3.1.3, restrict access to the /api/v1/prediction/:id endpoint, monitor for suspicious activity on Flowise chatflows, verify and validate user input to prevent property injection, perform vulnerability scanning on Flowise deployments, review compensating controls for exposed systems, and track exceptions and retest remediated assets.

Technical summary

The unauthenticated POST /api/v1/prediction/:id endpoint in Flowise accepted an overrideConfig object and spread it into internal flowConfig and flowData objects without checking apiOverrideStatus, allowing attackers to inject arbitrary properties into Flowise chatflow execution contexts, overwriting values like chatId, sessionId, and chatHistory, and controlling template variables consumed by flow nodes. This issue is fixed in version 3.1.3, which checks apiOverrideStatus before applying override configurations.

Defensive priority

Unauthenticated attackers can inject arbitrary properties into Flowise chatflow execution contexts, overwriting values like chatId, sessionId, and chatHistory, and controlling template variables.

Recommended defensive actions

• Review and apply the patch in version 3.1.3
• Restrict access to the /api/v1/prediction/:id endpoint
• Monitor for suspicious activity on Flowise chatflows
• Verify and validate user input to prevent property injection
• Perform vulnerability scanning on Flowise deployments
• Review compensating controls for exposed systems
• Track exceptions and retest remediated assets

Evidence notes

The CVE record and NVD detail provide information on the vulnerability in Flowise, a drag & drop user interface to build a customized large language model flow. The source item and references offer additional context and resources related to the issue. Evidence limits suggest verifying Flowise version 3.1.3 or later for patched deployments, and reviewing chatflow configurations for potential exposure. Defenders should validate affected scope, assess operational impact, and monitor for suspicious activity.

Official resources