# CVE-2026-93627: Zimbra Collaboration Suite Calendar Processing Authentication Bypass via Forged iCalendar CANCEL/REQUEST Organizer


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-77gq-8m6p-2c3g

## What is CVE-2026-93627?

CVE-2026-93627 is a medium-severity vulnerability in Zimbra Collaboration Suite, published on 23 Oct 2026. 

### Official description

An organizer authentication vulnerability in the email calendar processing of Zimbra Collaboration Suite (ZCS) allows an unauthenticated sender to cancel or modify an existing meeting in a recipient's calendar. Zimbra accepts iCalendar CANCEL and REQUEST components without verifying that the email sender is authorized to act as the supplied organizer. An attacker who knows the meeting UID and organizer address can supply a non-outdated sequence number to move the recipient's meeting to Trash or replace its details. Processing occurs automatically during email delivery without recipient interaction. ZCS 10.1.16 and 10.1.21 are affected.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2026-93627?


## How do I fix CVE-2026-93627?

No fix has been published for CVE-2026-93627 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-93627 being exploited?

There is no known exploitation of CVE-2026-93627 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93627 and fix it if it is affected.

What it is: CVE-2026-93627 is a medium-severity vulnerability in Zimbra Collaboration Suite, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-93627 in the wild and no public exploit code.

Affected product: Zimbra Collaboration Suite. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93627/ (Markdown: https://insights.sbomify.com/CVE-2026-93627/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93627
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93627
- OSV: https://osv.dev/vulnerability/CVE-2026-93627

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93627/
Summaries are generated and may contain mistakes; the official description above is the record.