EOL.WikiEOL.Wiki
← ← Back to all products

Plone

Security
CMS & ContentLatest Version: 6.2.1Latest Release: Jun 26, 2026

Plone is a powerful open-source CMS built on Python and Zope, known for security and extensibility.

Support summary

Plone has cycles in security-only maintenance. Production workloads should move toward actively supported releases.

What do EOL and support statuses mean?

Next EOL

Dec 31, 2027

Plone 6.2 · 497 days left

Supported cycles

3

0 lts

Versions

7

Latest Version

6.2.1

Active Support

0

EOL

4

Lifecycle Timeline

Today
6.2
6.2
6.1
6.1
6.0
6.0
5.2
5.2
5.1
5.1
5.0
5.0
4.3
4.3
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
6.2May 19, 2026Jun 26, 2026Dec 31, 20276.2.1No
Security
6.1Feb 7, 2025Jun 25, 2026Dec 31, 20276.1.5No
Security
6.0Dec 12, 2022Mar 27, 2025Dec 31, 20276.0.15No
Security
5.2Jul 10, 2019Oct 31, 2023Oct 31, 20245.2.15No
EOL
5.1Feb 5, 2018Oct 2, 2020Dec 12, 20225.1.7No
EOL
5.0Sep 27, 2015Feb 7, 2019Dec 12, 20225.0.10No
EOL
4.3Apr 6, 2013Aug 28, 2020Dec 12, 20224.3.20No
EOL

Data sources

Frequently Asked Questions

Which versions of Plone have reached end of life?
The following Plone versions have reached end of life and no longer receive security updates: 5.2, 5.1, 5.0, 4.3. It is recommended to upgrade to a supported version.
Is it safe to continue using Plone 5.2?
Plone 5.2 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 Plone?
The latest version of Plone is 6.2.1, released in the 6.2 release cycle.
How many versions of Plone are currently supported?
Plone currently has 3 actively supported version(s): 6.2, 6.1, 6.0.
When does Plone 6.2 reach end of life?
Plone 6.2 is scheduled to reach end of life on Dec 31, 2027.
What should I do when Plone reaches end of life?
When a Plone 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.