CVE-2025-0184 json
Server-Side Request Forgery (SSRF) in langgenius/dify
published last yr. modified 4mo ago also EUVD-2025-6834
- cvss
- 6.5
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 44%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Is CVE-2025-0184 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.51% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- huntr.com https://huntr.com/bounties/a7eac4ae-5d5e-4ac1-894b-7a8cce5cba9b referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected products
- langgenius langgenius/dify
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
github.com
/langgenius/dify/commit/c135ec4b08d946a1a1d3a198a1d72c1ccf47250f
patch
-
huntr.com
/bounties/a7eac4ae-5d5e-4ac1-894b-7a8cce5cba9b
exploit, third-party-advisory
Sources
- CVE List CVE-2025-0184
- NVD CVE-2025-0184
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.