CVE-2025-56520: Server-Side Request Forgery vulnerability in Dify v1.6.0
Dify
A server-side request forgery vulnerability was discovered in Dify version 1.6.0 via the remote file upload API component. The vulnerability has been published with a medium severity score and awaits patching information or exploitation confirmation.
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
- 5.3
- EPSS
- 0.01 · top 47% · 2026-11-13
- fix status
- Fix status unknown
- first report
- 30 Sep 2025
- last update
- 30 Sep 2025
- CVE ids
Timeline · 1
Sources · 1
Advisories and databases
- 2025-09-30CVE-2025-56520: Dify v1.6.0 was discovered to contain a Server-Side Request Forgery (SSRF) via the component…NVD · nvd.nist.gov/vuln/detail/CVE-2025-56520
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 30 Sep 2025 · first reported 30 Sep 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-56520: Server-Side Request Forgery vulnerability in Dify v1.6.0 https://gcdradar.vercel.app/incidents/cve-2025-56520-server-side-request-forgery-vulnerability-in · AIR-2025-0489 · closed 2025-09-30 - Lane: Patch now - Severity: 2 (Disclosed vulnerability) - Fix status: Fix status unknown - First reported: 2025-09-30 - AI role: Attack on AI - Products: Dify - CVE ids: CVE-2025-56520 - CVSS: 5.3 ## Summary A server-side request forgery vulnerability was discovered in Dify version 1.6.0 via the remote file upload API component. The vulnerability has been published with a medium severity score and awaits patching information or exploitation confirmation. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2025-09-30: CVE-2025-56520: Dify v1.6.0 was discovered to contain a Server-Side Request Forgery (SSRF) via the component… (https://nvd.nist.gov/vuln/detail/CVE-2025-56520) ## Sources - 2025-09-30 NVD: CVE-2025-56520: Dify v1.6.0 was discovered to contain a Server-Side Request Forgery (SSRF) via the component… https://nvd.nist.gov/vuln/detail/CVE-2025-56520 Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closed6.1Dify CVE-2025-58747: Cross-site scripting vulnerability in Dify MCP OAuth component
Patch now · Disclosed · since 17 Oct 2025 · CVE-2025-58747
AI - closed6.0Dify CVE-2025-59422: Broken access control vulnerability in Dify exposes chat messages
Patch now · Disclosed · since 25 Sep 2025 · CVE-2025-59422
AI - closed5.4Dify CVE-2026-21866: Stored XSS vulnerability in Dify chat rendering of Mermaid diagrams
Patch now · Disclosed · since 3 Mar 2026 · CVE-2026-21866
AI - closed5.5Dify CVE-2026-28288: Email enumeration vulnerability in Dify LLM development platform
Patch now · Disclosed · since 27 Feb 2026 · CVE-2026-28288
AI - closed6.1Dify CVE-2026-26023: Cross-site scripting vulnerability in Dify LLM platform
Patch now · Disclosed · since 11 Feb 2026 · CVE-2026-26023
AI - closed8.4Dify CVE-2025-67732: API Key Exposure Vulnerability in Dify
Patch now · Disclosed · since 5 Jan 2026 · CVE-2025-67732
AI