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

> Attackers can read other users' chat messages in the same workspace by accessing an unprotected API endpoint, compromising data confidentiality.

- **Severity:** Medium 6.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:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2025
- **Updated:** 25 Sep 2025
- **Also known as:** GHSA-jg5j-c9pq-w894

## What is CVE-2025-59422?

CVE-2025-59422 is a medium-severity missing authorization vulnerability in langgenius dify, published on 25 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

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

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-59422?

It affects 1 product.


Products: Langgenius Dify.

## How do I fix CVE-2025-59422?

No fix has been published for CVE-2025-59422 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-59422 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59422 exists.

## Other vulnerabilities in langgenius dify

- [CVE-2025-56157](https://insights.sbomify.com/CVE-2025-56157/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2025-3466](https://insights.sbomify.com/CVE-2025-3466/): Unsanitized Input in langgenius/dify (critical 9.8)
- [CVE-2025-63386](https://insights.sbomify.com/CVE-2025-63386/): Misconfiguration in n/a (critical 9.1)
- [CVE-2025-63388](https://insights.sbomify.com/CVE-2025-63388/): Misconfiguration in n/a (critical 9.1)
- [CVE-2024-10252](https://insights.sbomify.com/CVE-2024-10252/): Code Injection in langgenius/dify (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59422 and fix it if it is affected.

What it is: CVE-2025-59422 is a medium-severity missing authorization vulnerability in langgenius dify, published on 25 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59422 exists.

Affected product: langgenius dify. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-59422/ (Markdown: https://insights.sbomify.com/CVE-2025-59422/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59422
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59422
- OSV: https://osv.dev/vulnerability/CVE-2025-59422

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-59422/
Summaries are generated and may contain mistakes; the official description above is the record.