CVE-2026-115474
Zulip: Saving a draft DM to a user bypasses can_access_all_users_group permission
Zulip is an open-source team collaboration tool. From 8.0 until 12.2, in organizations where the Who can view all other users in the organization setting restricted guests from viewing other users, saving or editing a direct message draft did not verify that the sender could access the draft recipients. A guest could thereby gain access to otherwise restricted users' profile information without sending a message. Organizations that did not restrict guest access were unaffected. This issue is fixed in version 12.2.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| zulip zulip |
>= 8.0, < 12.2 (affected) | CNA: GitHub_M |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 6.5 medium |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N | CNA: GitHub_M |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://github.com/zulip/zulip/security/advisories/GHSA-vwqp-7j32-xfg5CNA: GitHub_M · x_refsource_CONFIRM
- https://github.com/zulip/zulip/pull/39913CNA: GitHub_M · x_refsource_MISC
- https://github.com/zulip/zulip/commit/1127d4cd3cc17a3cc38435ce57ed52b083c33f97CNA: GitHub_M · x_refsource_MISC
- https://github.com/zulip/zulip/commit/83a4a3a966e6eef11914b80f04426ae114a1970dCNA: GitHub_M · x_refsource_MISC
- https://github.com/zulip/zulip/releases/tag/12.2CNA: GitHub_M · x_refsource_MISC
- https://zulip.readthedocs.io/en/latest/overview/changelog.html#zulip-server-12-2CNA: GitHub_M · x_refsource_MISC
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.