Zimbra Foss Source Code Only Releases
Introduction
This aims to be a community updated list of actual Zimbra Foss Releases based on official Synacor/Zimbra Source Code published on their Zimbra Github organisation
Binary release
- If you want a ready-to-use binary release for Zimbra Foss (not a source code only one) please check the download links at: ZimbraFossBuildersList page.
- If you want a ready-to-use binary release for Zimbra Network Edition please check the official download links at: Zimbra Download page and also Zimbra_Releases page.
Releases
| Version | Status | NE release date | Expected end of embargo date | FOSS release date | Embargoed? | E. days |
|---|---|---|---|---|---|---|
| 10.1.12 | Embargo | October 16, 2025 | December 16, 2025 | N/A | Yes | N/A |
| 10.1.11 | NE only | August 8, 2025 | N/A | N/A | N/A | N/A |
| 10.0.17 | NE only | August 8, 2025 | N/A | N/A | N/A | N/A |
| 10.1.10 | Released | July 18, 2025 | September 18, 2025 | October 19, 2025 | Yes | 93 |
| 10.0.16 | Released | July 18, 2025 | September 18, 2025 | October 19, 2025 | Yes | 93 |
| 10.1.9 | Released | June 18, 2025 | August 18, 2025 | July 24, 2025 | Yes | 36 |
| 10.0.15 | Released | June 18, 2025 | August 18, 2025 | July 24, 2025 | Yes | 36 |
| 9.0.0.p46 | Released | June 18, 2025 | August 18, 2025 | July 25, 2025 | Yes | 37 |
| 10.1.8 | Released | May 15, 2025 | July 15, 2025 | July 24, 2025 | Yes | 70 |
| 10.0.14 | Released | May 15, 2025 | July 15, 2025 | July 24, 2025 | Yes | 70 |
| 9.0.0.p45 | Released | May 15, 2025 | July 15, 2025 | July 25, 2025 | Yes | 71 |
| 10.1.7 | Released | April 18, 2025 | N/A | ~ April 25, 2025 | No | 0 |
Columns explanation
- Version: NE version. We expect the FOSS version in the Github repos to be the same one.
- Status: See Status section below for a detailed explanation.
- NE release date: ZCS Network Edition release date.
- FOSS release date: If there is an embargo this is the actual end of embargo date. If there was not an embargo this is when the source code was originally pushed to the repos.
- Embargoed?: Whether source code was not pushed immediately to the repos after the NE release (and thus it was embargoed).
- E. days: How many days was the release embargoed. ( We don't include end date in calculation. )
Status
Depending on which Zimbra Github tags and/or commits are available a Zimbra release might be in different status:
- Non released: No tag since the previous release has been released.
- Embargo: Some tags related to the version have been released. However some of the security fixes have been embargoed and are not available at the Zimbra Github organisation.
- Released: Every security fix is available for the version. This is an actual proper release.
- NE only: This release focus on Network Edition changes only. No FOSS changes whatsoever were done. This is not a FOSS release. We add it here just for convenience.
Note: Embargos usually last for 60 days since the Network Edition release with the same version number. Note: Sometimes when you try to build a version which it is in Embargo status you might end up either in a failed build or in a binary that cannot be used reliably.
About future tags
Please notice that Zimbra sometimes pushes tags about future versions about two weeks before the actual NE version is released. That's to be expected. Regarding this list we will ignore those tags till the NE counterpart version has been released.
E.g.: ZCS NE 10.1.10 has not been released but 10.1.10 tags have been pushed to the Zimbra repos.
TODO
- Make an standard way of snapshotting a release tag on all of the Zimbra repos and also hash it so that we check if any change happens.
Remarks
- At 2025 07 23 some commits related to 10.1.8 and 10.1.9 were made public in the development branch. However as they have not been pushed to the appropriated 10.1.8 and 10.1.9 tags... making impossible the build based on those tags... well... we still consider these tags as embargoed.
Check also
- Zimbra Foss CVE Commits let's you track Network Edition security fixes and their counterpart in FOSS commits. That way it will be easier to track a release embargo status.
