Matomo End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Matomo versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1 | 1.12 | Aug 28, 2010 | Dec 17, 2013 | 4571 days past EOL | EOL |
| 2 | 2.18.1 | Dec 17, 2013 | Dec 18, 2017 | 3109 days past EOL | EOL |
| 3 | 3.14.1 | Dec 19, 2016 | Dec 1, 2021 | 1665 days past EOL | EOL |
| 4 | 4.16.2 | Nov 24, 2020 | Dec 19, 2024 | 551 days past EOL | EOL |
| 5 | 5.11.2 | Dec 18, 2023 | TBD | Supported | Active |
What does Matomo end of life mean for your organization?
When a version of Matomo reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Matomo 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Matomo versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →