CakePHP · Lifecycle Status

CakePHP End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all CakePHP versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

CakePHP 4.6 reaches end of life on September 9, 2026. Plan your migration now — 78 days remaining.
📅 Get reminded before CakePHP 4.6 reaches EOL on September 9, 2026 — alerts 90, 30 & 7 days out.
Google →
Latest Active
5.3.6
5.3 series
Next EOL
4.6
Sep 9, 2026
Active Versions
24
of 34 total
EOL Versions
6
no longer patched
40 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
30/40
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 →
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 20112012201320142015201620172018201920202021202220232024202520261.32.02.12.22.32.42.52.63.02.73.13.22.83.32.93.42.103.53.63.73.84.03.94.14.23.104.34.45.04.55.14.65.25.3TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
1.3 1.3.21 Apr 25, 2010 Nov 1, 2015 3887 days past EOL EOL
2.0 2.0.6 Oct 16, 2011 No EOL date Supported Active
2.1 2.1.5 Mar 4, 2012 No EOL date Supported Active
2.2 2.2.9 Jul 1, 2012 No EOL date Supported Active
2.3 2.3.10 Jan 28, 2013 No EOL date Supported Active
2.4 2.4.10 Aug 30, 2013 No EOL date Supported Active
2.5 2.5.9 May 12, 2014 No EOL date Supported Active
2.6 2.6.13 Dec 23, 2014 No EOL date Supported Active
3.0 3.0.19 Mar 22, 2015 No EOL date Supported Active
2.7 2.7.11 Jul 11, 2015 No EOL date Supported Active
3.1 3.1.14 Sep 19, 2015 Feb 13, 2017 3417 days past EOL EOL
3.2 3.2.14 Jan 29, 2016 No EOL date Supported Active
2.8 2.8.9 Feb 6, 2016 No EOL date Supported Active
3.3 3.3.16 Aug 12, 2016 No EOL date Supported Active
2.9 2.9.9 Sep 18, 2016 No EOL date Supported Active
3.4 3.4.14 Feb 12, 2017 No EOL date Supported Active
2.10 2.10.24 Jul 22, 2017 Jun 15, 2021 1834 days past EOL EOL
3.5 3.5.18 Aug 18, 2017 No EOL date Supported Active
3.6 3.6.15 Apr 14, 2018 No EOL date Supported Active
3.7 3.7.9 Dec 8, 2018 No EOL date Supported Active
3.8 3.8.13 Jun 26, 2019 No EOL date Supported Active
4.0 4.0.10 Dec 15, 2019 No EOL date Supported Active
3.9 3.9.10 Jun 20, 2020 No EOL date Supported Active
4.1 4.1.7 Jul 4, 2020 No EOL date Supported Active
4.2 4.2.12 Dec 20, 2020 Oct 14, 2023 983 days past EOL EOL
3.10 3.10.5 Jun 19, 2021 Dec 15, 2022 1286 days past EOL EOL
4.3 4.3.11 Oct 23, 2021 Sep 9, 2026 78 days remaining Warning
4.4 4.4.18 Jun 6, 2022 Sep 9, 2026 78 days remaining Warning
5.0 5.0.11 Sep 9, 2023 Jan 9, 2026 165 days past EOL EOL
4.5 4.5.11 Oct 14, 2023 Sep 9, 2026 78 days remaining Warning
5.1 5.1.7 Sep 13, 2024 TBD Supported Active
4.6 4.6.4 Mar 22, 2025 Sep 9, 2026 78 days remaining Warning
5.2 5.2.13 Mar 29, 2025 TBD Supported Active
5.3 5.3.6 Jan 9, 2026 TBD Supported Active

What does CakePHP end of life mean for your organization?

When a version of CakePHP 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 CakePHP 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 CakePHP versions. This is a bridge, not a permanent solution — plan your migration in parallel.

endoflife.ai
Need Extended Support?

We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.

Contact Us →
Frequently Asked Questions
What is the end-of-life date for CakePHP?
The next CakePHP version reaching EOL is 4.6 on September 9, 2026. See the full table above for all version EOL dates.
When is the CakePHP support end date?
The next CakePHP support end date is September 9, 2026, when version 4.6 reaches end of support. Each version has its own support end date — see the table above for every version's date.
What is the latest supported version of CakePHP?
The latest active version of CakePHP is 5.3.6. Always verify against the table above as support windows can change.
What happens when CakePHP reaches end of life?
When CakePHP reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of CakePHP?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL CakePHP versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →