CVE-2026-58141 · AI agents & MCP
NO FIX YET · SEE WHAT TO DO
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.
first public Nov 6, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Self-hosted Dify deployments before 1.15.0 where a console account is held by anyone beyond trusted staff. The flaw comes from the Squid proxy lacking destination deny rules and from the request helper not validating destination IPs, so any deployment relying on network isolation for internal services is exposed. Managed hosting handled by the vendor is not described by the sources as affected.
Not affected if managed-hosting, no-console-users-beyond-trusted, version-1.15.0-or-later
Who cares aws, dify, postgresql, self-hosted
1.15.01.15.0 or laterDify 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.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
This page as .md · .json · 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.