CVE-2026-70472: Flowise: Cross-workspace credential IDOR in openai-assistants-vector-store
Summary
These endpoints accept a client-controlled credential parameter. The server loads credentials by id and uses them directly, without checking whether that credential belongs to the caller’s workspace. If an attacker knows another workspace’s credentialId, they can use that workspace’s OpenAI key.
Details
Route permissions (assistants:) only check feature access. They do not check credential ownership. The controller passes req.query.credential straight to the service. The service does findOneBy({ id: credentialId }), decrypts the credential, and calls OpenAI APIs. There is no workspaceId check in this flow, so this is an IDOR.
Impact
- Cross-workspace unauthorized use of stored OpenAI keys. - Unauthorized read/modify/delete of victim vector stores and files. - Direct billing impact on victim OpenAI account. - Multi-tenant boundary violation with practical exploitability.
Reproduction steps
1. Set up two workspaces: A (attacker) and B (victim), each with an OpenAI credential. 2. Log in as a user in workspace A (with assistants-related permissions). 3. Call /api/v1/openai-assistants-vector-store and set credential to B’s credential ID. 4. Example: GET /api/v1/openai-assistants-vector-store?credential=<BcredentialId>. 5. If responses/actions are executed using B’s credential context, the issue is confirmed.
Other sources
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, Flowise openai-assistants-vector-store endpoints accept a client-controlled credential parameter and load credentials by id without checking whether that credential belongs to the caller workspace. Route permissions assistants: only check feature access. The controller passes req.query.credential straight to the service, and the service uses findOneBy({ id: credentialId }), decrypts the credential, and calls OpenAI APIs without a workspaceId check. If an attacker knows another workspace credentialId, the attacker can use that workspace OpenAI key, read, modify, or delete victim vector stores and files, cause billing impact on the victim OpenAI account, and violate multi-tenant boundaries. This issue is fixed in version 3.1.3.
— 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.3 - Upgrade
Upgrade
Flowise (openai-assistants-vector-store endpoints)to a version that resolves this vulnerability.Fixed in 3.1.3 - Configuration
Update the openai-assistants-vector-store endpoint(s) to check that the client-supplied credential/<credentialId> belongs to the caller’s workspace (add the missing workspaceId/ownership validation before loading the credential).
Flowise API route: /api/v1/openai-assistants-vector-store (and related openai-assistants-vector-store endpoints) credential parameter authorization/ownership check (workspaceId check) = enforce credentialId belongs to caller workspace
Event History
Frequently Asked Questions
What is the severity of CVE-2026-70472?
The severity of CVE-2026-70472 is rated at 60 on the risk scale.
How do I fix CVE-2026-70472?
To fix CVE-2026-70472, ensure that the server checks the ownership of the credential ID before allowing access.
What type of vulnerability is CVE-2026-70472?
CVE-2026-70472 is a cross-workspace credential IDOR vulnerability.
Who is affected by CVE-2026-70472?
CVE-2026-70472 affects users of the Flowise software that utilize the openai-assistants-vector-store.
Can an attacker exploit CVE-2026-70472 without credentials?
Yes, an attacker can exploit CVE-2026-70472 if they know another workspace’s credential ID.