# CVE-2026-10632: Zimbra Collaboration Suite Classic Web Client Reflected Cross-Site Scripting via Document Editor Packages Parameter


- **Severity:** High 8.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-rjjq-j274-2p2c

## What is CVE-2026-10632?

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

### Official description

A reflected cross-site scripting vulnerability in the Classic Web Client of Zimbra Collaboration Suite (ZCS) allows an attacker to inject JavaScript through the packages parameter of the /h/rest document editor. The editor inserts package names into script attributes without HTML encoding. When combined with CVE-2026-50053, an attacker with an ordinary Zimbra account can supply their own authentication token and document identifiers in a URL and execute JavaScript in another signed-in user's Zimbra browser session when that user opens the URL. This permits reading mailbox data and performing authenticated actions as the victim. The issue affects ZCS 10.1.16 and was remediated in 10.1.17.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-10632 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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