Dify AI Platform Carried Multi-Tenant Flaws Exposing Private Chats and Internal APIs
Cross-tenant data leakage vulnerabilities in Dify's cloud service let attackers read other users' conversations, preview documents, and probe internal API endpoints.

Dify, the AI application framework reportedly underpinning roughly one million deployed apps, carried a set of multi-tenant isolation failures serious enough to expose private conversation data across tenant boundaries.
The attack surface breaks down into three distinct abuse paths. An authenticated attacker on the shared cloud service could read private chat histories belonging to other tenants, preview documents those tenants had uploaded, and reach internal API endpoints that should never be reachable from a peer tenant context. Each of those primitives is bad on its own. Combined, they describe a meaningful lateral-movement surface inside a shared AI infrastructure platform.
Multi-tenant isolation is foundational. When it fails in an AI platform, the blast radius expands fast — conversation logs often contain credentials, PII, and proprietary business logic that users have fed into prompts without thinking twice about who else might be on the same host.
At time of writing, specific CVE identifiers had not been publicly assigned, and Dify had not published a formal security advisory with patched-version strings. That absence is worth flagging. Defenders running self-hosted Dify deployments should monitor the project's official release channel for a patch notice; the cloud-hosted version's remediation timeline sits with the vendor.
The researcher or research team responsible for the discovery has not been publicly named in available disclosure materials, which limits independent verification of scope and severity.
Organizations with Dify integrations — particularly those using the multi-tenant cloud tier — should audit what data their applications are feeding into the platform. If conversation logs or document uploads contain sensitive material, that data was potentially reachable by co-tenants during the window these flaws were present.
Dify's popularity in the AI development ecosystem makes the patch cadence here worth watching closely.



