CVE-2026-115574
Zulip: Custom profile fields can be read by logged-out visitors in organization with web-public channels
Zulip is an open-source team collaboration tool. From 11.0 until 12.2, organizations with web-public channels enabled exposed the GET /json/users endpoint to logged-out spectators, and a missing access-control check allowed include_custom_profile_fields=true to return every user's custom profile field values in addition to the documented limited directory data. This exposed those custom profile field values to unauthenticated visitors. 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 |
>= 11.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 / 5.3 medium |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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-3m37-hwq6-jrj8CNA: GitHub_M · x_refsource_CONFIRM
- https://github.com/zulip/zulip/pull/39913CNA: GitHub_M · x_refsource_MISC
- https://github.com/zulip/zulip/commit/6f33a8fa345ba776039a3f46131c253599a3ba15CNA: GitHub_M · x_refsource_MISC
- https://github.com/zulip/zulip/commit/774d4c7b12755178fa406f0c0f3b2cafdbbec32cCNA: 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.