CVE-2025-59422: langgenius dify · Improper Access Control
Affects langgenius difySource CVE Database V5
Not known to be exploited · CVSS 6.0 Medium · fixed in 1.9.0 : update langgenius dify when convenient.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.9.0
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| langgenius dify | Affected
| Fixed in– |
AI-suggested
European organizations should immediately upgrade Dify installations from version 1.8.1 to version 1.9.0 or later, where the access control issue has been fixed. Until the upgrade is applied, organizations should restrict user access to the affected API endpoints by implementing additional access control checks at the network or application firewall level, limiting API access to trusted users only. Monitoring and logging access to chat message APIs should be enhanced to detect any unauthorized access attempts. Organizations should also review workspace membership and permissions to minimize the number of users with access to sensitive conversations. Conducting an internal audit of chat data exposure and informing affected users may be necessary to comply with GDPR breach notification requirements. Finally, developers using Dify should follow secure coding practices to validate access rights rigorously and consider implementing rate limiting and anomaly detection on API endpoints to prevent exploitation.
Description
Dify is an open-source LLM app development platform. In version 1.8.1, a broken access control vulnerability on the /console/api/apps/<APP_ID>chat-messages?conversation_id=<CONVERSATION_ID>&limit=10 endpoint allows users in the same workspace to read chat messages of other users. A regular user is able to read the query data and the filename of the admins and probably other users chats, if they know the conversation_id. This impacts the confidentiality of chats. This issue has been patched in version 1.9.0.