Mattermost End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Mattermost versions. Data from endoflife.date, checked against the vendor's own lifecycle pages where we have read them (share on /accuracy). Updated at every deploy.
Mattermost 12.0 is supported until January 15, 2027, its end-of-support date. The next Mattermost version to reach end of life is 11.10, on November 15, 2026. 54 of 58 tracked Mattermost versions are past end of life; the most recent to reach it, 11.9, did so on October 15, 2026. The full Mattermost lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 6.0 | 6.0.4 | Oct 8, 2021 | Jan 15, 2022 | 1764 days past EOL | EOL |
| 6.1 | 6.1.3 | Nov 11, 2021 | Feb 15, 2022 | 1733 days past EOL | EOL |
| 6.2 | 6.2.5 | Dec 13, 2021 | Mar 15, 2022 | 1705 days past EOL | EOL |
| 6.3 LTS | 6.3.10 | Jan 13, 2022 | Oct 15, 2022 | 1491 days past EOL | EOL |
| 6.4 | 6.4.3 | Feb 15, 2022 | May 15, 2022 | 1644 days past EOL | EOL |
| 6.5 | 6.5.2 | Mar 11, 2022 | Jun 15, 2022 | 1613 days past EOL | EOL |
| 6.6 | 6.6.2 | Apr 7, 2022 | Jul 15, 2022 | 1583 days past EOL | EOL |
| 6.7 | 6.7.2 | May 11, 2022 | Aug 15, 2022 | 1552 days past EOL | EOL |
| 7.0 | 7.0.2 | Jun 13, 2022 | Sep 15, 2022 | 1521 days past EOL | EOL |
| 7.1 LTS | 7.1.9 | Jul 13, 2022 | May 15, 2023 | 1279 days past EOL | EOL |
| 7.2 | 7.2.1 | Aug 11, 2022 | Nov 15, 2022 | 1460 days past EOL | EOL |
| 7.3 | 7.3.1 | Sep 14, 2022 | Dec 15, 2022 | 1430 days past EOL | EOL |
| 7.4 | 7.4.1 | Oct 12, 2022 | Jan 15, 2023 | 1399 days past EOL | EOL |
| 7.5 LTS | 7.5.2 | Nov 9, 2022 | Feb 15, 2023 | 1368 days past EOL | EOL |
| 7.7 | 7.7.4 | Jan 13, 2023 | Apr 15, 2023 | 1309 days past EOL | EOL |
| 7.8 LTS | 7.8.15 | Feb 14, 2023 | Nov 15, 2023 | 1095 days past EOL | EOL |
| 7.9 | 7.9.6 | Mar 14, 2023 | Jul 15, 2023 | 1218 days past EOL | EOL |
| 7.10 | 7.10.5 | Apr 12, 2023 | Aug 15, 2023 | 1187 days past EOL | EOL |
| 8.0 | 8.0.4 | Jul 9, 2023 | Oct 15, 2023 | 1126 days past EOL | EOL |
| 8.1 LTS | 8.1.13 | Aug 10, 2023 | May 15, 2024 | 913 days past EOL | EOL |
| 9.0 | 9.0.5 | Sep 14, 2023 | Dec 15, 2023 | 1065 days past EOL | EOL |
| 9.1 | 9.1.5 | Oct 13, 2023 | Jan 15, 2024 | 1034 days past EOL | EOL |
| 9.2 | 9.2.6 | Nov 6, 2023 | Feb 15, 2024 | 1003 days past EOL | EOL |
| 9.3 | 9.3.3 | Dec 5, 2023 | Mar 15, 2024 | 974 days past EOL | EOL |
| 9.4 | 9.4.5 | Jan 8, 2024 | Apr 15, 2024 | 943 days past EOL | EOL |
| 9.5 | 9.5.14 | Feb 2, 2024 | Nov 15, 2024 | 729 days past EOL | EOL |
| 9.6 | 9.6.3 | Mar 1, 2024 | Jun 15, 2024 | 882 days past EOL | EOL |
| 9.7 | 9.7.6 | Apr 3, 2024 | Jul 15, 2024 | 852 days past EOL | EOL |
| 9.8 | 9.8.3 | May 3, 2024 | Aug 15, 2024 | 821 days past EOL | EOL |
| 9.9 | 9.9.3 | May 31, 2024 | Sep 15, 2024 | 790 days past EOL | EOL |
| 9.10 | 9.10.3 | Jun 28, 2024 | Oct 15, 2024 | 760 days past EOL | EOL |
| 9.11 LTS | 9.11.18 | Aug 2, 2024 | May 15, 2025 | 548 days past EOL | EOL |
| 10.0 | 10.0.4 | Sep 16, 2024 | Dec 15, 2024 | 699 days past EOL | EOL |
| 10.1 | 10.1.7 | Oct 16, 2024 | Jan 15, 2025 | 668 days past EOL | EOL |
| 10.2 | 10.2.3 | Nov 15, 2024 | Feb 15, 2025 | 637 days past EOL | EOL |
| 10.3 | 10.3.4 | Dec 16, 2024 | Mar 15, 2025 | 609 days past EOL | EOL |
| 10.4 | 10.4.5 | Jan 16, 2025 | Apr 15, 2025 | 578 days past EOL | EOL |
| 10.5 LTS | 10.5.14 | Feb 16, 2025 | Nov 15, 2025 | 364 days past EOL | EOL |
| 10.6 | 10.6.6 | Mar 16, 2025 | Jun 15, 2025 | 517 days past EOL | EOL |
| 10.7 | 10.7.4 | Apr 16, 2025 | Jul 15, 2025 | 487 days past EOL | EOL |
| 10.8 | 10.8.4 | May 16, 2025 | Aug 15, 2025 | 456 days past EOL | EOL |
| 10.9 | 10.9.5 | Jun 16, 2025 | Sep 15, 2025 | 425 days past EOL | EOL |
| 10.10 | 10.10.3 | Jul 16, 2025 | Oct 15, 2025 | 395 days past EOL | EOL |
| 10.11 LTS | 10.11.26 | Aug 15, 2025 | Aug 15, 2026 | 91 days past EOL | EOL |
| 10.12 | 10.12.4 | Sep 16, 2025 | Dec 15, 2025 | 334 days past EOL | EOL |
| 11.0 | 11.0.7 | Oct 16, 2025 | Jan 15, 2026 | 303 days past EOL | EOL |
| 11.1 | 11.1.3 | Nov 14, 2025 | Feb 15, 2026 | 272 days past EOL | EOL |
| 11.2 | 11.2.4 | Dec 16, 2025 | Mar 15, 2026 | 244 days past EOL | EOL |
| 11.3 | 11.3.3 | Jan 16, 2026 | Apr 15, 2026 | 213 days past EOL | EOL |
| 11.4 | 11.4.5 | Feb 16, 2026 | May 15, 2026 | 183 days past EOL | EOL |
| 11.5 | 11.5.7 | Mar 16, 2026 | Jun 15, 2026 | 152 days past EOL | EOL |
| 11.6 | 11.6.6 | Apr 16, 2026 | Jul 15, 2026 | 122 days past EOL | EOL |
| 11.7 LTS | 11.7.15 | May 15, 2026 | May 15, 2027 | 182 days remaining | Active |
| 11.8 | 11.8.5 | Jun 16, 2026 | Sep 15, 2026 | 60 days past EOL | EOL |
| 11.9 | 11.9.2 | Jul 16, 2026 | Oct 15, 2026 | 30 days past EOL | EOL |
| 11.10 | 11.10.5 | Aug 14, 2026 | Nov 15, 2026 | 1 day remaining | Warning |
| 11.11 | 11.11.4 | Sep 16, 2026 | Dec 15, 2026 | 31 days remaining | Warning |
| 12.0 | 12.0.2 | Oct 16, 2026 | Jan 15, 2027 | 62 days remaining | Warning |
[](https://endoflife.ai/mattermost)
Mattermost release and support pattern
Across the 58 release lines with a published release date, Mattermost has shipped a new line roughly every 4 weeks (median interval). A line typically stays supported for about 3 months from its release to its end-of-life date. 9 of the 58 tracked lines are designated long-term support, which is where the longer windows sit.
Of the 58 release lines tracked, 54 are past end of life and 4 are still within support. The newest line, 12.0, was released October 16, 2026. The next scheduled end of life is 11.10 on November 15, 2026 — 0 days from this build. The longest-supported line currently published is 11.7, to May 15, 2027.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does Mattermost end of life mean for your organization?
When a version of Mattermost reaches end of life, the vendor's standard security patches for that version stop. Vulnerabilities found after that date are still published on the National Vulnerability Database, exploit code often becomes public, and systems on that version stay exposed until they are upgraded or covered by extended support.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but the vendor's policy provides no patch for the ended version. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Mattermost should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Mattermost reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, check whether the vendor or a third party sells extended support with security patches for your Mattermost version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.
Mattermost has 54 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Mattermost is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."