Quick answers
- Is CVE-2026-105762 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105762 being exploited in the wild.
- How severe is CVE-2026-105762?
- High severity, with a CVSS score of 8.3, published 6 October 2026.
- Which products and versions are affected?
- Dify before 1.13.0.
- Is there a fix for CVE-2026-105762?
- Yes: fixed in 1.13.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105762 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-105762?
- Check whether you run Dify at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.13.0
Technical details
The /console/api/remote-files/upload endpoint in remote_files.py accepted attacker-supplied URLs without authentication, causing the server to fetch content from arbitrary sources. This is a server-side request forgery (SSRF) vulnerability exploitable via network requests with no authentication required. An attacker can use the vulnerable server to enumerate internal services, access cloud metadata (AWS/GCP/Azure), or pivot through the network to compromise backend systems.
Affected products
- Dify Dify before 1.13.0
Timeline
- 2026-10-06: disclosed
- 2026-02-11: patched