DEV Community

CVE Reports
CVE Reports

Posted on • Originally published at cvereports.com

CVE-2026-69258: CVE-2026-69258: Unauthenticated Property Injection and Authorization Bypass in Flowise

#security #cve #cybersecurity

CVE-2026-69258: Unauthenticated Property Injection and Authorization Bypass in Flowise

Vulnerability ID: CVE-2026-69258
CVSS Score: 8.8
Published: 2026-08-04

CVE-2026-69258 is a high-severity property injection and unauthenticated authorization bypass vulnerability in Flowise, a drag-and-drop orchestration interface for building customized LLM workflows. In affected versions prior to 3.1.3, the unauthenticated prediction API endpoint (POST /api/v1/prediction/:id) processed client-controlled parameters inside an overrideConfig payload without authorization checks. The backend unconditionally spread this object into internal context structures, enabling unauthenticated remote attackers to overwrite critical session values, pollute execution contexts, and bypass flow restrictions.

TL;DR

An unauthenticated property injection vulnerability in Flowise (< 3.1.3) allows remote attackers to overwrite critical workflow parameters, facilitating session hijacking and prompt injection.

⚠️ Exploit Status: POC

Technical Details

  • CWE ID: CWE-915 / CWE-639
  • Attack Vector: Network
  • CVSS v4.0 Score: 8.8
  • Vulnerability Class: Property Injection / Authorization Bypass
  • Exploit Status: Proof-of-Concept Available
  • Remediation: Upgrade to v3.1.3 or higher

Affected Systems

  • Flowise deployments exposing unauthenticated prediction endpoints (< 3.1.3)
  • Flowise: < 3.1.3 (Fixed in: 3.1.3)

Code Analysis

Commit: 23b997e

Remove object spread operators for overrideConfig parameters to prevent unauthenticated property injection.

Mitigation Strategies

  • Upgrade Flowise server instances to version 3.1.3 or higher immediately.
  • Deploy WAF rules to block JSON requests targeting prediction endpoints that contain 'overrideConfig' along with internal state keys.
  • Audit existing workflow schemas to identify and secure any reliance on user-supplied variables within administrative routing nodes.

Remediation Steps:

  1. Determine current package version using 'npm list -g flowise' or checking the container version.
  2. Run 'npm install -g flowise@latest' or update the docker-compose image to 'flowiseai/flowise:3.1.3'.
  3. Restart the Flowise service to apply configuration changes.
  4. Verify that the prediction API endpoint now safely ignores unauthenticated parameters inside the overrideConfig parameter block.

References

Read the full report for CVE-2026-69258 on our website for more details including interactive diagrams and full exploit analysis.

Top comments (0)