Read the docs

Zulip Server bot transfer exposes private channels to former owner

Priority MEDIUM 40Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
Low · Low · None
Fix status
Fixed

Attack profile from CVSS 3.1 · GHSA-fphq-r53h-f8qj. Fix status from GitHub.

Summary

Zulip Server before 12.4 and version 13.0-rc1 let a bot owner keep working access to a bot after transferring its ownership, because the bot's API key does not change on transfer. Bots can send messages to and list any channel their owner can access, so the previous owner can post as the bot in the new owner's private channels and see their names, descriptions and subscriber counts. Any authenticated user who owns a bot can do this, and a deactivated user can do it after an administrator reactivates a bot they owned. The previous owner cannot read messages in those channels.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Description from the GitHub advisory

### Summary A user who owned a bot could make another user its owner while keeping a working copy of the bot's API key. Since bots can send messages to any channel their owner can, the previous owner could then use the bot to post in the new owner's private channels, and to list those channels. A deactivated user could gain the same ability if an administrator reactivated a bot they had owned, because that makes the administrator the bot's owner. Severity is moderate: the attacker can't read messages in those channels, but by default, any user other than a guest can create a bot. ### Details Bots can send messages to any channel that their owner can, inheriting their owner's sending permissions. A bot can also list the channels its owner is subscribed to, including their names, descriptions, and subscriber counts. A bot's owner could make any other active user the bot's owner, without administrator permissions (`patch_bot_backend` in `zerver/views/users.py`). The bot's API key didn't change, so the previous owner could keep using the bot with the new owner's channel access. The new owner wasn't notified that they had been given the bot. Since Zulip Server 8.0, reactivating a bot whose owner is deactivated makes the administrator who reactivates it the bot's owner (`do_reactivate_user` in `zerver/actions/create_user.py`). The bot's API key didn't change in this case either. A bot's API key keeps working when its owner is deactivated, so the deactivated owner could use the bot with the administrator's channel access. ### Impact The previous owner of a bot could post, as the bot, in any channel the new owner can post in, including private channels the previous owner has no access to. They could also see the names, descriptions, and subscriber counts of the private channels the new owner is subscribed to. Messages posted this way appear to come from a bot owned by the new owner. The previous owner could not read messages in those channels. Any user who owns a bot could do this, by transferring it to another user. A deactivated user could do this only after an administrator reactivated a bot they had owned. This affects all Zulip Server versions through 12.3. ### Fix Zulip Server 12.4 restricts how a bot's owner can change: - Only organization administrators can change a bot's owner. - Changing a bot's owner still doesn't change its API key. Instead, the new owner receives a direct message saying that the previous owner may still have a copy of the API key. - Reactivating a bot whose owner is deactivated now generates a new API key for the bot. Integrations using the old key will need to be updated. Upgrading doesn't replace the API key of a bot whose owner was changed before the upgrade. The bot's current owner can [generate a new API key](https://zulip.com/help/manage-a-bot#get-a-bots-api-key) for it. ### Credit This vulnerability was discovered by Ada Logics using Google’s security automation tooling, and later also independently reported by Yves Soete of Blacksight LLC (@yssoe). ### References - [Channel permissions for bots](https://zulip.com/help/bots-overview#channel-permissions-for-bots) - [Get a bot's API key](https://zulip.com/help/manage-a-bot#get-a-bots-api-key)

Why it matters now

Fix Fixed Zulip server: 12.4, 13.0-rc2

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—Zulip server< 12.412.4Patch availableGHSA-fphq-r53h-f8qj
—Zulip server= 13.0-rc113.0-rc2Patch availableGHSA-fphq-r53h-f8qj
  • Zulip server Vendor— Affected < 12.4 Fixed in 12.4 Patch available GHSA-fphq-r53h-f8qj
  • Zulip server Vendor— Affected = 13.0-rc1 Fixed in 13.0-rc2 Patch available GHSA-fphq-r53h-f8qj

Remediation

Upgrade to Zulip Server 12.4 or 13.0-rc2. Zulip Server 12.4 restricts bot owner changes to organization administrators and generates a new API key when a bot with a deactivated owner is reactivated. Upgrading does not replace the API key of a bot whose owner was changed before the upgrade, so the bot's current owner must generate a new API key for it.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

  • Fix · GHSA-fphq-r53h-f8qj Zulip server Fixed in 12.4 Advisory →
  • Fix · GHSA-fphq-r53h-f8qj Zulip server Fixed in 13.0-rc2 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-fphq-r53h-f8qj

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences