Read the docs

Zulip exports with member consent leak deleted users' direct messages

Priority LOW 38CWE-359Published · Updated

Key facts

Attack vector
Network
Privileges required
High
User interaction
None
Attack complexity
Low
Impact type
Information disclosure
Confidentiality · integrity · availability
High · None · None
Fix status
Fixed

Attack profile from CVSS 3.1 · GHSA-m2g9-5v7r-xqcg. Fix status from GitHub. Impact type from CWE-359.

Summary

Zulip Server from 11.0 through 12.3 and version 13.0-rc1 are affected. An organization export with member consent treats deleted users as consenting, so it includes direct messages from conversations they took part in, including messages written by other participants who did not consent (CWE-359). An administrator can obtain these messages, and only organizations with at least one deleted user are affected.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Description from the GitHub advisory

### Summary An organization export of public and private data with member consent treated every deleted user as having consented to the export of their private data. As a result, the export included direct messages from conversations that a deleted user had been part of, including messages written by other participants who had not consented. Severity is limited: creating such an export requires administrator permissions, and only conversations involving a deleted user are affected. User deletion isn't available in the Zulip apps: on self-hosted servers, it requires running the `manage.py delete_user` management command, and on Zulip Cloud, it's done by Zulip's support team. ### Details The "Public and private data (with consent)" export includes the private data of users who have allowed administrators to export it. Since Zulip Server 11.0, it also treats mirror dummy accounts as consenting. Mirror dummies are placeholder accounts that represent users from data imported from other products, such as Slack, and they only contain data that was already accessible to the exporting organization. When a user is deleted (as opposed to deactivated), their account is turned into a mirror dummy too, so `get_consented_user_ids` (`zerver/lib/export.py`) considered them to be consenting. Deleting a user also disables their export consent setting, but since mirror dummies are considered consenting regardless of that setting, this had no effect. The deleted account remains a participant in its direct message conversations, so the export included those conversations, along with messages from the other participants. ### Impact An organization administrator could obtain, through an export with member consent, direct messages in conversations that a deleted user had been part of. This includes messages sent in such conversations by other participants who had not allowed administrators to export their private data, as well as any remaining messages of the deleted user, whose consent setting was disabled when they were deleted. This affects Zulip Server 11.0 through 12.3, and only organizations with at least one deleted user. This is fixed in Zulip Server 12.4. ### References - [Export your organization](https://zulip.com/help/export-your-organization) - [Configure whether administrators can export your private data](https://zulip.com/help/export-your-organization#configure-whether-administrators-can-export-your-private-data)

Why it matters now

Fix Fixed Zulip server: 12.4, 13.0-rc2

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—Zulip server>= 11.0, <= 12.312.4Patch availableGHSA-m2g9-5v7r-xqcg
—Zulip server= 13.0-rc113.0-rc2Patch availableGHSA-m2g9-5v7r-xqcg
  • Zulip server Vendor— Affected >= 11.0, <= 12.3 Fixed in 12.4 Patch available GHSA-m2g9-5v7r-xqcg
  • Zulip server Vendor— Affected = 13.0-rc1 Fixed in 13.0-rc2 Patch available GHSA-m2g9-5v7r-xqcg

Remediation

Upgrade Zulip Server to 12.4 or 13.0-rc2.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

  • Fix · GHSA-m2g9-5v7r-xqcg Zulip server Fixed in 12.4 Advisory →
  • Fix · GHSA-m2g9-5v7r-xqcg Zulip server Fixed in 13.0-rc2 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-m2g9-5v7r-xqcg

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences