End of life

Drupal 7 end of life

Drupal 7 reached end of life on 5 January 2025, and drupal.org says it no longer receives security updates. The last release was 7.103, published on 4 December 2024 with no security fixes. You can migrate to Drupal 11, buy extended security support from a Drupal Association certified vendor, or keep Drupal 7 patched with OSSeva.

What now

Which vendors provide Drupal 7 security patches now that support has ended?

Drupal extended support

Only your email is required · An engineer replies within 1 business day · No commitment

End of life
5 January 2025
Released
Jan 2011
Final release
7.103 (4 December 2024)
Successor
Drupal 11

Date published by drupal.org: Drupal 7 end of life. We do not publish a lifecycle date we cannot source. Dates checked on drupal.org and endoflife.date on 19 November 2026.

Last reviewed

Drupal versions: release and end-of-life dates

Drupal release and end-of-life dates
VersionReleasedEnd of lifeStatus
Drupal 7 (this page)5 Jan 20115 January 2025End of life

End-of-life dates are published by each project and checked against endoflife.date.

What actually stops on 5 January 2025

  • Security updates for Drupal 7. The drupal.org end-of-life page says Drupal 7 will no longer receive security updates or compatibility updates.
  • Security advisories for core and contributed projects. The Drupal Security Team's 2019 announcement (PSA-2019-02-25) said it would stop providing both, and warned that reports about Drupal 7 vulnerabilities might become public.
  • Releases after 7.103. drupal.org describes 7.103, from 4 December 2024, as a maintenance release that contains no security fixes.
  • Compatibility work for newer PHP. 7.103 is the first Drupal 7 release to pass tests on PHP 8.3, and drupal.org says PHP 8.4 will not get support.

What actually breaks in the upgrade

Land on Drupal 11, not Drupal 10

The drupal.org release schedule gives 9 December 2026 as the end of life of Drupal 10 and early December 2028 for Drupal 11. A migration that starts now and lands on Drupal 10 would arrive at an end-of-life date within weeks. drupal.org points Drupal 7 sites to its certified migration partners and a migration resource center.

Drupal 7 runs on PHP 5.6 to 8.3 only

drupal.org's PHP requirements page lists PHP 5.6 as the minimum and PHP 8.3 as the maximum for Drupal 7, and says 8.4 will not get support. The PHP underneath a Drupal 7 site has its own end-of-life dates: PHP 7.4 ended in November 2022, 8.1 in December 2025 and 8.3 security support ends on 31 December 2027, per php.net. Patching Drupal without patching PHP leaves the older half of the stack open. PHP extended support for 7.4 to 8.3.

The compliance clock runs from the end-of-life date

drupal.org's own end-of-life page warns that unaddressed Drupal 7 issues can put a site out of compliance with FedRAMP, PCI, HIPAA and SOC 2. It tells sites that cannot migrate to inform customers, managers and CISOs of their plan for managing vulnerabilities.

What the last Drupal 7 release and the PHP ceiling mean together

Drupal 7 has two ceilings that most other end-of-life products do not. The first is the release itself: 7.103, published on 4 December 2024, was the last Drupal 7 release from the project, and drupal.org's release page describes it as a maintenance release with bug fixes and small API improvements and no security fixes. There is therefore no "last security release" to pin to. A Drupal 7 site on 7.103 has every fix the project ever shipped, and none after.

The second ceiling is PHP. 7.103 is the first Drupal 7 release to pass tests on PHP 8.3, and drupal.org's requirements page lists 8.3 as the maximum and says 8.4 will not get support. A Drupal 7 site cannot follow PHP forward past 8.3, whose security support ends on 31 December 2027 per php.net. The earlier lines are worse: PHP 7.4 ended in November 2022 and 8.1 in December 2025.

That is why Drupal 7 patching has to cover two layers. A patched core on an unpatched PHP still exposes the interpreter, and a patched PHP under an unpatched core still exposes the modules. OSSeva patches PHP 7.4 and 8.1 to 8.3 after end of life as well as Drupal 7, so the same engagement can cover both. Check which PHP your site runs before you decide: the answer decides whether the PHP upgrade can happen first and take a layer of risk out while the migration is planned.

The practical order for most sites is: confirm the PHP version, move it to 8.1 to 8.3 if the modules allow it, put patching on the Drupal 7 core and modules in place, and then plan the migration to Drupal 11 on a schedule that no longer depends on a security deadline.

Drupal 7 extended support and the Drupal Association program

