{"vulnerability": "ghsa-6vh2-wg4h-4vwj", "sightings": [{"uuid": "a5d06542-daaa-47a0-86cb-378cb48738dc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "GHSA-6vh2-wg4h-4vwj", "type": "seen", "source": "https://gist.github.com/alon710/6149a4f7f7f2ae19b65c163d6f6db13a", "content": "# CVE-2026-69258: CVE-2026-69258: Unauthenticated Property Injection and Authorization Bypass in Flowise\n\n> **CVSS Score:** 8.8\n> **Published:** 2026-08-04\n> **Full Report:** https://cvereports.com/reports/CVE-2026-69258\n\n## Summary\nCVE-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.\n\n## TL;DR\nAn unauthenticated property injection vulnerability in Flowise (< 3.1.3) allows remote attackers to overwrite critical workflow parameters, facilitating session hijacking and prompt injection.\n\n## Exploit Status: POC\n\n## Technical Details\n\n- **CWE ID**: CWE-915 / CWE-639\n- **Attack Vector**: Network\n- **CVSS v4.0 Score**: 8.8\n- **Vulnerability Class**: Property Injection / Authorization Bypass\n- **Exploit Status**: Proof-of-Concept Available\n- **Remediation**: Upgrade to v3.1.3 or higher\n\n## Affected Systems\n\n- Flowise deployments exposing unauthenticated prediction endpoints (< 3.1.3)\n- **Flowise**: < 3.1.3 (Fixed in: `3.1.3`)\n\n## Mitigation\n\n- Upgrade Flowise server instances to version 3.1.3 or higher immediately.\n- Deploy WAF rules to block JSON requests targeting prediction endpoints that contain 'overrideConfig' along with internal state keys.\n- Audit existing workflow schemas to identify and secure any reliance on user-supplied variables within administrative routing nodes.\n\n**Remediation Steps:**\n1. Determine current package version using 'npm list -g flowise' or checking the container version.\n2. Run 'npm install -g flowise@latest' or update the docker-compose image to 'flowiseai/flowise:3.1.3'.\n3. Restart the Flowise service to apply configuration changes.\n4. Verify that the prediction API endpoint now safely ignores unauthenticated parameters inside the overrideConfig parameter block.\n\n## References\n\n- [GitHub Security Advisory GHSA-6vh2-wg4h-4vwj](https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-6vh2-wg4h-4vwj)\n- [Flowise Pull Request #6279](https://github.com/FlowiseAI/Flowise/pull/6279)\n- [Flowise Security Fix Commit](https://github.com/FlowiseAI/Flowise/commit/23b997ee5ef9e269b628bad0f56f1ecb86bd2fca)\n- [Flowise v3.1.3 Release Notes](https://github.com/FlowiseAI/Flowise/releases/tag/flowise@3.1.3)\n- [CVE Official Entry](https://www.cve.org/CVERecord?id=CVE-2026-69258)\n\n\n---\n*Generated by [CVEReports](https://cvereports.com/reports/CVE-2026-69258) - Automated Vulnerability Intelligence*", "creation_timestamp": "2026-08-04T16:31:33.408927Z"}]}