---
id: "CVE-2026-58141"
page: "https://infrastack.ai/live/CVE-2026-58141"
kind: "vulnerability"
aliases: ["CVE-2026-58141"]
title: "Dify: any console user can reach internal services and cloud metadata"
severity: "high"
cvss: 7.6
epss: null
exploited: false
status: "open"
category: "ai-tooling"
products: []
ecosystems: []
tags: ["ai-tooling", "aws", "dify", "postgresql", "self-hosted"]
not_affected_if: ["managed-hosting", "no-console-users-beyond-trusted", "version-1.15.0-or-later"]
published_at: "2026-11-06T16:18:54+00:00"
first_seen_at: "2026-11-06T16:42:41+00:00"
updated_at: "2026-11-06T16:44:40+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-58141", "first_seen_at": "2026-11-06T16:42:41+00:00"}]
exploit_sources: []
---

# Dify: any console user can reach internal services and cloud metadata

Link for people: https://infrastack.ai/live/CVE-2026-58141 (this .md is for agents)

Dify before 1.15.0 lets any logged-in console user send arbitrary HTTP requests from the server through remote file, upload, and HTTP Request workflow endpoints, bypassing its SSRF protections. An attacker can reach internal services, PostgreSQL, the sandbox, and on AWS read IAM credentials from the instance metadata service.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the Dify version in use; affected if below `1.15.0`
- Review whether the console is reachable by users who are not fully trusted
- On AWS, check whether instances allow IMDS access from the Dify containers

## Fix

- Dify: upgrade to `1.15.0` or later

## Timeline

- 2026-11-06T16:42:41+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-58141

## Documents

- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/dify-ssrf-protection-bypass-via-remote-files-endpoints
- [fix] Patch: github.com https://github.com/langgenius/dify/commit/7bfcf9185c75bb18f0b44335080524e659f087d9
- [fix] Release notes: github.com https://github.com/langgenius/dify/releases/tag/1.15.0

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_