# CVE-2026-50057: Zimbra Collaboration Suite Local Privilege Escalation via Unrestricted Postfix Sudo Permissions


- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-h6p2-5x3j-hpj8

## What is CVE-2026-50057?

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

### Official description

A local privilege escalation vulnerability in the Zimbra Collaboration Suite (ZCS) MTA package allows the Unix zimbra account to execute arbitrary commands as root. The installed sudo policy permits passwordless root execution of Postfix administration commands without restricting their arguments. An attacker can select a zimbra-controlled daemon_directory in the Postfix configuration and invoke postfix set-permissions, causing Postfix to execute the attacker's post-install program as root. The Postfix configuration directory is also writable by zimbra, so restricting postconf alone does not remove the execution path. Exploitation requires local command execution as zimbra on an MTA node. ZCS 10.1.16 and 10.1.21 are affected.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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


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

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

## Is CVE-2026-50057 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-50057 is a high-severity vulnerability in Zimbra Collaboration Suite, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-50057 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-50057/ (Markdown: https://insights.sbomify.com/CVE-2026-50057/index.md)
```

## Sources

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

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