# CVE-2026-58141: Dify < 1.15.0 SSRF Protection Bypass via Remote-Files Endpoints

Status: published. Published: 2026-11-06. Updated: 2026-11-06.

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/<url>, 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.

## Remediation

- fix: The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches. (source: CNA: VulnCheck) — https://github.com/langgenius/dify/pull/36332
- fix: The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches. (source: CNA: VulnCheck) — https://github.com/langgenius/dify/commit/7bfcf9185c75bb18f0b44335080524e659f087d9

## Affected products and versions

- langgenius / dify (langgenius/dify): ≥ 0.6.0; < 1.15.0 (affected, semver). Source: CNA: VulnCheck

## Severity and prioritization

- CVSS 4.0: 7.2 (high); 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; source: CNA: VulnCheck

- CVSS 3.1: 7.6 (high); CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L; source: CNA: VulnCheck

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: exploitation none; automatable yes; technical impact partial; source ADP: CISA-ADP

- Weaknesses: CWE-918

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://github.com/langgenius/dify/releases/tag/1.15.0 (CNA: VulnCheck; release-notes)

- https://github.com/langgenius/dify/pull/36332 (CNA: VulnCheck; issue-tracking, patch)

- https://github.com/langgenius/dify/commit/7bfcf9185c75bb18f0b44335080524e659f087d9 (CNA: VulnCheck; patch)

- https://www.vulncheck.com/advisories/dify-ssrf-protection-bypass-via-remote-files-endpoints (CNA: VulnCheck; third-party-advisory)

## Provenance

- CNA: VulnCheck: https://www.cve.org/CVERecord?id=CVE-2026-58141; retrieved 2026-11-06; source updated 2026-11-06

Revision: cbeeb5ad0cd5fd5675dae9a126d2b0fe3b2f0f9e933ea18d1f0f4fbbbbf0c7ef

Canonical: https://y2.dev/cve/CVE-2026-58141

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.