INCIDENT MAP

Browse / AI Framework and Platform Flaws / CVE-2026-70472

Flowise: Cross-workspace credential IDOR in openai-assistants-vector-store

CVE-2026-70472 · 2026-08-04 high

Class
AI Framework and Platform Flaws (filed by a model that read the advisory)
Technique
Authentication and access control
Affected
flowise (npm)
Gets past
Authorisation check
CVSS
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:H/SA:H
EPSS
0.5% chance of exploitation in 30 days

How it works, in short

A client-supplied credential ID is used without checking that it belongs to the caller's workspace, letting one tenant use another tenant's OpenAI key. (Our summary, written by a model. The source text is below.)

Details

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

Reproduction steps

References

Source: GitHub Advisory Database, used under CC BY 4.0.