← ← Back to all products
Craft CMS
Active
CMS & ContentLatest Version: 5.10.14Latest Release: Aug 18, 2026
Craft CMS is a flexible, user-friendly content management system for building custom digital experiences.
Support summary
Craft CMS currently has supported cycles. Track the next EOL date and validate upgrades before your change window.
What do EOL and support statuses mean?Next EOL
Dec 31, 2031
Craft CMS 5 · 1958 days left
Supported cycles
1
0 lts
Versions
4
Latest Version
5.10.14
Active Support
1
EOL
3
Lifecycle Timeline
Today ↓
5
5
4
4
3
3
2
2
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 5 | Mar 26, 2024 | Dec 31, 2030 | Dec 31, 2031 | 5.10.14 | No | Active |
| 4 | May 4, 2022 | Apr 30, 2025 | Apr 30, 2026 | 4.18.7 | No | EOL |
| 3 | Apr 4, 2018 | Apr 30, 2023 | Apr 30, 2024 | 3.9.15 | No | EOL |
| 2 | Apr 1, 2014 | Jan 31, 2020 | Jan 31, 2022 | 2.9.2 | No | EOL |
Data sources
Frequently Asked Questions
Which versions of Craft CMS have reached end of life?
The following Craft CMS versions have reached end of life and no longer receive security updates: 4, 3, 2. It is recommended to upgrade to a supported version.
Is it safe to continue using Craft CMS 4?
Craft CMS 4 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Craft CMS?
The latest version of Craft CMS is 5.10.14, released in the 5 release cycle.
How many versions of Craft CMS are currently supported?
Craft CMS currently has 1 actively supported version(s): 5.
When does Craft CMS 5 reach end of life?
Craft CMS 5 is scheduled to reach end of life on Dec 31, 2031.
What should I do when Craft CMS reaches end of life?
When a Craft CMS version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.