← ← Back to all products
CKEditor
Active
ApplicationsLatest Version: 48.5.1Latest Release: Sep 16, 2026
CKEditor is a smart WYSIWYG rich text editor for web content creation and collaborative editing.
Support summary
CKEditor 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
No announced EOL date is currently listed.
Supported cycles
1
1 lts
Versions
2
Latest Version
48.5.1
Active Support
1
EOL
1
Lifecycle Timeline
Nov 23, 2012As of Sep 19, 2026
5Active · Date not announced
4EOL · Jun 30, 2023
ActiveSecurityEOLHistorical phase unknown
Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 5 | Apr 25, 2018 | Maintained | Date not announced | 48.5.1 | No | Active |
| 4 | Nov 23, 2012 | Ended | Jun 30, 2023 | 4.25.1 | Yes | EOL |
Data sources
Frequently Asked Questions
Which versions of CKEditor have reached end of life?
The following CKEditor versions have reached end of life and no longer receive security updates: 4. It is recommended to upgrade to a supported version.
Is it safe to continue using CKEditor 4?
CKEditor 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 CKEditor?
The latest version of CKEditor is 48.5.1, released in the 5 release cycle.
How many versions of CKEditor are currently supported?
CKEditor currently has 1 actively supported version(s): 5.
When does CKEditor 5 reach end of life?
CKEditor 5 does not have a specific end-of-life date announced yet.
What should I do when CKEditor reaches end of life?
When a CKEditor 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.