CVE-2025-29720: Server-Side Request Forgery vulnerability in Dify
Dify
Dify contains a Server-Side Request Forgery vulnerability via its remote files API component. The vulnerability has been publicly disclosed with a medium severity rating.
disclosed CVENo confirmed exploitation, so this record is tracked as a disclosed vulnerability and not counted as an incident. It moves into the counts if CISA or the vendor confirms exploitation. Why
- CVSS
- 4.8
- EPSS
- <0.01 · top 94% · 2026-11-13
- fix status
- Fix status unknown
- first report
- 14 Apr 2025
- last update
- 14 Apr 2025
- CVE ids
Timeline · 1
Sources · 1
Advisories and databases
- 2025-04-14CVE-2025-29720: Dify v1.0 was discovered to contain a Server-Side Request Forgery (SSRF) via the component…NVD · nvd.nist.gov/vuln/detail/CVE-2025-29720
Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.
Classification
- lane
- Patch now
- AI role
- Attack on AI
- categories
- Infrastructure vulnerability
- severity
- 2 · Disclosed vulnerability
- fix status
- Fix status unknown
- targets
- Framework / tooling
- owasp llm top 10
- LLM03:2025 Supply Chain
- mitre atlas
- no technique for these categories
- tags
- ssrf
- dates
- happened 14 Apr 2025 · first reported 14 Apr 2025
- origin
- NVDVulnerability record from NVD / the GitHub Advisory Database. This product uses the NVD API but is not endorsed or certified by the NVD.
- record
- confidence 0.95 · created 2026-10-18 10:04Z · updated 2026-10-18 10:04Z
Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned
Copy a brief
This record as a short Markdown brief, for a ticket, a chat or a coding agent.
the brief as text
# CVE-2025-29720: Server-Side Request Forgery vulnerability in Dify https://gcdradar.vercel.app/incidents/cve-2025-29720-server-side-request-forgery-vulnerability-in · AIR-2025-0413 · closed 2025-04-14 - Lane: Patch now - Severity: 2 (Disclosed vulnerability) - Fix status: Fix status unknown - First reported: 2025-04-14 - AI role: Attack on AI - Products: Dify - CVE ids: CVE-2025-29720 - CVSS: 4.8 ## Summary Dify contains a Server-Side Request Forgery vulnerability via its remote files API component. The vulnerability has been publicly disclosed with a medium severity rating. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2025-04-14: CVE-2025-29720: Dify v1.0 was discovered to contain a Server-Side Request Forgery (SSRF) via the component… (https://nvd.nist.gov/vuln/detail/CVE-2025-29720) ## Sources - 2025-04-14 NVD: CVE-2025-29720: Dify v1.0 was discovered to contain a Server-Side Request Forgery (SSRF) via the component… https://nvd.nist.gov/vuln/detail/CVE-2025-29720 Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closed6.1Dify CVE-2025-43854: Clickjacking Vulnerability in Dify Platform
Patch now · Disclosed · since 28 Apr 2025 · CVE-2025-43854
AI - closed7.6Dify CVE-2025-43862: Access Control Flaw in Dify LLM Platform
Patch now · Disclosed · since 25 Apr 2025 · CVE-2025-43862
AI - closed6.3Dify CVE-2025-32790: Unauthorized App DSL Export Vulnerability in Dify
Patch now · Disclosed · since 18 Apr 2025 · CVE-2025-32790
AI - closed6.5Dify CVE-2025-32796: Access Control Flaw in Dify LLM App Platform
Patch now · Disclosed · since 18 Apr 2025 · CVE-2025-32796
AI - closed6.5Dify CVE-2025-32795: Authorization bypass vulnerability in Dify app management
Patch now · Disclosed · since 18 Apr 2025 · CVE-2025-32795
AI - closed8.8Dify CVE-2024-10252: Code injection vulnerability in Dify sandbox service
Patch now · Disclosed · since 20 Mar 2025 · CVE-2024-10252
AI