CVE-2026-115574 · Other
NO FIX YET · SEE WHAT TO DO
From Zulip 11.0 up to 12.2, organizations with web-public channels let logged-out visitors call GET /json/users with include_custom_profile_fields=true and receive every user's custom profile field values. An attacker with no account can read that personal profile data.
first public Aug 10, 2026 · 1 source
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Only Zulip servers running versions 11.0 through 12.2 where the organization has web-public channels enabled are exposed. Organizations on older versions or without web-public channels are not exposed through this endpoint. Self-hosted and managed Zulip deployments both need to be checked against their version.
Not affected if no-web-public-channels, version-12.2-or-later, version-below-11.0
Who cares self-hosted, web-public-channels, zulip
zulip-server --version or the installed release; affected versions are 11.0 through 12.2 (before 12.2).GET /json/users?include_custom_profile_fields=true returns custom profile field values without logging in.12.2Zulip 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.
This page as .md · .json · in your agent: get_signal("CVE-2026-115574") · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.