Drupal End of Life Dates
cms
Developers rely on a robust content management system to build and maintain complex websites, and one popular choice is a free and open-source web content management system written in PHP. This system, created in 2001, is maintained by the Drupal Association, a non-profit organization dedicated to supporting the project. With its modular design and extensive community support, it provides an open-source back-end framework for at least 14% of the top 10,000 websites worldwide, making it a widely adopted solution for web development. The system's popularity stems from its flexibility, scalability, and customizability, allowing developers to tailor it to their specific needs.
The end-of-life landscape for this content management system is complex, with a total of 20 versions released over the years. Currently, 16 versions are no longer supported, while 4 versions remain active. The latest stable version, 10.5.11, is still receiving updates, but version 10.5 is set to reach its end-of-life on 2026-06-17. This means that developers using version 10.5 should start planning their upgrade to a newer version to ensure continued support and security updates. The last version to reach its end-of-life was 10.4, which occurred on 2025-12-10, highlighting the importance of staying up-to-date with the latest versions.
The security picture for this content management system is a concern, with a total of 57 CVEs tracked, including 18 critical vulnerabilities. The most affected version is 11.3, with 4 CVEs, emphasizing the need for developers to prioritize security updates and patches. To mitigate potential risks, developers should regularly review the security advisories and update their installations to the latest versions. By doing so, they can ensure the security and integrity of their websites, protecting against potential exploits and vulnerabilities. With the next end-of-life date approaching, developers should take proactive steps to upgrade their installations and stay ahead of potential security threats.
Last updated: Sep 7, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 11.4 | Jul 1, 2026 | Jan 1, 2027 | Jul 7, 2027 | in 303d | 11.4.6 | — | Active | |
| 10.6 | Dec 17, 2025 | Jun 16, 2026 | Dec 16, 2026 | in 100d | 10.6.16 | Active | ||
| 11.3 | Dec 17, 2025 | Jun 16, 2026 | Dec 16, 2026 | in 100d | 11.3.16 | Active | ||
| 11.2 | Jun 18, 2025 | Dec 10, 2025 | Jun 17, 2026 | 82d ago | 11.2.14 | EOL | ||
| 10.5 | Jun 18, 2025 | Dec 17, 2025 | Jun 17, 2026 | 82d ago | 10.5.12 | EOL | ||
| 10.4 | Dec 17, 2024 | Jun 18, 2025 | Dec 10, 2025 | 271d ago | 10.4.10 | EOL | ||
| 11.1 | Dec 16, 2024 | Jun 18, 2025 | Dec 10, 2025 | 271d ago | 11.1.10 | EOL | ||
| 11.0 | Aug 2, 2024 | Dec 16, 2024 | Jun 16, 2025 | 448d ago | 11.0.13 | EOL | ||
| 10.3 | Jun 20, 2024 | Aug 2, 2024 | Jun 16, 2025 | 448d ago | 10.3.14 | EOL | ||
| 10.2 | Dec 15, 2023 | Jun 20, 2024 | Dec 17, 2024 | 629d ago | 10.2.12 | EOL | ||
| 10.1 | Jun 22, 2023 | Dec 15, 2023 | Jun 20, 2024 | 809d ago | 10.1.8 | EOL | ||
| 9.5 | Dec 15, 2022 | Jun 21, 2023 | Nov 1, 2023 | 1041d ago | 9.5.11 | EOL | ||
| 10.0 | Dec 15, 2022 | Jun 21, 2023 | Dec 15, 2023 | 997d ago | 10.0.11 | EOL | ||
| 9.4 | Jun 15, 2022 | Dec 14, 2022 | Jun 21, 2023 | 1174d ago | 9.4.15 | EOL | ||
| 9.3 | Dec 8, 2021 | Jun 15, 2022 | Dec 14, 2022 | 1363d ago | 9.3.22 | EOL | ||
| 9.2 | Jun 16, 2021 | Dec 8, 2021 | Jun 15, 2022 | 1545d ago | 9.2.21 | EOL | ||
| 9.1 | Dec 2, 2020 | Jun 16, 2021 | Dec 8, 2021 | 1734d ago | 9.1.15 | EOL | ||
| 8.9 | Jun 3, 2020 | Dec 1, 2020 | Nov 2, 2021 | 1770d ago | 8.9.20 | EOL | ||
| 9.0 | Jun 3, 2020 | Dec 2, 2020 | Jun 16, 2021 | 1909d ago | 9.0.14 | EOL | ||
| 8.8 | Dec 4, 2019 | Jun 3, 2020 | Dec 1, 2020 | 2106d ago | 8.8.12 | EOL | ||
| 7 LTS | Jan 5, 2011 | Nov 19, 2015 | Jan 5, 2025 | 610d ago | 7.103 | EOL |
Data sourced from endoflife.date · CVE data from NVD
