Statamic 5 · Version Status
Statamic 5 End of Life Date
Statamic 5 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.
⚡
Statamic 5 reaches end of life in December 2026. Plan your migration now (the vendor names the month only).
📅 Get reminded before Statamic 5 reaches EOL in December 2026 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Dec 2026
EOL in December 2026
Latest Release
5.74.7
Standard release
Release Date
May 9, 2024
Statamic 5 series
Where these dates come from
End of lifeDec 2026Vendor's own page, checked by a person · statamic.dev · checked Nov 1, 2026high · 2 sources agree End of active supportMar 2026Vendor's own page, checked by a person · statamic.dev · checked Nov 1, 2026high · 2 sources agree ReleaseMay 9, 2024Vendor's own page, checked by a person · statamic.dev · checked Nov 1, 2026high · 2 sources agree 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
Statamic 5 was released on May 9, 2024 and support is scheduled to end in December 2026 — a planned supported lifespan of 2 years and 8 months, longer than the 1 year and 7 months median for Statamic releases. Its most recent patch is 5.74.7, published October 22, 2026.
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 Statamic 5 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 |
|---|
| 3.3 |
3.3.68 |
Sep 30, 2023 |
EOL |
| 3.4 |
3.4.17 |
Jul 2024 |
EOL |
| 4 |
4.58.3 |
Sep 2024 |
EOL |
| → 5 |
5.74.7 |
Dec 2026 |
Warning |
| 6 |
6.40.0 |
Dec 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: 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 Statamic 5 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
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 reaches end of life in December 2026. The vendor publishes the month only, not a day.
Is Statamic 5 still supported?
Statamic 5 is still supported but approaching end of life in December 2026. Begin planning your migration now.
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 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 Statamic should migrate immediately or implement compensating controls.