Statamic 5 · Version Status
Statamic 5 End of Life Date
Statamic 5 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
✓
Statamic 5 is actively supported. EOL date: December 31, 2026.
EOL Date
Dec 31, 2026
236 days remaining
Latest Release
5.73.21
Standard release
Release Date
May 9, 2024
Statamic 5 series
| Version | Latest | EOL Date | Status |
|---|
| 3.3 |
3.3.68 |
Sep 30, 2023 |
EOL |
| 3.4 |
3.4.17 |
Jul 31, 2024 |
EOL |
| 4 |
4.58.3 |
Sep 30, 2024 |
EOL |
| → 5 |
5.73.21 |
Dec 31, 2026 |
Active |
| 6 |
6.18.0 |
Dec 31, 2027 |
Active |
What does Statamic 5 end of life mean?
When Statamic 5 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: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Statamic 5 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Statamic 6 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Statamic 5 reach end of life?
Statamic 5 reached end of life on December 31, 2026. That is 236 days remaining.
Is Statamic 5 still supported?
Yes, Statamic 5 is currently supported. The EOL date is December 31, 2026.
What should I upgrade to from Statamic 5?
The recommended upgrade from Statamic 5 is
Statamic 6 — the latest actively supported version. Check the
Statamic full timeline for all supported versions.
What are the security risks of running Statamic 5 past EOL?
When Statamic 5 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Statamic should migrate immediately or implement compensating controls.