Zulip leaks message edits to non-subscribers when moving messages
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · GHSA-7w3h-65w5-m522. Fix status from GitHub.
Summary
Zulip server 4.0 and later before 12.3 leaks data when messages are moved from a public channel to a private channel. Users who are not subscribed to the private channel keep their message records from the public channel, so they receive the content of later edits to those messages. Their topic mute or follow settings also carry over into the private channel, and they are sent an update that reveals the private channel's ID and topic name. A user with low privileges can exploit this over the network without user interaction.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
This was discovered in an internal security audit using Claude Code. ### Impact Two data leaks occur when moving messages from a public channel to a private channel. A "non-subscriber" below refers to a user who is not subscribed to the private channel, and therefore under Zulip's access model shouldn't have access to its contents. - A non-subscriber's historical `UserMessage` rows (created by starring/reacting/marking-read in the public channel) survive the move, so the non-subscriber keeps receiving `update_message` events - leaking the content of any future edits to the affected messages, in a channel whose content should be inaccessible to them. - A non-subscriber's `UserTopic` row - recording that they muted or followed the topic in the public channel - is migrated into the private target channel instead of removed. This both persists the row and pushes to that user a `user_topic` event carrying the private channel's `stream_id` and `topic_name`. ### Root cause Both leaks stem from access being inferred from Subscription rows, while in a public channel a user can hold a `UserMessage` or `UserTopic` row without any subscription: - Content-edit `update_message` events were sent to every holder of a `UserMessage` row, with no access check at all - so a non-subscriber's surviving rows kept delivering edits. - On a channel move, the set of users "losing access" (whose `UserTopic` row is removed rather than migrated) is derived from `Subscription` rows on the old channel. A user holding a `UserTopic` row without a subscription is unaccounted for, so the row is migrated instead of revoked. ### Patches Fixed in Zulip server 12.3.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | Zulip server | >=4.0 | 12.3 | Patch available | GHSA-7w3h-65w5-m522 |
- Zulip server Vendor— Affected >=4.0 Fixed in 12.3 Patch available GHSA-7w3h-65w5-m522
Remediation
Upgrade Zulip server to version 12.3 or later.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-7w3h-65w5-m522 Zulip server Fixed in 12.3 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-7w3h-65w5-m522
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences