Vulnerability report

Exploited in the wild High confidence Not in CISA KEV

CVE-2025-56520

Dify Server-Side Request Forgery

Dify

Severity
CVSS 5.3 · Medium
Confidence
High
Exploit status
Exploited in the wild
EPSS
0.7%
First observed
—
Last observed
—

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2025-56520 is an unauthenticated vulnerability affecting Dify. Dify v1.6.0 was discovered to contain a Server-Side Request Forgery (SSRF) via the component controllers.console.remote_files.RemoteFileUploadApi. A...

Is it exploited?

Yes. Previdian tracks this CVE as a known exploited vulnerability. Confidence is high. Also confirmed by third-party sources.

Who is affected?

Dify.

What should we do?

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Overview

Dify Server-Side Request Forgery

Dify v1.6.0 was discovered to contain a Server-Side Request Forgery (SSRF) via the component controllers.console.remote_files.RemoteFileUploadApi. A different vulnerability than CVE-2025-29720.

Published
30 Sep 2025
Exploitation Reported
05 Oct 2026
Attack vector
Remote
Complexity
Low
Privileges
None
User interaction
None

Tags

nuclei_scanner

CVE References

  • CVE Record CVE.org · CVE Record https://www.cve.org/CVERecord?id=CVE-2025-56520
  • GitHub — langgenius/dify github.com · CVE Record https://github.com/langgenius/dify/issues/22532

Exploitation evidence

Why Previdian marks this CVE as exploited

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploited in the wild

The Shadowserver

Recorded 05 Oct 2026

A trusted third party reported exploitation.

Proof of concept available

Nuclei Templates

Recorded 12 Jun 2026

Public scanner or PoC coverage increases practical exploitability.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
The Shadowserver First 2026-10-05 00:00 UTC

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets
User-Agents
Callback hosts
0
0
0

Request targets and User-Agents available in Pro. Callback host details available in Enterprise.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

Scanner Artifacts

Scanner and exploit-framework references linked to this CVE.

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

5.3 Medium

Potential damage if exploited. Separate from whether attackers are using it.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS

0.7%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

Potential Proof of Concepts

These PoCs are unverified and could contain malware. Use at your own risk.

Timeline

From disclosure to observed exploitation

  1. 00:00 UTC

    Added to Previdian KEV Feed

    High-confidence, third-party attested exploitation

  2. 14:21 UTC

    Public PoC available

    Public proof-of-concept code published

  3. 15:34 UTC

    Nuclei template available

    Scanner coverage available

  4. 00:00 UTC

    CVE published

    Vulnerability disclosed publicly

  5. 00:00 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2025-56520

Free JSON includes basic KEV fields
{
  "cve_id": "CVE-2025-56520",
  "confidence": "High",
  "cvss_score": 5.3,
  "cvss_estimated": false,
  "epss_score": 0.00696,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}