drupal.org's Drupal 7 end-of-life page, read on 19 November 2026, describes an Extended Security Support Provider Program and names two certified vendors: HeroDevs and Tag1 Consulting. It presents buying extended security support from a certified vendor as the option for sites that cannot migrate before the deadline.

OSSeva also keeps Drupal 7 patched for sites that need it to keep receiving security fixes while they plan the migration.

Who patches Drupal 7 after end of life?

The Drupal Security Team does not. Two vendors are named on drupal.org as certified, and OSSeva also patches Drupal 7. Only HeroDevs' own page is quoted below; Tag1's page was not read.

Facts from drupal.org and from HeroDevs' own page, read on 19 November 2026.

ProviderWhat the source saysFix timing the page states
HeroDevs (NES for Drupal)Listed by drupal.org as a certified vendor. Its page offers drop-in replacements for Drupal 7.xSecurity-related and application-breaking issues resolved immediately, same day if possible
Tag1 ConsultingListed by drupal.org as a certified vendor. Its own page was not read for this comparisonNot listed
OSSevaDrupal 7 patches, plus patched PHP 7.4 and 8.1 to 8.3Critical within 48 hours, High within 7 days

How we compared: the certified-vendor names come from drupal.org's end-of-life page, read on 19 November 2026, and the HeroDevs row from its own Drupal page. The timing statements are different measures (a response commitment and a patch window). Check each vendor's page for current terms.

Your options, costed honestly

Including the ones that do not involve buying anything from us.

OptionWhat it isEffortCostOur view
Migrate to Drupal 11Rebuild or migrate content, configuration and custom modules onto a supported major, supported to early December 2028.Scales with content model, custom modules and contributed modulesEngineering timeThe long-term answer.
Certified extended security supportdrupal.org lists HeroDevs and Tag1 Consulting as the certified vendors in its Extended Security Support Provider Program.Starts from your current versionSubscriptionRight if your contract or auditor asks for a Drupal Association certified vendor.
Keep Drupal 7 patched with OSSevaBackported security fixes for Drupal 7: Critical within 48 hours, High within 7 days, plus patched PHP 7.4 and 8.1 to 8.3 underneath.Starts from your current versionSubscription, priced per applicationFor sites that cannot migrate this year.
Stay unpatchedNo security updates for Drupal 7, and new flaws are not announced by the Drupal Security Team.NoneZero nowA poor place to carry risk for a site reachable from the internet.

What OSSeva does for Drupal 7

OSSeva patches this line

OSSeva patches Drupal 7 after end of life, and the 10.5 and 11.2 lines that have left security coverage. Other Drupal versions are assessed case by case through a version coverage check.

Drupal extended support

What your auditor will say

PCI DSS 4.0

Requirement 6.3.3. Payment pages and checkout flows on Drupal 7 need patched components or a documented compensating control.

SOC 2

CC7.1. Auditors look for evidence that production applications receive security fixes.

FedRAMP and HIPAA

drupal.org's end-of-life page names both as standards a Drupal 7 site can fall out of compliance with once security updates stop.

Compliance library Drupal end of life dates for every version

Questions

Drupal 7: common questions

Book a 15-minute call

Is Drupal 7 end of life?

Yes. drupal.org lists its end of life as 5 January 2025 and says Drupal 7 no longer receives security updates or compatibility updates.

What is the last Drupal 7 version?

7.103, published on 4 December 2024. drupal.org describes it as a maintenance release with no security fixes, and the first Drupal 7 release to pass tests on PHP 8.3.

Which PHP version does Drupal 7 support?

PHP 5.6 as the minimum and PHP 8.3 as the maximum, per drupal.org. PHP 8.4 will not get support. OSSeva patches PHP 7.4 and 8.1 to 8.3 after end of life.

Who provides Drupal 7 support after end of life?

Not the Drupal Security Team. drupal.org's end-of-life page names HeroDevs and Tag1 Consulting as the certified vendors in its Extended Security Support Provider Program. OSSeva also patches Drupal 7: Critical fixes within 48 hours, High within 7 days.

Should I upgrade Drupal 7 to Drupal 10 or 11?

Drupal 11. drupal.org gives 9 December 2026 as the end of life of Drupal 10 and early December 2028 for Drupal 11.

Does Drupal 7 still get security advisories?

No. The Drupal Security Team announced in 2019 that it would stop issuing advisories for Drupal 7 core and contributed projects at end of life, so a new flaw is not announced there.

Get a quote

Still running Drupal 7?

Tell us the versions and the estate size. We will tell you honestly whether to upgrade or to buy cover — and we say 'upgrade' more often than you would expect.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call