CVE-2026-67622

CVE-2026-67622 is an IDOR in Flowise that allows cross-workspace credential access, and the headline CVSS score almost certainly understates the real risk. The vulnerability exists because credential lookup resolves against a global UUID namespace rather than a workspace-relative one — when the Assistants endpoint requests credentials by UUID, it receives any credential in the system, not just ones belonging to the requesting workspace. The critical insight most teams will miss: this is not a bug in the Assistants endpoint alone. The credential resolution logic is shared across every integration in Flowise — Slack webhooks, HTTP endpoints, database connectors, vector stores. If you patch only the Assistants endpoint, you leave the same IDOR live in every other integration path. An attacker who understands this pattern (and CVE publications teach exactly that) will pivot to enumerating those other vectors while defenders are busy patching the reported endpoint. This is the documented recidivism pattern in multi-endpoint IDOR disclosures — the CVE becomes a roadmap for attackers. The severity compounds because credentials in Flowise aren't merely readable — they're implicitly trusted for write actions, including file uploads into target workspaces. This crosses from data disclosure into execution territory, which changes your compliance analysis (GDPR Article 32, SOC 2 CC6). More critically: the credential grants access to external systems. That Slack webhook token, database connection string, or HTTP API key you retrieve doesn't just live in Flowise — it gates everything those integrations touch. The CVSS blast radius stops at Flowise's boundary; the actual blast radius does not. For immediate action: inventory every integration endpoint in your Flowise deployment and verify they all enforce workspace-bounded credential resolution, not just the Assistants endpoint. Assume the vulnerability exists in all of them until proven otherwise. Prioritize patching the integration pathways that connect to external systems (Slack, HTTP, databases) — those are where the credential becomes a key to your broader infrastructure. If you're on a multi-tenant SaaS deployment, treat this as a cross-tenant breach vector. If self-hosted, treat it as an insider-grade threat where a compromised account can enumerate and weaponize credentials from other workspaces in the same deployment. The deeper fix requires making credential resolution workspace-aware at the lookup layer, not just adding endpoint-level checks. Endpoint-level patches will be inconsistently applied and will miss new integrations added over time.

Reviewed through automated stages and approved by a human before publication.