Disclosed weakness · no CVE recorded
Dify file previews could serve active content without a consistent isolation policy
Dify · Dify · file delivery and previews
First documented disclosure · Review checkpoint
Summary
Several file delivery routes handled SVG, XML and missing MIME metadata without a consistent browser isolation policy.
Severity and exploitation evidence
No CVSS score recorded in this review.
Exploitation not established: The reviewed sources describe a correction or controlled reproduction; malicious exploitation against users is not established.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
Inline active content and MIME handling differed across uploaded files, tool files, workspace logos and API previews.
Conditions required
A user opens attacker-influenced file content through an affected delivery route.
Potential impact
Active file content could execute in a browser context without the isolation now applied by the correction; the public report withholds exploit details.
Affected versions and configurations
The reviewed upstream report does not establish a complete affected-release range.
Fix and mitigation status
1.20.0 contains the correction.
Practical next steps
Upgrade the matching Dify components to 1.20.0 and apply the documented file-preview policy.
Operating lesson
Treat file preview responses as a browser security boundary.
Evidence and limits
The PR intentionally omits the original private report. Local browser checks in the report show blocked scripts and same-origin storage access after the fix. Tagged verification: inline SVG receives a sandbox policy and other active or untyped content is forced to download.
Sources
- fix(api): harden file previews and signed URL renewal
Primary source ·
- 1.20.0 release notes
Primary source ·
- Dify 1.20.0 file response policy
Primary source ·