dify - 💡(How to fix) Fix Follow up Security Issue [2 comments, 2 participants]

Self Checks

• I have read the Contributing Guide and Language Policy.
• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report, otherwise it will be closed.
• 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
• Please do not modify this template :) and fill in all the required fields.

Dify version

N/A

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

N/A

✔️ Expected Behavior

Hi maintainers,

I’m opening this public issue only to follow up on two private security reports I submitted through GitHub Security Advisories on March 30.

I haven’t received any response yet, so I wanted to kindly confirm whether the reports were received and whether they are currently being reviewed. I’m happy to provide additional information, testing notes, or PoC clarification in the private advisory threads.

For safety, I’m not including any technical vulnerability details in this public issue.

If GitHub Security Advisories is not the preferred reporting channel for this project, please let me know the correct security contact.

Thank you.

❌ Actual Behavior

N/A