langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-20 19:50:06 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Users should not be able to access other users' conversation history #13137

New Issue
Open
opened 2026-02-21 19:10:43 -05:00 by yindo · 12 comments
yindo commented 2026-02-21 19:10:43 -05:00
Owner
Copy Link
Copy Source

Originally created by @fdb02983rhy on GitHub (Apr 19, 2025).

Self Checks

  • 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 (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.2.0 main brach 2025.04.19

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  1. Use a custom sys.user_id to start a conversation via a shared app.
  2. Open the same app in incognito mode and use the same sys.user_id.

✔️ Expected Behavior

In incognito mode, even use the same sys.user_id, user should not be able to access existing conversation history

❌ Actual Behavior

In incognito mode, user can access conversation history by an existing sys.user_id

Originally created by @fdb02983rhy on GitHub (Apr 19, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.2.0 main brach 2025.04.19 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 1. Use a custom sys.user_id to start a conversation via a shared app. 2. Open the same app in incognito mode and use the same sys.user_id. ### ✔️ Expected Behavior In incognito mode, even use the same sys.user_id, user should not be able to access existing conversation history ### ❌ Actual Behavior In incognito mode, user can access conversation history by an existing sys.user_id
yindo added the 🐞 bug label 2026-02-21 19:10:43 -05:00
yindo commented 2026-02-21 19:10:44 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Apr 19, 2025):

I wasn't able to find specific information on how Dify prevents unauthorized access to conversation history or how it handles session management and user data isolation in incognito mode. However, the sys.user_id is used to uniquely identify users within the platform, which is crucial for managing user sessions and controlling access to data specific to each user [1][2].

To address the issue you're experiencing, it might be necessary to review how sys.user_id is being managed in your implementation, especially in incognito mode, to ensure that it doesn't inadvertently allow access to other users' data. You may want to consider implementing additional checks or mechanisms to isolate session data more effectively in incognito mode.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Apr 19, 2025): <!-- Answer --> I wasn't able to find specific information on how Dify prevents unauthorized access to conversation history or how it handles session management and user data isolation in incognito mode. However, the `sys.user_id` is used to uniquely identify users within the platform, which is crucial for managing user sessions and controlling access to data specific to each user <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/guides/workflow/node/start.md)</sup><sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/guides/workflow/variables.md)</sup>. To address the issue you're experiencing, it might be necessary to review how `sys.user_id` is being managed in your implementation, especially in incognito mode, to ensure that it doesn't inadvertently allow access to other users' data. You may want to consider implementing additional checks or mechanisms to isolate session data more effectively in incognito mode. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/38adf8a6-31eb-4b38-8a09-556d11e238e1?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/38adf8a6-31eb-4b38-8a09-556d11e238e1?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/38adf8a6-31eb-4b38-8a09-556d11e238e1?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/38adf8a6-31eb-4b38-8a09-556d11e238e1?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/38adf8a6-31eb-4b38-8a09-556d11e238e1?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/38adf8a6-31eb-4b38-8a09-556d11e238e1?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/38adf8a6-31eb-4b38-8a09-556d11e238e1?feedback_type=other)</sup>
yindo commented 2026-02-21 19:10:44 -05:00
Author
Owner
Copy Link
Copy Source

@fdb02983rhy commented on GitHub (Apr 19, 2025):

For anyone who would like to use this functionality, I strongly recommend adding encryption and decryption (like cryptography) to the original user ID until this issue is fixed.

@fdb02983rhy commented on GitHub (Apr 19, 2025): For anyone who would like to use this functionality, I strongly recommend adding encryption and decryption (like cryptography) to the original user ID until this issue is fixed.
yindo commented 2026-02-21 19:10:44 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 22, 2025):

Hi, @fdb02983rhy. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported a security issue in version 1.2.0 (self-hosted Docker) where using the same sys.user_id in incognito mode allows access to another user's conversation history.
  • This behavior indicates a lack of proper session isolation in incognito mode.
  • A contributor suggested reviewing sys.user_id management and recommended encryption/decryption of the user ID as a temporary workaround.
  • No official fix or update has been provided yet to address this issue.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open.
  • If I do not hear back within 15 days, I will automatically close this issue.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Aug 22, 2025): Hi, @fdb02983rhy. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported a security issue in version 1.2.0 (self-hosted Docker) where using the same sys.user_id in incognito mode allows access to another user's conversation history. - This behavior indicates a lack of proper session isolation in incognito mode. - A contributor suggested reviewing sys.user_id management and recommended encryption/decryption of the user ID as a temporary workaround. - No official fix or update has been provided yet to address this issue. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open. - If I do not hear back within 15 days, I will automatically close this issue. Thank you for your understanding and contribution!
yindo commented 2026-02-21 19:10:44 -05:00
Author
Owner
Copy Link
Copy Source

@fdb02983rhy commented on GitHub (Aug 26, 2025):

Hi, @fdb02983rhy. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported a security issue in version 1.2.0 (self-hosted Docker) where using the same sys.user_id in incognito mode allows access to another user's conversation history.
  • This behavior indicates a lack of proper session isolation in incognito mode.
  • A contributor suggested reviewing sys.user_id management and recommended encryption/decryption of the user ID as a temporary workaround.
  • No official fix or update has been provided yet to address this issue.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open.
  • If I do not hear back within 15 days, I will automatically close this issue.

