Matomo 2 · Version Status
Matomo 2 End of Life Date
Matomo 2 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
Matomo 2 is past end of life. This version no longer receives security patches. 3246 days past EOL — migrate to a supported version immediately.
EOL Date
Dec 18, 2017
3246 days past EOL
Latest Release
2.18.1
Standard release
Release Date
Dec 17, 2013
Matomo 2 series
Where these dates come from
End of lifeDec 18, 2017endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees End of active supportDec 19, 2016endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseDec 17, 2013endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Matomo 2 was released on December 17, 2013 and support ended on December 18, 2017 — a supported lifespan of 4 years, in line with the 4 years and 1 month median for Matomo releases. Its latest release on record is 2.18.1, published July 1, 2020 — 2 years and 7 months after the published end-of-life date. It has been past its end-of-life date for 8 years and 11 months. 2 newer Matomo releases have shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended Matomo 2 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| 1 |
1.12 |
Dec 17, 2013 |
EOL |
| → 2 |
2.18.1 |
Dec 18, 2017 |
EOL |
| 3 |
3.14.1 |
Dec 1, 2021 |
EOL |
| 4 |
4.16.2 |
Dec 19, 2024 |
EOL |
| 5 |
5.14.2 |
EOL |
Active |
What does Matomo 2 end of life mean?
When Matomo 2 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Matomo 2 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Matomo 5 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Matomo 2 reach end of life?
Matomo 2 reached end of life on December 18, 2017. This version is no longer receiving security patches.
Is Matomo 2 still supported?
No. Matomo 2 reached end of life on December 18, 2017 and is no longer receiving security patches.
What should I upgrade to from Matomo 2?
The recommended upgrade from Matomo 2 is
Matomo 5 — the latest actively supported version. Check the
Matomo full timeline for all supported versions.
What are the security risks of running Matomo 2 past EOL?
Since Matomo 2 reached end of life, the maintainers no longer issue security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Matomo should migrate immediately or implement compensating controls.