# CVE-2026-105762: Dify remote file upload server-side request forgery

Source: https://junglewise.ai/threats/cve-2026-105762-dify-is-an-open-source-llm-app-development-platform-prior-to-1  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-06. Updated: 2026-10-06  
License: CC BY 4.0 with a link back

CVE-2026-105762 · Severity: high · CVSS 8.3 · Published 2026-10-06

Dify is an open-source platform for building applications powered by language models. Prior to version 1.13.0, the file upload endpoint failed to validate user credentials and accepted attacker-controlled URLs, allowing remote attackers to trick the Dify server into making requests to internal services or cloud metadata endpoints. This could expose sensitive configuration data and enable network reconnaissance attacks.

Technologies: [Dify](https://junglewise.ai/threats/technologies/dify-dify). Vendors: [Dify](https://junglewise.ai/threats/vendors/dify).

## 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

## References

- [https://github.com/langgenius/dify/commit/2f87ecc0ce1d05ab3ef9537f29b84a5fa5823017](https://github.com/langgenius/dify/commit/2f87ecc0ce1d05ab3ef9537f29b84a5fa5823017)
- [https://github.com/langgenius/dify/pull/32236](https://github.com/langgenius/dify/pull/32236)

## Related threats

- [Dify SSRF bypass in remote file operations](https://junglewise.ai/threats/cve-2026-58141-dify-before-1-15-0-contains-a-server-side-request-forgery)
- [Dify is an open-source LLM app development platform. Prior to 1.13.1, the method `DELETE…](https://junglewise.ai/threats/cve-2026-34082-dify-is-an-open-source-llm-app-development-platform-prior-to-1-13)
- [Dify is an open-source LLM app development platform. Prior to version 1.11.0, the API key is exposed in plaintext to…](https://junglewise.ai/threats/cve-2025-67732-dify-is-an-open-source-llm-app-development-platform-prior-to)