Disclosed weakness · no CVE recorded

Dify public retry events could expose hidden workflow prompts and execution details

Dify · Dify · Web App and Explore workflow streams

First documented disclosure · Review checkpoint

Summary

A workflow retry could send prompts and model details to the browser even when run details were hidden.

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.

Exploitation evidence source

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

Public stream converters redacted start and finish events but serialized node-retry details in full.

Conditions required

A published chatflow or workflow retries a node whose failed result contains sensitive process data.

Potential impact

The browser could receive prompts, model information and other execution details intended to be omitted from the public stream.

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 to 1.20.0; treat frontend visibility settings as insufficient protection for older public retry streams.

Operating lesson

Enforce redaction at every event serializer, including failure and retry paths.

Evidence and limits

The original report demonstrates the response-conversion boundary and does not claim a deployment-specific reproduction. Debugger, Service API and OpenAPI responses are deliberately outside the redaction change. Tagged verification: public node-retry events use the detail-removal serializer.

Sources