CVE-2026-46444: Flowise: Vector Store No Permission Checks
FINDING 4: OpenAI Assistants Vector Store - No Auth on CRUD Operations Severity: HIGH (CVSS ~8.1) Type: CWE-306 (Missing Authentication for Critical Function) File: packages/server/src/routes/openai-assistants-vector-store/index.ts
Description: ALL CRUD endpoints for OpenAI Assistants Vector Store have no authentication middleware AND the route path /api/v1/openai-assistants-vector-store is NOT in WHITELISTURLS. However, it is also NOT protected by the main auth middleware when accessed via API key — the route requires API key auth (not whitelisted), but NO permission checks exist on any operation.
The real issue is that the routes have no checkAnyPermission() middleware, meaning any authenticated user regardless of role can: - Create vector stores - Upload files to vector stores - Delete vector stores and files - Modify any vector store
Evidence: typescript // No permission middleware on any route router.post('/', controller.createAssistantVectorStore) // No permission check router.put(['/', '/:id'], controller.updateAssistantVectorStore) // No permission check router.delete(['/', '/:id'], controller.deleteAssistantVectorStore) // No permission check router.post('/:id', getMulterStorage().array('files'), controller.uploadFilesToAssistantVectorStore) // No permission check
Impact: Any authenticated user can manipulate OpenAI vector stores, upload malicious files, delete data, or exfiltrate stored documents regardless of their assigned permissions.
Other sources
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to version 3.1.2, all CRUD endpoints for OpenAI Assistants Vector Store have no authentication middleware and the route path /api/v1/openai-assistants-vector-store is not in WHITELISTURLS. However, it is also not protected by the main auth middleware when accessed via API key — the route requires API key auth (not whitelisted), but no permission checks exist on any operation. This issue has been patched in version 3.1.2.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/flowiseto a version that resolves this vulnerability.Fixed in 3.1.2 - Configuration
Add checkAnyPermission() middleware to all CRUD endpoints (POST '/', PUT ['/', '/:id'], DELETE ['/', '/:id'], POST '/:id' upload) so that create, update, delete and upload operations require appropriate permission checks; ensure the route is enforced by the main auth middleware for API key access as well.
OpenAI Assistants Vector Store routes (packages/server/src/routes/openai-assistants-vector-store/index.ts) checkAnyPermission middleware = present
Event History
Frequently Asked Questions
What is the severity of CVE-2026-46444?
The severity of CVE-2026-46444 is high, with a CVSS score of 8.7.
What does CVE-2026-46444 affect?
CVE-2026-46444 affects the OpenAI Assistants Vector Store within the Flowise application.
How do I fix CVE-2026-46444?
To fix CVE-2026-46444, implement proper authentication checks for all CRUD operations in the affected vector store.
What type of vulnerability is CVE-2026-46444?
CVE-2026-46444 is classified as a CWE-306 vulnerability due to missing authentication for critical functions.
When was CVE-2026-46444 published?
CVE-2026-46444 was published on May 14, 2026.