CVE-2026-73576

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreHIGH confidence

Score 6.3 from GitHub Security Advisory published 2026-08-13. a secondary CVSS source baseline 6.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In Zimbra Collaboration (ZCS) before 10.1.17, weak cryptographic key generation vulnerability exists in the OnlyOffice integration. The zimbraDocumentEditingJwtSecret is generated using an insecure random number generator, resulting in insufficient entropy. An attacker who obtains a JWT signed with the generated secret may be able to recover the JWT signing secret through offline brute-force, potentially enabling JWT forgery.

CVSS v3
6.3
EG Score
6.3(high)
EG Risk
28(Track)
EG Risk 28/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity63% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

August 13, 2026

Last Modified

August 13, 2026

Advisory Details (2)

Auto-updated Aug 13, 2026
No patch confirmed yet.
generic

Zimbra Responsible Disclosure Policy - Zimbra :: Tech Center

https://wiki.zimbra.com/wiki/Zimbra_Responsible_Disclosure_Policy
generic

Zimbra Security Advisories - Zimbra :: Tech Center

https://wiki.zimbra.com/wiki/Zimbra_Security_Advisories

Vendor Advisories for CVE-2026-73576(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 25× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 00:52 UTCEG score recompute
  2. 2026-08-21 00:52 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 02:49 UTCEG score recompute
  5. 2026-08-20 02:49 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 04:44 UTCEG score recompute
  8. 2026-08-19 04:44 UTCGHSA enrichment
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 06:41 UTCEG score recompute
  12. 2026-08-18 06:41 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 08:38 UTCEG score recompute
  15. 2026-08-17 08:37 UTCGHSA enrichment
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 10:34 UTCEG score recompute
  19. 2026-08-16 10:34 UTCGHSA enrichment
  20. 2026-08-16 02:15 UTCEPSS rescore
  21. 2026-08-15 12:32 UTCEG score recompute
  22. 2026-08-15 12:32 UTCGHSA enrichment
  23. 2026-08-15 01:31 UTCEPSS rescore
  24. 2026-08-14 14:28 UTCEG score recompute
  25. 2026-08-14 14:28 UTCGHSA enrichment
Show 4 more
  1. 2026-08-13 16:25 UTCEG score recompute
  2. 2026-08-13 16:17 UTCEG score recompute
  3. 2026-08-13 15:32 UTCEG score recompute
  4. 2026-08-13 15:31 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-73576?
CVE-2026-73576 is a medium vulnerability published on August 13, 2026. In Zimbra Collaboration (ZCS) before 10.1.17, weak cryptographic key generation vulnerability exists in the OnlyOffice integration. The zimbraDocumentEditingJwtSecret is generated using an insecure random number generator, resulting in insufficient entropy. An attacker who obtains a JWT signed with…
When was CVE-2026-73576 disclosed?
CVE-2026-73576 was first published in the National Vulnerability Database on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73576 actively exploited?
CVE-2026-73576 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.2% of all scored CVEs.
What is the CVSS score of CVE-2026-73576?
CVE-2026-73576 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-73576?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73576, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-73576

Explore →

Is Your Infrastructure Affected by CVE-2026-73576?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs