Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach internet-facing ZCS with OnlyOffice
-
DeliveryOpen supported public Briefcase document
-
ExploitTamper unsigned save fields with traversal path
-
ExecutionWrite file outside intended directory
-
ImpactExecute commands as zimbra
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK
2 techniques across 2 tactics: Discovery, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires the OnlyOffice/Document Editing integration to be available/enabled on the Zimbra server (a non-default add-on component), and the attacker must have access to an existing supported PUBLIC Briefcase document, which provides the unauthenticated entry point. The concrete flaw is abuse of unsigned save fields to perform path-traversal writes that result in command execution as the zimbra system account. Limiting factors: deployments without OnlyOffice document editing, or without publicly accessible supported Briefcase documents, are not exploitable via this path; the fixed/patched version could not be confirmed from the single wiki reference provided. |
| Impact | The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H = 9.8) portrays this as a maximally severe, remote, unauthenticated command-execution flaw in Zimbra Collaboration Suite, and command execution as the 'zimbra' service account plausibly justifies the C:H/I:H/A:H impact triad. However, the raw score understates real-world gating: exploitation is explicitly conditional on the OnlyOffice/Document Editing integration being available AND the attacker having access to an existing supported PUBLIC Briefcase document. That makes AC:L optimistic - the OnlyOffice add-on is a non-default, separately-provisioned component, so realistically this behaves closer to AC:H. No EPSS score, no CISA KEV listing, and no public exploit code were provided, so there is no confirmed active exploitation - status is 'no public exploit identified at time of analysis.' Weighing signals: this is a genuine high-priority patch target because Zimbra is a historically favored, internet-facing target and the outcome (RCE as zimbra) is severe, but the OnlyOffice/public-Briefcase preconditions mean it is not universally exploitable against every ZCS deployment. Treat as high priority specifically for installs that expose OnlyOffice document editing. |
| Exploit ScenarioDerived | An unauthenticated remote attacker locates a Zimbra server with OnlyOffice/Document Editing enabled and reachable public Briefcase documents, opens such a document, and abuses the unsigned save fields to write attacker-controlled content outside the intended directory via path traversal. The traversal write lands in a location that leads to command execution as the zimbra user, giving the attacker code execution on the mail server. No public proof-of-concept was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 25, 2026
Unauthenticated remote attackers who can reach an existing publicly shared Briefcase document can abuse unsigned save fields in Zimbra Collaboration Suite's OnlyOffice/Document Editing integration to perform path-traversal writes and execute commands as the zimbra service account. Exploitation is contingent on the non-default OnlyOffice/Document Editing add-on being enabled and on a supported Briefcase document being publicly accessible, so the 9.8 score in the source feed (AV:N/AC:L) is moderated by an independent assessment that rates attack complexity as High (AC:H) given those prerequisites. No public exploit code or confirmed active exploitation was identified at time of analysis, and no patched version could be confirmed from the single Zimbra wiki advisory reference provided.
RemediationAI
No vendor-released patch version could be confirmed from the available single reference (the Zimbra security advisories wiki at https://wiki.zimbra.com/wiki/Zimbra_Security_Advisories); monitor that page and apply the vendor fix as soon as an affected-build matrix and patched version are published, since the wildcard CPE gives no version guidance. In the interim, the highest-value compensating control is to disable or remove the OnlyOffice/Document Editing integration on any server that does not strictly require it - this closes the vulnerable save path entirely, at the cost of losing in-browser collaborative document editing. Where the integration must stay enabled, eliminate the unauthenticated entry point by auditing and revoking public/anonymous sharing on Briefcase folders so that no supported document is reachable without authentication; the trade-off is that legitimate external or cross-tenant document sharing will stop working and internal users must be re-authenticated to reach those documents. Additional hardening with clear trade-offs: restrict network exposure of the Document Editing service port so only the Zimbra mailstore can reach it (breaks direct client access and requires firewall changes); ensure the zimbra service account cannot write outside its own data directories by tightening filesystem ownership and permissions and mounting application directories read-only where practical (may interfere with legitimate document storage and log rotation); and deploy file-integrity monitoring or an EDR/WAF rule that alerts on traversal sequences such as '../' in OnlyOffice save requests (can generate false positives on unusual but legitimate filenames). Applying the vendor advisory as soon as the fixed build is identified remains the only complete remediation.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a CWE-22 path traversal in the save-handling path of Zimbra's OnlyOffice/Document Editing integration, reached via the unauthenticated entry point created by a publicly shared Briefcase document. Save requests issued by the document-editing backend carry fields that are not cryptographically signed or otherwise integrity-protected; an attacker who can trigger a save against a supported public Briefcase document can influence those fields, embedding directory-traversal sequences that cause the server to write files outside the intended storage location. Because the Zimbra mailstore/Document Editing components run as the zimbra service account, writing attacker-controlled content to a suitable location (for example a servlet, script or configuration path reachable by the running service) converts the arbitrary file write into command execution under that account. The CPE cpe:2.3:a:zimbra:zimbra_collaboration_suite_(zcs):*:*:*:*:*:*:*:* uses wildcards, indicating the issue is tracked against Zimbra Collaboration Suite (ZCS) without a version qualifier in the source data. Attack complexity, not reachability, is the limiting factor: only deployments with the non-default OnlyOffice/Document Editing component active and at least one publicly accessible supported Briefcase document expose the path described.
Know when Zimbra gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Remote and unauthenticated against public Briefcase docs (AV:N/PR:N), but the required non-default OnlyOffice integration plus access to a supported public document raises complexity (AC:H); command execution as zimbra yields full C/I/A.
Primary rating from Vendor (rapid7).
CVSS VectorVendor: rapid7
Lifecycle Timeline
2DescriptionCVE.org
When OnlyOffice/Document Editing is available, an unauthenticated remote attacker with access to an existing supported public Briefcase document can abuse unsigned save fields to perform path-traversal writes and execute commands as zimbra.
Executive ViewAI
Zimbra Collaboration Suite, when the non-default OnlyOffice/Document Editing add-on is enabled and a publicly shared Briefcase document exists, is exposed to a critical vulnerability that could allow attackers to compromise the email and collaboration server. This could result in unauthorized access to sensitive business communications, operational disruption, and potential lateral movement within the network. With no vendor patch available, leadership should prioritize immediate mitigation to protect organizational data.
No vendor-released patch identified at time of analysis. Interim mitigations include disabling the non-default OnlyOffice/Document Editing add-on if not business-critical, removing all public sharing permissions from Briefcase documents, restricting access to trusted internal users, and monitoring Zimbra logs for suspicious file writes or command execution as the zimbra service account.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
Remote code execution in Zimbra Collaboration (ZCS) before 10.1.20 enables unauthenticated network attackers to execute
Zimbra's sudo configuration permits the zimbra user to execute the zmslapd binary as root with arbitrary parameters. Rat
An issue was discovered in ProxyServlet.java in the /proxy servlet in Zimbra Collaboration Suite 8.8 before 8.8.15 Patch
A critical unauthenticated remote code execution vulnerability exists in Zimbra Collaboration Suite PostJournal service
Multiple cross-site request forgery (CSRF) vulnerabilities in the Mail interface in Zimbra Collaboration Server (ZCS) be
An issue was discovered in Zimbra Collaboration (ZCS) 8.8.x and 9.x (e.g., 8.8.15). Rated high severity (CVSS 7.8), this
Unspecified vulnerability in Zimbra Collaboration Server 7.2.5 and earlier, and 8.0.x through 8.0.5, has "critical" impa
An issue was discovered in Zimbra Collaboration (ZCS) 9.0 and 10.0. Rated medium severity (CVSS 6.1), this vulnerability
An issue in Zimbra Collaboration ZCS v.8.8.15 and v.9.0 allows an attacker to execute arbitrary code via the sfdc_preaut
An issue in Zimbra Collaboration (ZCS) v.8.8.15 and v.9.0 allows a remote attacker to escalate privileges and obtain sen
Zimbra Collaboration Open Source 8.8.15 does not encrypt the initial-login randomly created password (from the "zmprove
An issue was discovered in ZmMailMsgView.js in the Calendar Invite component in Zimbra Collaboration Suite 8.8.x before
EUVD-2026-87101
GHSA-4g2j-34p9-p684
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB