Analysis and contextual insights are available on OpenCVE Cloud.
No solution or workaround provided in the CVE record.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 06 Nov 2026 16:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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/<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. | |
| Title | Dify < 1.15.0 SSRF Protection Bypass via Remote-Files Endpoints | |
| Weaknesses | CWE-918 | |
| References |
| |
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-11-06T16:43:46.844Z
Reserved: 2026-06-29T14:13:18.385Z
Link: CVE-2026-58141
No data.
Status : Received
Published: 2026-11-06T16:18:54.697
Modified: 2026-11-06T17:18:29.880
Link: CVE-2026-58141
No data.
OpenCVE Enrichment
No data.