Open Redirect in Dify AI Workflow OAuth Flow Exposes Sensitive Data (CVE‑2026‑XXXX)
What Happened — A medium‑severity open‑redirect flaw (CVSS 5.4) was discovered in Dify’s oauth_redirect_url handling. An attacker can craft a malicious link that, when visited, forces the OAuth flow to redirect to an attacker‑controlled site, allowing disclosure of information in the application’s context. The vendor has published a patch on GitHub.
Why It Matters for Compliance & Audit Readiness
- Open‑redirects bypass the trust boundaries that SOC 2 Access Control criteria (CC6.1, CC6.2) are designed to protect.
- The incident demonstrates the need for continuous monitoring of OAuth configurations and evidence that redirect URLs are whitelisted.
- Mapping this flaw to your SOC 2 control set provides audit‑ready proof that you remediate authentication‑related misconfigurations promptly.
Who Is Affected — SaaS providers and enterprises that embed Dify AI Workflow for internal or customer‑facing applications (primarily the technology/SaaS sector).
Recommended Actions
- Review all OAuth redirect URLs in your Dify deployments and enforce a strict whitelist.
- Apply the vendor‑supplied patch immediately; verify the fix with automated regression testing.
- Document the remediation in your SOC 2 access‑control evidence repository (e.g., change‑control tickets, configuration baselines).
Technical Notes — The vulnerability resides in the AppInitializer component’s OAuth flow. Exploitation requires user interaction (clicking a malicious link). CVE ID: ZDI‑26‑452 / ZDI‑CAN‑29196. CVSS 5.4 (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N). Patch: https://github.com/langgenius/dify/pull/38864. Source: Zero Day Initiative