CVE-2026-73576: 
Zimbra Collaboration Server vulnerability analysis and mitigation

CVE-2026-73576 is a weak cryptographic key generation vulnerability in the OnlyOffice integration of Zimbra Collaboration (ZCS). The zimbraDocumentEditingJwtSecret is generated using an insecure (non-cryptographically secure) random number generator, resulting in insufficient entropy. An attacker who obtains a JWT signed with this secret may recover the signing key via offline brute-force and subsequently forge JWTs. All ZCS versions before 10.1.17 are affected. It carries a CVSS v3.1 base score of 6.3 (Medium) (GitHub Advisory, Zimbra Security Advisories).

The root cause is classified as CWE-1241 (Use of Predictable Algorithm in Random Number Generator). Zimbra's OnlyOffice integration generates the zimbraDocumentEditingJwtSecret — used to sign JWTs for document editing sessions — with a predictable pseudo-random number generator that produces insufficient entropy. An authenticated attacker with low privileges can obtain a legitimately signed JWT (e.g., by accessing the document editing feature), then perform an offline brute-force or cryptanalytic attack (CAPEC-97: Cryptanalysis) against the weak secret to recover it. Once the secret is known, the attacker can forge arbitrary JWTs, bypassing authentication controls for the OnlyOffice integration. Exploitation requires network access and low-level authentication, but no user interaction (GitHub Advisory).

Successful exploitation allows an authenticated attacker to forge JWTs and impersonate arbitrary users within the Zimbra OnlyOffice document editing functionality. The primary impact is a high integrity loss — forged tokens could grant unauthorized access to documents, enable unauthorized edits, or facilitate privilege escalation within the document editing subsystem. Confidentiality and availability are not directly impacted by this vulnerability, though forged access to sensitive documents could lead to indirect data exposure (GitHub Advisory, Zimbra Security Advisories).

There is no public proof-of-concept exploit and no evidence of in-the-wild exploitation at this time (GitHub Advisory). The NVD SSVC assessment classifies exploitation as "none" and the attack as non-automatable, reflecting the requirement for an attacker to first obtain a valid JWT before attempting offline brute-force. The EPSS score is approximately 0.188% (9th percentile), indicating a low near-term exploitation probability. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Qualys has added detection for this CVE (Detection ID 532191).

1. Reconnaissance: Identify Zimbra Collaboration instances running versions prior to 10.1.17 with OnlyOffice document editing enabled, using network scanning or banner grabbing tools.
2. Obtain a valid JWT: Authenticate to the Zimbra instance with a low-privileged account and initiate a document editing session via the OnlyOffice integration to capture a legitimately issued JWT (e.g., via browser developer tools or proxy interception).
3. Offline brute-force the JWT secret: Use a JWT cracking tool (e.g., hashcat with JWT mode, or jwt_tool) to perform an offline dictionary or brute-force attack against the captured JWT, exploiting the low entropy of the zimbraDocumentEditingJwtSecret.
4. Forge a JWT: Once the signing secret is recovered, craft a new JWT with a modified payload (e.g., substituting a target user's identity or elevated claims) and sign it with the recovered secret.
5. Access document editing as target user: Submit the forged JWT to the OnlyOffice integration endpoint to gain unauthorized access to document editing sessions as the impersonated user (GitHub Advisory).

• Network: Unusual or repeated requests to OnlyOffice/document editing API endpoints from unexpected source IPs or user accounts; JWT tokens in HTTP headers originating from accounts that have not recently authenticated.
• Logs: Zimbra mailbox or OnlyOffice integration logs showing document editing sessions initiated by users who did not perform a corresponding login event; authentication anomalies where a user's JWT is used from multiple distinct IP addresses simultaneously.
• Application: Multiple failed JWT validation attempts in OnlyOffice integration logs, which may indicate brute-force attempts against the secret; unexpected changes to the zimbraDocumentEditingJwtSecret configuration attribute.

Upgrade Zimbra Collaboration to version 10.1.17 or later, which addresses the weak key generation by using a cryptographically secure random number generator for zimbraDocumentEditingJwtSecret (Zimbra Security Advisories, GitHub Advisory). As an additional remediation step on affected systems, administrators should manually rotate the zimbraDocumentEditingJwtSecret to a value generated by a cryptographically secure source after upgrading. If immediate upgrade is not possible, consider disabling the OnlyOffice document editing integration until patching can be completed.

The vulnerability was disclosed by Zimbra on August 13, 2026, via their Security Advisories wiki and the GitHub Advisory Database. Coverage has been limited to automated vulnerability tracking platforms such as VulDB, CVEFeed, and INCIBE-CERT, with no notable independent researcher commentary or significant social media discussion observed at this time (Zimbra Security Advisories).