# CVE-2026-115574: Zulip custom profile fields information disclosure

Source: https://junglewise.ai/threats/cve-2026-115574-zulip-is-an-open-source-team-collaboration-tool-from-11-0-until  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-04. Updated: 2026-11-04  
License: CC BY 4.0 with a link back

CVE-2026-115574 · Severity: medium · CVSS 5.3 · Published 2026-11-04

Zulip is an open-source team collaboration platform. When organizations enable web-public channels, unauthenticated visitors can request custom profile field values (such as phone numbers, birthdays, and pronouns) for all users via the GET /json/users API endpoint, exposing sensitive personal information that should remain private. This issue affects versions 11.0 through 12.1 and is fixed in version 12.2.

Technologies: [Zulip](https://junglewise.ai/threats/technologies/zulip). Vendors: [Zulip](https://junglewise.ai/threats/vendors/zulip).

## Quick answers

**Is CVE-2026-115574 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-115574 being exploited in the wild.

**How severe is CVE-2026-115574?** Medium severity, with a CVSS score of 5.3, published 4 November 2026.

**Which products and versions are affected?** Zulip 11.0 to 12.1.

**Is there a fix for CVE-2026-115574?** Yes: fixed in 12.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-115574 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-115574?** Check whether you run Zulip at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 12.2

## Technical details

The GET /json/users endpoint was accessible to spectators (logged-out users) on realms with web-public channels enabled. The endpoint honored the include_custom_profile_fields parameter without enforcing access control, allowing unauthenticated visitors to retrieve custom profile field values for all users. The fix adds a check in get_users_for_api() to ensure spectators (denoted by acting_user=None) cannot request custom profile fields, regardless of the parameter value.

## Affected products

- Zulip Zulip 11.0 to 12.1

## Timeline

- 2026-11-04: disclosed

## References

- [https://github.com/zulip/zulip/commit/6f33a8fa345ba776039a3f46131c253599a3ba15](https://github.com/zulip/zulip/commit/6f33a8fa345ba776039a3f46131c253599a3ba15)
- [https://github.com/zulip/zulip/commit/774d4c7b12755178fa406f0c0f3b2cafdbbec32c](https://github.com/zulip/zulip/commit/774d4c7b12755178fa406f0c0f3b2cafdbbec32c)

## Related threats

- [Zulip authorization bypass in draft message handling](https://junglewise.ai/threats/cve-2026-115474-zulip-is-an-open-source-team-collaboration-tool-from-8-0-until)
- [Zulip Server path traversal in data import utility](https://junglewise.ai/threats/cve-2026-26058-zulip-server-path-traversal-in-data-import-utility)
- [Zulip missing authorization for anonymous access to attachments and topics](https://junglewise.ai/threats/cve-2026-25742-zulip-missing-authorization-for-anonymous-access-to-attachments)