Thank you for your understanding and contribution!

Yep

@fdb02983rhy commented on GitHub (Aug 26, 2025): > Hi, [@fdb02983rhy](https://github.com/fdb02983rhy). I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. > > **Issue Summary:** > > * You reported a security issue in version 1.2.0 (self-hosted Docker) where using the same sys.user_id in incognito mode allows access to another user's conversation history. > * This behavior indicates a lack of proper session isolation in incognito mode. > * A contributor suggested reviewing sys.user_id management and recommended encryption/decryption of the user ID as a temporary workaround. > * No official fix or update has been provided yet to address this issue. > > **Next Steps:** > > * Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open. > * If I do not hear back within 15 days, I will automatically close this issue. > > Thank you for your understanding and contribution! Yep
yindo commented 2026-02-21 19:10:44 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 26, 2025):

Hi, @fdb02983rhy. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported a security issue in Dify v1.2.0 (self-hosted Docker) where using the same sys.user_id in incognito mode allows access to another user's conversation history.
  • This indicates insufficient session isolation between users sharing the same user ID.
  • A contributor suggested reviewing sys.user_id management and encrypting the user ID as a temporary workaround.
  • No official fix has been implemented yet.
  • You confirmed the issue is still present.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open.
  • Otherwise, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Sep 26, 2025): Hi, @fdb02983rhy. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported a security issue in Dify v1.2.0 (self-hosted Docker) where using the same sys.user_id in incognito mode allows access to another user's conversation history. - This indicates insufficient session isolation between users sharing the same user ID. - A contributor suggested reviewing sys.user_id management and encrypting the user ID as a temporary workaround. - No official fix has been implemented yet. - You confirmed the issue is still present. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open. - Otherwise, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
yindo commented 2026-02-21 19:10:44 -05:00
Author
Owner
Copy Link
Copy Source

@fdb02983rhy commented on GitHub (Sep 26, 2025):

Hi, @fdb02983rhy. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported a security issue in Dify v1.2.0 (self-hosted Docker) where using the same sys.user_id in incognito mode allows access to another user's conversation history.
  • This indicates insufficient session isolation between users sharing the same user ID.
  • A contributor suggested reviewing sys.user_id management and encrypting the user ID as a temporary workaround.
  • No official fix has been implemented yet.
  • You confirmed the issue is still present.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open.
  • Otherwise, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

Yes

@fdb02983rhy commented on GitHub (Sep 26, 2025): > Hi, [@fdb02983rhy](https://github.com/fdb02983rhy). I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. > > **Issue Summary:** > > * You reported a security issue in Dify v1.2.0 (self-hosted Docker) where using the same sys.user_id in incognito mode allows access to another user's conversation history. > * This indicates insufficient session isolation between users sharing the same user ID. > * A contributor suggested reviewing sys.user_id management and encrypting the user ID as a temporary workaround. > * No official fix has been implemented yet. > * You confirmed the issue is still present. > > **Next Steps:** > > * Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open. > * Otherwise, this issue will be automatically closed in 15 days. > > Thank you for your understanding and contribution! Yes
yindo commented 2026-02-21 19:10:44 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 4, 2025):

Hi, @fdb02983rhy. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported a security issue in Dify v1.2.0 (self-hosted Docker) where using the same sys.user_id in incognito mode allows access to another user's conversation history.
  • This indicates insufficient session isolation related to sys.user_id management.
  • A contributor suggested reviewing user ID handling and encrypting the user ID as a temporary workaround.
  • Despite follow-ups, you confirmed the issue remains unresolved with no official fix yet.
  • The issue is currently marked as stale pending further updates from you.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open.
  • Otherwise, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Nov 4, 2025): Hi, @fdb02983rhy. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported a security issue in Dify v1.2.0 (self-hosted Docker) where using the same sys.user_id in incognito mode allows access to another user's conversation history. - This indicates insufficient session isolation related to sys.user_id management. - A contributor suggested reviewing user ID handling and encrypting the user ID as a temporary workaround. - Despite follow-ups, you confirmed the issue remains unresolved with no official fix yet. - The issue is currently marked as stale pending further updates from you. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open. - Otherwise, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
yindo commented 2026-02-21 19:10:44 -05:00
Author
Owner
Copy Link
Copy Source

@fdb02983rhy commented on GitHub (Nov 4, 2025):

Hi, @fdb02983rhy. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported a security issue in Dify v1.2.0 (self-hosted Docker) where using the same sys.user_id in incognito mode allows access to another user's conversation history.
  • This indicates insufficient session isolation related to sys.user_id management.
  • A contributor suggested reviewing user ID handling and encrypting the user ID as a temporary workaround.
  • Despite follow-ups, you confirmed the issue remains unresolved with no official fix yet.
  • The issue is currently marked as stale pending further updates from you.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open.
  • Otherwise, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

Yes

