Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-105762 – Unauthenticated SSRF – Dify prior to 1.13.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-105762 is an unauthenticated Server-Side Request Forgery (SSRF) vulnerability in Dify, the open-source LLM application development platform by LangGenius. The flaw resides in the /console/api/remote-files/upload endpoint, which fetches attacker-supplied URLs on the server’s behalf without any authentication or destination validation. The issue carries a CVSS v3.1 base score of 8.3 (High) and affects all Dify deployments running a version prior to 1.13.0.

Technical details

  • Root cause: The remote file upload handler (api/controllers/web/remote_files.py) accepts a user-controlled url parameter and issues an outbound HTTP request to it without validating or restricting the destination (no allowlist/denylist for internal or reserved IP ranges).
  • Trigger conditions: An attacker sends an unauthenticated HTTP POST request to /console/api/remote-files/upload with a url field pointing at an internal, loopback, or cloud metadata address.
  • Attack vector: Network-based (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N). The vulnerability has a scope change (S:C), meaning the impact can extend beyond the vulnerable component itself.
  • Impact: The server can be coerced into making requests to internal-only services, cloud instance metadata endpoints (e.g., AWS/GCP metadata services), or other network-restricted resources, potentially disclosing sensitive internal data, credentials, or facilitating further lateral movement/reconnaissance within the hosting environment.

Affected software

  • Dify (langgenius/dify) — all versions prior to 1.13.0

Severity

  • CVSS v3.1 Base Score: 8.3 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L

Mitigation and recommended actions

  • Immediate: Upgrade Dify to version 1.13.0 or later, which fixes the issue (addressed via PR #32236 / commit 2f87ecc0ce1d05ab3ef9537f29b84a5fa5823017).
  • If immediate patching is not possible:
    • Restrict or disable public access to the /console/api/remote-files/upload endpoint at the network/reverse-proxy layer until patched.
    • Deploy egress filtering/firewall rules on the Dify host to block outbound requests to loopback, link-local, and private IP ranges (including 169.254.169.254 cloud metadata addresses and RFC1918 ranges).
    • Disable or restrict access to cloud instance metadata services (e.g., require IMDSv2 on AWS) to reduce the blast radius of SSRF-based credential theft.
    • Monitor outbound request logs from the Dify server for anomalous destinations.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge