Cpe:2.3:a:dify:dify:*:*:*:*:*:*:*:* - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/cpes/cpe2.3adifydify/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioFri, 06 Nov 2026 17:26:35 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgDify: Server-side request forgery (CVE-2026-58141)https://feed.craftedsignal.io/briefs/2026-11-dify-ssrf/Fri, 06 Nov 2026 17:26:35 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-11-dify-ssrf/Dify versions prior to 1.15.0 contain a server-side request forgery (SSRF) vulnerability allowing authenticated users to access internal network services and cloud metadata via misconfigured proxy settings.Dify versions prior to 1.15.0 contain a server-side request forgery (SSRF) vulnerability that permits authenticated console users to bypass security protections. The vulnerability stems from a Squid proxy configuration that lacks destination deny rules and a make_request() helper function that fails to perform independent destination IP validation.

Impact

Authenticated attackers can reach internal infrastructure, including sandbox environments, internal APIs, and PostgreSQL databases. On AWS deployments, attackers may leverage this flaw to access the instance metadata service to retrieve IAM credentials. The HTTP Request workflow node further enables unauthorized POST, PUT, and DELETE operations against internal services that rely on network isolation for authorization.

Recommendation

  • Upgrade Dify to version 1.15.0 or later immediately to apply the patch for CVE-2026-58141.
  • Audit application logs for abnormal outbound requests originating from the Dify backend.
  • Implement stricter network segmentation (egress filtering) for the Dify environment to prevent internal network scanning and unauthorized access to cloud metadata services.
]]>highadvisory