@fdb02983rhy commented on GitHub (Nov 4, 2025): > Hi, [@fdb02983rhy](https://github.com/fdb02983rhy). I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. > > **Issue Summary:** > > * You reported a security issue in Dify v1.2.0 (self-hosted Docker) where using the same sys.user_id in incognito mode allows access to another user's conversation history. > * This indicates insufficient session isolation related to sys.user_id management. > * A contributor suggested reviewing user ID handling and encrypting the user ID as a temporary workaround. > * Despite follow-ups, you confirmed the issue remains unresolved with no official fix yet. > * The issue is currently marked as stale pending further updates from you. > > **Next Steps:** > > * Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open. > * Otherwise, this issue will be automatically closed in 15 days. > > Thank you for your understanding and contribution! Yes
yindo commented 2026-02-21 19:10:44 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 31, 2025):

Hi, @fdb02983rhy. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported a security issue in Dify v1.2.0 (self-hosted Docker) where using the same sys.user_id in incognito mode grants access to another user's conversation history.
  • This indicates insufficient session isolation and a potential vulnerability in user session management.
  • A contributor suggested reviewing sys.user_id handling and encrypting the user ID as a temporary workaround.
  • Despite my follow-ups, no official fix has been implemented yet.
  • You have confirmed the issue remains relevant.

Next Steps:

  • Please let me know if this issue is still affecting the latest version of Dify by commenting here to keep the discussion open.
  • If I do not hear back within 15 days, this issue will be automatically closed.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Dec 31, 2025): Hi, @fdb02983rhy. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported a security issue in Dify v1.2.0 (self-hosted Docker) where using the same sys.user_id in incognito mode grants access to another user's conversation history. - This indicates insufficient session isolation and a potential vulnerability in user session management. - A contributor suggested reviewing sys.user_id handling and encrypting the user ID as a temporary workaround. - Despite my follow-ups, no official fix has been implemented yet. - You have confirmed the issue remains relevant. **Next Steps:** - Please let me know if this issue is still affecting the latest version of Dify by commenting here to keep the discussion open. - If I do not hear back within 15 days, this issue will be automatically closed. Thank you for your understanding and contribution!
yindo commented 2026-02-21 19:10:44 -05:00
Author
Owner
Copy Link
Copy Source

@fdb02983rhy commented on GitHub (Dec 31, 2025):

Hi, @fdb02983rhy. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported a security issue in Dify v1.2.0 (self-hosted Docker) where using the same sys.user_id in incognito mode grants access to another user's conversation history.
  • This indicates insufficient session isolation and a potential vulnerability in user session management.
  • A contributor suggested reviewing sys.user_id handling and encrypting the user ID as a temporary workaround.
  • Despite my follow-ups, no official fix has been implemented yet.
  • You have confirmed the issue remains relevant.

Next Steps:

  • Please let me know if this issue is still affecting the latest version of Dify by commenting here to keep the discussion open.
  • If I do not hear back within 15 days, this issue will be automatically closed.

Thank you for your understanding and contribution!

yes

@fdb02983rhy commented on GitHub (Dec 31, 2025): > Hi, [@fdb02983rhy](https://github.com/fdb02983rhy). I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. > > **Issue Summary:** > > * You reported a security issue in Dify v1.2.0 (self-hosted Docker) where using the same sys.user_id in incognito mode grants access to another user's conversation history. > * This indicates insufficient session isolation and a potential vulnerability in user session management. > * A contributor suggested reviewing sys.user_id handling and encrypting the user ID as a temporary workaround. > * Despite my follow-ups, no official fix has been implemented yet. > * You have confirmed the issue remains relevant. > > **Next Steps:** > > * Please let me know if this issue is still affecting the latest version of Dify by commenting here to keep the discussion open. > * If I do not hear back within 15 days, this issue will be automatically closed. > > Thank you for your understanding and contribution! yes
yindo commented 2026-02-21 19:10:44 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 31, 2026):

Hi, @fdb02983rhy. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported a security concern in Dify v1.2.0 (self-hosted Docker) where using the same sys.user_id in incognito mode grants access to existing conversation history, breaking session isolation.
  • A contributor suggested reviewing sys.user_id handling and encrypting the user ID as a temporary workaround.
  • You have confirmed multiple times that the issue persists without an official fix.
  • The issue has been inactive recently and is now marked as stale.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open.
  • If I do not hear back within 15 days, the issue will be automatically closed.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Jan 31, 2026): Hi, @fdb02983rhy. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported a security concern in Dify v1.2.0 (self-hosted Docker) where using the same sys.user_id in incognito mode grants access to existing conversation history, breaking session isolation. - A contributor suggested reviewing sys.user_id handling and encrypting the user ID as a temporary workaround. - You have confirmed multiple times that the issue persists without an official fix. - The issue has been inactive recently and is now marked as stale. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open. - If I do not hear back within 15 days, the issue will be automatically closed. Thank you for your understanding and contribution!
yindo commented 2026-02-21 19:10:44 -05:00
Author
Owner
Copy Link
Copy Source

@fdb02983rhy commented on GitHub (Jan 31, 2026):

yes

@fdb02983rhy commented on GitHub (Jan 31, 2026): yes
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#13137
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?