Drupal 7 · Version Status
Drupal 7 End of Life Date
Drupal 7 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
Drupal 7 is past end of life. This version no longer receives security patches. 671 days past EOL — migrate to a supported version immediately.
EOL Date
Jan 5, 2025
671 days past EOL
Latest Release
7.103
LTS release
Release Date
Jan 5, 2011
Drupal 7 series
Where these dates come from
End of lifeJan 5, 2025Vendor's own page, read by our adapter · drupal.org · checked Nov 7, 2026high · 2 sources agree End of active supportNov 19, 2015endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseJan 5, 2011endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Drupal 7 was released on January 5, 2011 and support ended on January 5, 2025 — a supported lifespan of 14 years, longer than the 1 year median for Drupal releases. It was a long-term support (LTS) release, so it received a longer patch window than the interim releases around it. Its most recent release is 7.103, published December 4, 2024. Standard support ended 1 year and 10 months ago. Security fixes now come only through extended support; without it this version is unpatched. 5 newer Drupal releases have shipped since.
Attack Surface
20/30 High tier
CISA KEV Exposure
20/20 Named in CISA 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 → ·
View score card →
| Version | Latest | EOL Date | Status |
|---|
| → 7 LTS |
7.103 |
Jan 5, 2025 |
EOL |
| 8.8 |
8.8.12 |
Dec 1, 2020 |
EOL |
| 8.9 |
8.9.20 |
Nov 2, 2021 |
EOL |
| 9.0 |
9.0.14 |
Jun 16, 2021 |
EOL |
| 9.1 |
9.1.15 |
Dec 8, 2021 |
EOL |
| 9.2 |
9.2.21 |
Jun 15, 2022 |
EOL |
| 9.3 |
9.3.22 |
Dec 14, 2022 |
EOL |
| 9.4 |
9.4.15 |
Jun 21, 2023 |
EOL |
What does Drupal 7 end of life mean?
When Drupal 7 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Drupal 7 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Drupal 11.4 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Drupal 7 reach end of life?
Drupal 7 reached end of life on January 5, 2025. This version is no longer receiving security patches.
Is Drupal 7 still supported?
No. Drupal 7 reached end of life on January 5, 2025 and is no longer receiving security patches.
What should I upgrade to from Drupal 7?
The recommended upgrade from Drupal 7 is
Drupal 11.4 — the latest actively supported version. Check the
Drupal full timeline for all supported versions.
What are the security risks of running Drupal 7 past EOL?
Since Drupal 7 reached end of life, the maintainers no longer issue security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Drupal should migrate immediately or implement compensating controls.