Zulip versions 12.5 and 13.3 can leak an internal secret, letting attackers take over a server

Zulip released fixes on Nov. 19, 2026, for versions 12.5 and 13.3 that can leak an internal secret and let attackers modify files or take over a server. Self‑hosted users are urged to upgrade or isolate systems while cloud users are largely unaffected.

Share
Zulip server security update advisory for versions 12.5 and 13.3

On November 19, 2026, Zulip released security fixes for Zulip Server 12.5 and 13.3 to close a flaw that can leak an internal secret, letting an attacker perform unauthorized file operations and, in the worst case, take over a server. The issue targets file storage and upload handling, and Zulip says the fix is urgent for installations that cannot rely on its cloud S3 integration.

How the flaw works

The advisory points to a single underlying problem: an internal secret was unintentionally exposed, likely through configuration or implementation in how file storage and upload handling are set up. That secret can be used to bypass normal checks and act as if it has full server privileges. The vulnerability isn’t a remote code execution bug in a library, but rather a mistake that leaks a key or credential. Once an attacker has that secret, they can modify or delete files and potentially escalate further.

Why the risk matters

The practical impact is that any organization running one of the vulnerable versions is at risk of an attacker gaining elevated privileges. Zulip lists “unauthorized file modification,” “full server takeover via secret exposure,” and “data deletion capability granted to attackers” as direct consequences. A compromised Zulip server can be used as a foothold to attack other services on the same network, or to pilfer stored messages and attachments. Zulip hasn’t reported any confirmed breaches tied to these flaws, so we don’t know whether attackers are already exploiting the issue or whether the vulnerabilities were discovered through code review.

What’s next

Zulip recommends upgrading to version 13.3 within days, and suggests a temporary block for installations that cannot upgrade right away. The company also notes that cloud users are largely unaffected because file storage is handled via S3 integration, so the block likely applies to specific self‑hosted configurations or as a precautionary measure rather than to cloud setups. For self‑hosted users, the safest bet is to isolate the Zulip server from other internal systems or restrict network access until you can patch. The next clear milestone is the widespread rollout of 13.3. If Zulip Cloud continues to report no issues after this patch, that will lend credibility to the claim that the S3 integration mitigates the risk. Until then, the only thing we know for certain is that the vulnerabilities exist and that a fix is available. Whether they’re being actively abused remains an open question.

Explore more coverage on BeansSearch this story across publishers

Read more