# CVE-2026-115785: Zimbra Collaboration Suite Data Source Test SMTP Command Injection via Unsanitized Email Address


- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-m4x2-65hq-rqw6

## What is CVE-2026-115785?

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

### Official description

An SMTP command injection vulnerability in the data-source testing functionality of Zimbra Collaboration Suite (ZCS) allows an ordinary authenticated user with account options enabled to inject CR/LF into the emailAddress inserted into an SMTP envelope command by a JSON SOAP request. After a successful preliminary POP3 or IMAP login, Zimbra sends the injected commands to the selected SMTP service. If that service accepts the pipelined transaction, the attacker can submit mail with attacker-selected recipients, headers and body content without victim interaction. The vulnerable command-construction path is present in ZCS 10.1.16 and 10.1.20.

Weakness: CWE-93 (Improper Neutralization of CRLF Sequences)

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


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

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

## Is CVE-2026-115785 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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