Drupal End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Drupal versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 7 LTS | 7.103 | Jan 5, 2011 | Jan 5, 2025 | 554 days past EOL | EOL |
| 8.8 | 8.8.12 | Dec 4, 2019 | Dec 1, 2020 | 2050 days past EOL | EOL |
| 8.9 | 8.9.20 | Jun 3, 2020 | Nov 2, 2021 | 1714 days past EOL | EOL |
| 9.0 | 9.0.14 | Jun 3, 2020 | Jun 16, 2021 | 1853 days past EOL | EOL |
| 9.1 | 9.1.15 | Dec 2, 2020 | Dec 8, 2021 | 1678 days past EOL | EOL |
| 9.2 | 9.2.21 | Jun 16, 2021 | Jun 15, 2022 | 1489 days past EOL | EOL |
| 9.3 | 9.3.22 | Dec 8, 2021 | Dec 14, 2022 | 1307 days past EOL | EOL |
| 9.4 | 9.4.15 | Jun 15, 2022 | Jun 21, 2023 | 1118 days past EOL | EOL |
| 9.5 | 9.5.11 | Dec 15, 2022 | Nov 1, 2023 | 985 days past EOL | EOL |
| 10.0 | 10.0.11 | Dec 15, 2022 | Dec 15, 2023 | 941 days past EOL | EOL |
| 10.1 | 10.1.8 | Jun 22, 2023 | Jun 20, 2024 | 753 days past EOL | EOL |
| 10.2 | 10.2.12 | Dec 15, 2023 | Dec 17, 2024 | 573 days past EOL | EOL |
| 10.3 | 10.3.14 | Jun 20, 2024 | Jun 16, 2025 | 392 days past EOL | EOL |
| 11.0 | 11.0.13 | Aug 2, 2024 | Jun 16, 2025 | 392 days past EOL | EOL |
| 11.1 | 11.1.10 | Dec 16, 2024 | Dec 10, 2025 | 215 days past EOL | EOL |
| 10.4 | 10.4.10 | Dec 17, 2024 | Dec 10, 2025 | 215 days past EOL | EOL |
| 10.5 | 10.5.12 | Jun 18, 2025 | Jun 17, 2026 | 26 days past EOL | EOL |
| 11.2 | 11.2.14 | Jun 18, 2025 | Jun 17, 2026 | 26 days past EOL | EOL |
| 10.6 | 10.6.12 | Dec 17, 2025 | Dec 16, 2026 | 156 days remaining | Warning |
| 11.3 | 11.3.13 | Dec 17, 2025 | Dec 16, 2026 | 156 days remaining | Warning |
| 11.4 | 11.4.2 | Jul 1, 2026 | Jul 7, 2027 | 359 days remaining | Active |
What does Drupal end of life mean for your organization?
When a version of Drupal 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 Drupal 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 Drupal versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Drupal has 18 versions past end of life — security patches have stopped, but CVE disclosures haven't. Tell us what you run and we'll match you with a vetted extended-support provider within 1 business day. Free, no obligation.
Get My Support Options →