Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2025-25195 Overview
CVE-2025-25195 is an information disclosure vulnerability in Zulip, an open source team chat application. A weekly cron job introduced in commit 50256f48314250978f521ef439cafa704e056539 demoted channels to inactive status after 180 days without traffic. The status-change event was broadcast to all users in the organization rather than only channel subscribers. The event payload contained the name of the private channel, leaking metadata to unauthorized users. The same behavior occurred when a previously inactive private channel received its first new message. The issue was fixed before any release, existing only in the main branch [CWE-200].
Critical Impact
Names of private Zulip channels could be exposed to every user in the organization when channel activity status changed, breaking confidentiality expectations for private channel metadata.
Affected Products
- Zulip server main branch containing commit 50256f48314250978f521ef439cafa704e056539
- No published Zulip release versions are affected
- Development and self-hosted deployments tracking main prior to the fix
Discovery Timeline
- 2025-02-13 - CVE-2025-25195 published to NVD
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2025-25195
Vulnerability Analysis
The vulnerability is a broken access control issue that causes information disclosure of private channel names. Zulip added logic to track whether a channel was recently_active based on message traffic in the last 180 days. When a channel transitioned between active and inactive states, Zulip emitted a client event so subscribers could update their UI.
The transition event was dispatched using active_user_ids(stream.realm_id), which returns every active user in the organization. Because the event payload included the private channel's name, non-subscribers received channel metadata they were never authorized to see. Two conditions triggered the leak: the weekly cron job demoting a private channel to inactive, and the first message posted to a private channel that had been inactive for over 180 days.
Root Cause
The root cause is an incorrect audience selection for a client event. The notify function passed the realm-wide user list to send_event_on_commit instead of restricting recipients to users with metadata access to the channel. Private channels in Zulip normally hide their name and existence from non-subscribers, but the status-change event bypassed that boundary.
Attack Vector
Exploitation requires only an authenticated account in the same Zulip organization. No elevated privileges or user interaction from victims are needed. An attacker with a low-privileged account could passively collect private channel names as inactive transitions occurred or as messages resumed in dormant private channels.
# Vulnerable dispatch (before fix) in zerver/lib/streams.py
# Event was sent to every active user in the realm, not just channel subscribers.
name=stream.name,
)
- send_event_on_commit(stream.realm, event, active_user_ids(stream.realm_id))
+ send_event_on_commit(stream.realm, event, can_access_stream_metadata_user_ids(stream))
Source: Zulip Commit 75be449d
Detection Methods for CVE-2025-25195
Indicators of Compromise
- Presence of Zulip server code built from main between commit 50256f48 and the fix commits 75be449d and a2a1a7f8
- Client event logs showing stream update events with is_recently_active field delivered to users not subscribed to the affected private channel
- Cron entry update-channel-recently-active-status running against a vulnerable build
Detection Strategies
- Review Zulip application logs for send_event_on_commit calls tied to stream active-status changes and confirm the recipient list matches channel subscribers only
- Audit deployed Zulip commit hashes against the fix commits referenced in Zulip Security Advisory GHSA-x8cx
- Correlate scheduled cron execution of update_channel_recently_active_status with subsequent broadcast events to non-subscribers
Monitoring Recommendations
- Monitor Zulip server processes for unexpected event fan-out targeting all realm users when private-channel state changes
- Track deployment provenance so that self-hosted instances following main are flagged for advisory review
- Log and review the first message sent to any private channel dormant longer than 180 days for correlated leak events
How to Mitigate CVE-2025-25195
Immediate Actions Required
- Update self-hosted Zulip installations tracking main to include commits 75be449d456d29fef27e9d1828bafa30174284b4 and a2a1a7f8d152296c8966f1380872c0ac69e5c87e
- Inventory all Zulip deployments and confirm none were built from vulnerable main snapshots
- Notify organization administrators if private channel names may have been disclosed while the vulnerable code was running
Patch Information
The issue was remediated in commits 75be449d456d29fef27e9d1828bafa30174284b4 and a2a1a7f8d152296c8966f1380872c0ac69e5c87e. The fix replaces the realm-wide recipient list with can_access_stream_metadata_user_ids(stream), ensuring the is_recently_active event is only sent to users authorized to see channel metadata. The vulnerability never shipped in a tagged release, so users of published Zulip versions require no action. See the Zulip Security Advisory GHSA-x8cx for coordinated disclosure details.
Workarounds
- Pin production deployments to a tagged Zulip release rather than the main development branch
- If running main is required, apply the fix commits manually before deploying to environments containing private channels
- Temporarily disable the update-channel-recently-active-status cron entry until the patched commits are deployed
# Verify Zulip server includes the fix commits
cd /home/zulip/deployments/current
git log --oneline | grep -E '75be449d|a2a1a7f8'
# If missing, apply the fix commits from upstream
git fetch origin
git cherry-pick 75be449d456d29fef27e9d1828bafa30174284b4
git cherry-pick a2a1a7f8d152296c8966f1380872c0ac69e5c87e
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

