EOL Software
Oct 26, 2026

PHP End-of-Life Dates: Support Timeline for Every Version (2026)

The definitive reference for every PHP release, support window, and end-of-life date, plus what EOL means for the millions of applications still running unsupported versions.

Give me the TL;DR
PHP End-of-Life Dates: Support Timeline for Every Version (2026)

As of October 2026, PHP 8.2, 8.3, 8.4, and 8.5 are supported, the latest release is PHP 8.5.12, and PHP 8.2 reaches end of life on December 31, 2026.

  • Latest version: PHP 8.5.12 (October 21, 2026). PHP 8.6 releases November 19, 2026.
  • End-of-life dates: PHP 8.2 on December 31, 2026; 8.3 on December 31, 2027; 8.4 on December 31, 2028; 8.5 on December 31, 2029. PHP 8.1 and every older branch are already end-of-life.
  • Recommended for production: PHP 8.4 or newer, on the latest patch for your branch. See Latest PHP Releases by Branch.
  • PHP2Shell (CVE-2026-109618, CVE-2026-109619): fixed in 8.2.35, 8.3.36, 8.4.27, and 8.5.12. No upstream release for 8.1 or older. Patched runtimes for EOL branches are available through NES for PHP. Details below.

PHP powers roughly 75% of all websites with a known server-side programming language, according to W3Techs. WordPress alone, which runs on PHP, accounts for over 43% of all websites on the internet. Drupal, Joomla, Laravel, Symfony, Magento: the PHP ecosystem is enormous, and a significant portion of it is running on versions that no longer receive security patches.

This page is the definitive reference for PHP's release and support lifecycle: every version's release date, end-of-life date, and latest patch, plus the security risks of running EOL PHP and the options for teams that cannot upgrade immediately. It is updated as new versions ship.

How PHP's Support Policy Works

The PHP project follows a predictable release and support cycle. A new feature version (e.g., 8.5) ships once per year, typically in late November. Each version then moves through three phases:

  • Active Support (2 years): Bug fixes, security patches, and regular point releases.
  • Security Support (2 years): Only critical security patches. No bug fixes or new features.
  • End of Life: No further updates of any kind. No security patches. No bug fixes.

This gives each PHP version a four-year total support window. Prior to September 2024, the cycle was shorter: two years of active support followed by only one year of security fixes, for a three-year total. The PHP project extended the security support period to two years and aligned all end-of-support dates to December 31 of the relevant year. PHP 8.1 was the first version to benefit from the extended timeline, with its EOL shifting from November 2024 to December 31, 2025.

PHP has no separate LTS track. Every release gets the same four-year window, and the PHP project does not extend it for any version.

Note: PHP 6 was never released. A planned Unicode-native rewrite of PHP was abandoned, and development jumped from PHP 5.x directly to PHP 7.0.

Complete PHP Version Timeline

PHP Version Support Lifecycle

PHP Version Support Lifecycle
Version Release Date Active Support Until Security Support Until (EOL) Latest Release Status
8.6 Nov 19, 2026 (scheduled) Dec 31, 2028 (projected) Dec 31, 2030 (projected) Pre-release until GA Upcoming (GA Nov 19, 2026)
8.5 Nov 20, 2025 Dec 31, 2027 Dec 31, 2029 8.5.12 (Oct 21, 2026) Active
8.4 Nov 21, 2024 Dec 31, 2026 Dec 31, 2028 8.4.27 (Oct 21, 2026) Active
8.3 Nov 23, 2023 Dec 31, 2025 Dec 31, 2027 8.3.36 (Oct 21, 2026) Security Only
8.2 Dec 8, 2022 Dec 31, 2024 Dec 31, 2026 8.2.35 (Oct 21, 2026) Security Only (EOL Dec 31, 2026)
8.1 Nov 25, 2021 Nov 25, 2023 Dec 31, 2025 8.1.34 (Dec 18, 2025) EOL
8.0 Nov 26, 2020 Nov 26, 2022 Nov 26, 2023 8.0.30 EOL
7.4 Nov 28, 2019 Nov 28, 2021 Nov 28, 2022 7.4.33 EOL
7.3 Dec 6, 2018 Dec 6, 2020 Dec 6, 2021 7.3.33 EOL
7.2 Nov 30, 2017 Nov 30, 2019 Nov 30, 2020 7.2.34 EOL
7.1 Dec 1, 2016 Dec 1, 2018 Dec 1, 2019 7.1.33 EOL
7.0 Dec 3, 2015 Dec 3, 2017 Jan 10, 2019 7.0.33 EOL
5.6 Aug 28, 2014 Dec 31, 2016 Dec 31, 2018 5.6.40 EOL
5.5 Jun 20, 2013 Jul 10, 2015 Jul 21, 2016 5.5.38 EOL
5.4 Mar 1, 2012 Sep 14, 2014 Sep 3, 2015 5.4.45 EOL

PHP 8.6 dates are projected from the PHP release cycle policy and will be confirmed at GA.

Latest PHP Releases by Branch

Current as of October 24, 2026. The PHP project shipped an out-of-cycle security release for every supported branch on October 21, 2026, so these are the minimum versions to be running. Newer patch releases may have shipped since; php.net/downloads always lists the current ones.

Latest PHP Releases by Branch
Branch Latest Release Release Date Notes
8.5 8.5.12 Oct 21, 2026 Fixes PHP2Shell (CVE-2026-109618, CVE-2026-109619)
8.4 8.4.27 Oct 21, 2026 Fixes PHP2Shell
8.3 8.3.36 Oct 21, 2026 Fixes PHP2Shell
8.2 8.2.35 Oct 21, 2026 Fixes PHP2Shell; 8.2 receives no security fixes after Dec 31, 2026
8.6 8.6.0 RC4 Oct 21, 2026 Pre-release, not for production; includes the PHP2Shell fixes

Run php -v to check what you have. If your PHP comes from a Linux distribution, the version string may not tell the whole story: distributions often backport fixes under an older-looking version number, so check your package changelog for the CVE IDs rather than relying on the version alone.

PHP2Shell (CVE-2026-109618 and CVE-2026-109619): Which PHP Versions Are Fixed

PHP2Shell is the name researchers gave to two critical, unauthenticated remote code execution flaws in PHP core, disclosed and fixed on October 21, 2026 after details leaked the day before. CVE-2026-109618 corrupts request memory when PHP bails out of an out-of-memory error. CVE-2026-109619 is a use after free caused by global state that survives from one request to the next on the same worker. The PHP project rates both 9.2 under CVSS 4.0. NVD's CVSS 3.1 scores, which many scanners display, are 9.8 and 8.1 respectively.

The advisories list every PHP release before 8.2.35 as affected, which takes in every end-of-life branch. Here is where each version stands upstream:

PHP2Shell (CVE-2026-109618, CVE-2026-109619) fix status by PHP version
PHP Version Upstream Status PHP2Shell Fix From the PHP Project
8.5 Active 8.5.12
8.4 Active 8.4.27
8.3 Security only 8.3.36
8.2 Security only until Dec 31, 2026 8.2.35
8.1 EOL No release; minimal source backport only
8.0 EOL No release; minimal source backport only
7.4 EOL No release; minimal source backport only
7.3 and older (including 5.x) EOL No release, no backport

To answer the question directly: there is no PHP 7.4.34, 8.0.31, or 8.1.35 from the PHP project, and none is coming. Because of the severity, the PHP security team published minimal source backports for 7.4, 8.0, and 8.1 for people who compile PHP themselves. Servers that install PHP from packages only get those fixes if their vendor ships them.

That end-of-life population is large. Mallory's Shodan count on October 21, 2026 found about 2.6 million internet-facing services reporting a PHP version, and roughly 73.5% of them reported PHP 8.1 or older. Version banners are an imperfect proxy, but the order of magnitude is not in doubt.

Exploitation status. Amazon Threat Intelligence logged a probe on October 17, four days before disclosure, and exploit attempts began hours before the fixes shipped. watchTowr and Cloudflare both reported attack traffic on October 21.

Mitigations if you cannot update yet. The PHP project is explicit that updating is the only complete fix. The advisory's stopgaps reduce exposure to the known attack paths but do not make an installation safe:

  • CVE-2026-109618: set memory_limit=-1 administratively and restart every worker; do not substitute RLIMIT_AS or RLIMIT_DATA; keep post_max_size conservative and enforce request size limits at the web server or proxy.
  • CVE-2026-109619: set session.upload_progress.enabled=0 in php.ini or the FPM pool (not via ini_set() or .user.ini) and restart every worker. On PHP 8.5, also set fatal_error_backtraces=0.

For end-of-life branches, the realistic options are a supported upgrade (8.2.35 is the minimum fixed version, but with 8.2 reaching EOL on December 31, 2026, 8.4 or 8.5 is the better target), building from the source backports, or a patched runtime from a vendor. HeroDevs Never-Ending Support (NES) for PHP ships PHP2Shell-patched runtimes for PHP 5.6, 7.1, 7.2, 7.3, 7.4, 8.0, 8.1, and 8.2, including the 7.3-and-older branches that got no upstream backport at all, as drop-in packages for the version you already run.

For the full technical breakdown of both bugs, attack paths, and mitigations, see our PHP2Shell deep-dive. For how the fix came together in under a day, read the PHP2Shell story.

Versions Reaching EOL Next: What to Watch

PHP 8.2 End of Life: December 31, 2026

PHP 8.2 is in its security-only support phase and reaches end of life on December 31, 2026. Active support (bug fixes) ended on December 31, 2024, so the only updates 8.2 receives now are critical security patches. The last of those may well be 8.2.35, the PHP2Shell release; the 8.2.35 release notes state that 8.2 "will receive no further security fixes after that date."

PHP 8.2 introduced readonly classes, disjunctive normal form types, standalone null, false, and true types, and deprecated dynamic properties. It remains widely deployed, particularly across WordPress hosting environments that were slow to adopt 8.3 and 8.4.

PHP2Shell is a preview of what 2027 looks like for 8.2. This time 8.2 got a release. The next critical PHP CVE disclosed after December 31 will be fixed in 8.3 and newer only, and 8.2 will join 8.1 in the "source backport if you're lucky" column. Teams on 8.2 need an upgrade, or another source of patches, in place before December 31, 2026.

PHP 8.4: Active Support Ends December 31, 2026

PHP 8.4 moves from active support to security-only support on the same day 8.2 reaches EOL. Nothing breaks, and 8.4 remains supported for security fixes through December 31, 2028, but routine bug fixes stop at the end of 2026. PHP 8.4 is still a sound production target.

PHP 8.3: Security Support Until December 31, 2027

PHP 8.3 entered security-only support at the end of 2025. It will continue receiving critical security patches through December 31, 2027. Teams on 8.3 should be evaluating 8.4 or 8.5 for their next upgrade cycle.

PHP 8.1: End of Life December 31, 2025

PHP 8.1 reached end of life on December 31, 2025. Its final release was 8.1.34 on December 18, 2025. Any CVE disclosed against PHP 8.1 after that date is not patched by the PHP project, and that is no longer hypothetical: PHP2Shell (CVE-2026-109618 and CVE-2026-109619) was fixed only in PHP 8.2 and later, with nothing for 8.1 beyond a minimal source backport. There is no PHP 8.1.35.

For more details, see our dedicated coverage: PHP 8.1 End of Life: Security Support Has Officially Ended.

End-of-Life PHP Versions in Detail

PHP 8.0 End of Life

  • EOL Date: November 26, 2023
  • Last Release: 8.0.30

PHP 8.0 was a landmark release, introducing the JIT compiler, union types, named arguments, attributes, match expressions, and nullsafe operators. Despite its significance, PHP 8.0 followed the original three-year support model (two years active, one year security) and lost all support in November 2023. PHP 8.0 is vulnerable to every PHP CVE disclosed since then, including the critical CVE-2024-4577 (CVSS 9.8) remote code execution flaw that has been actively exploited in the wild since mid-2024, and both PHP2Shell CVEs, for which 8.0 received only a source backport and no release.

PHP 7.4 End of Life

  • EOL Date: November 28, 2022
  • Last Release: 7.4.33

PHP 7.4 was the final release in the PHP 7.x series and remains one of the most heavily deployed PHP versions on the internet. WordPress.org statistics have historically shown PHP 7.4 as the single most-used PHP version across WordPress installations, with over 40% of WordPress sites running it at one point. PHP 7.4 introduced typed properties, arrow functions, the null coalescing assignment operator, and preloading.

PHP 7.4 has been unsupported since November 2022. Every CVE disclosed against PHP since November 2022 is unpatched on 7.4 upstream, including CVE-2024-4577, which is actively exploited, and PHP2Shell. 7.4.33 is still the last official release; there is no PHP 7.4.34.

PHP 7.3 End of Life

  • EOL Date: December 6, 2021
  • Last Release: 7.3.33

PHP 7.3 added flexible heredoc/nowdoc syntax, trailing commas in function calls, and json_throw_on_error. It has been unsupported since December 2021 and received no PHP2Shell backport of any kind.

PHP 7.2 End of Life

  • EOL Date: November 30, 2020
  • Last Release: 7.2.34

PHP 7.2 introduced object type hints, the sodium cryptography extension as a core module, and abstract method overriding. It has been unsupported since November 2020.

PHP 7.1 End of Life

  • EOL Date: December 1, 2019
  • Last Release: 7.1.33

PHP 7.1 introduced nullable types, void return types, class constant visibility, and iterable pseudo-type. It has been unsupported since December 2019.

PHP 7.0 End of Life

  • EOL Date: January 10, 2019
  • Last Release: 7.0.33

PHP 5.6 End of Life

  • EOL Date: December 31, 2018
  • Last Release: 5.6.40

PHP 5.6 was the last version of the PHP 5.x series and its EOL marked the end of an era for PHP. Despite being unsupported since the end of 2018, PHP 5.x deployments still exist in production environments, particularly in legacy enterprise applications and older CMS installations. W3Techs data has shown PHP 5.x usage persisting on a measurable percentage of websites for years after EOL. PHP 5.x is within the PHP2Shell affected range and has no upstream fix or backport.

PHP Versions for WordPress (2026)

WordPress.org recommends PHP 8.3 or greater. WordPress still runs on PHP 7.4 and later in legacy environments, but WordPress.org warns that those versions have reached end of life and may expose a site to security vulnerabilities. Real-world adoption lags well behind the recommendation, and many hosting providers are slow to enforce upgrades.

That gap matters because a PHP vulnerability bypasses everything above it. A site can keep WordPress core, plugins, and themes fully patched and still be taken over through the PHP runtime. PHP2Shell is the current example: the confirmed CVE-2026-109618 exploit runs against Apache mod_php before any application code executes, and mod_php remains common on shared WordPress hosting.

CVE-2024-4577: A Case Study in EOL PHP Risk

CVE-2024-4577 (CVSS 9.8) is an OS command injection vulnerability that affects PHP running on Windows with CGI configurations. The flaw exploits Windows "Best-Fit" character encoding behavior to bypass previous CGI protections and achieve remote code execution.

This vulnerability was disclosed in June 2024 and patched in PHP 8.1.29, 8.2.20, and 8.3.8. PHP 8.0 and all 7.x versions are confirmed vulnerable but received no official patches because they were already end-of-life.

Since January 2025, security researchers have documented mass exploitation of CVE-2024-4577 across multiple regions, with over 1,000 unique IPs observed attacking vulnerable systems in a single month. Threat actors have used the vulnerability to deploy cryptominers, RATs, web shells, and DDoS botnet malware.

For a deeper technical analysis, see our CVE-2024-4577 vulnerability write-up and vulnerability directory entry.

PHP2Shell repeated the pattern two years later, faster: critical vulnerabilities are disclosed, patches are issued only for supported versions, and attackers go after the gap within hours.

What Happens After End of Life

When a PHP version reaches EOL, three things change immediately:

Security patches stop. The PHP project will not release fixes for new CVEs, regardless of severity. CVE-2024-4577 and PHP2Shell both demonstrated that critical RCE vulnerabilities affecting EOL versions go unpatched upstream while being actively exploited.

Ecosystem compatibility degrades. PHP frameworks (Laravel, Symfony, Drupal), package managers (Composer), and hosting providers progressively drop support for older PHP versions. Laravel 11 requires PHP 8.2 or higher. Drupal 11 requires PHP 8.3. Running EOL PHP increasingly means running an EOL application stack.

Compliance audits flag it. SOC 2, PCI DSS, HIPAA, FedRAMP, NIS2, DORA, and the EU Cyber Resilience Act require organizations to use supported software or demonstrate equivalent compensating controls. PCI DSS Requirement 6.3.3, for example, expects critical vulnerabilities to be patched within 30 days, which an EOL PHP branch with a public PHP2Shell exploit cannot meet without a patched runtime. EOL PHP is a finding on virtually every security audit, and vulnerability scanners like Qualys, Nessus, and Snyk flag it automatically.

Is My PHP Version Supported?

PHP Version Upgrade Recommendations

PHP Version Upgrade Recommendations
Version Status Recommended Action
8.5 Supported (Active) Update to 8.5.12 or later (PHP2Shell fix)
8.4 Supported (Active until Dec 31, 2026, then Security Only) Update to 8.4.27 or later (PHP2Shell fix)
8.3 Supported (Security Only) Update to 8.3.36 or later; plan upgrade to 8.4 or 8.5
8.2 Supported (Security Only, EOL Dec 31, 2026) Update to 8.2.35 now; upgrade before Dec 31, 2026
8.1 EOL No PHP2Shell release; upgrade or adopt extended support
8.0 EOL No PHP2Shell release; upgrade or adopt extended support
7.4 EOL No PHP2Shell release; upgrade or adopt extended support
7.3 and below EOL No PHP2Shell fix or backport; upgrade or adopt extended support

Options for EOL PHP Versions

1. Upgrade to a Supported Version

The best long-term approach. PHP's migration guides (available at php.net) document the breaking changes and deprecations between each version. Tools like Rector can automate many code transformations.

The challenge is scope. Upgrading from PHP 7.4 to 8.4 spans five feature releases and a major-version boundary, and the gap between PHP 7.x and 8.x is substantial: deprecated dynamic properties, stricter type handling, removed functions, and changes to string-to-number comparisons all require careful testing. For large codebases, particularly those relying on frameworks or CMSs that also need upgrading, the total migration effort can take months. If PHP2Shell is what's forcing the decision, note that 8.2.35 is the oldest fixed release, but 8.2 itself goes EOL on December 31, 2026, so 8.4 or 8.5 is the target that doesn't put you back here when 8.2 goes EOL.

2. Migrate to a Different Technology

Some organizations use a PHP EOL event as a trigger to re-platform entirely, moving to Node.js, Python, Go, or another backend technology. This is the most expensive and time-consuming option, but may make strategic sense for teams already planning to move away from PHP.

3. Adopt Commercial Extended Support

For organizations that cannot upgrade immediately, commercial extended support provides ongoing security patches for EOL PHP versions, closing the vulnerability gap while your team plans and executes a migration on its own timeline.

HeroDevs Never-Ending Support (NES) for PHP covers PHP 5.6 and 7.1 through 8.2, with coverage for 8.2 continuing past its December 31, 2026 EOL. NES ships patched runtimes of the PHP version you already run, as signed RPM and DEB packages and Windows installers, with a 14-day SLA for critical CVEs. That includes fixes for PHP2Shell and CVE-2024-4577 on branches the PHP project no longer patches. This is the same model HeroDevs uses across its full NES product portfolio: a secure, drop-in replacement that requires no application code changes.

Frequently Asked Questions

What is the latest PHP version?

PHP ships a new version each November; PHP 8.6's release date is November 19, 2026. As of October 24, 2026, the latest stable release was PHP 8.5.12 (October 21, 2026), with 8.4.27, 8.3.36, and 8.2.35 on the other supported branches. php.net/downloads always lists the current patch versions.

What PHP version should I use?

PHP 8.4 or newer is the right choice for most production environments. PHP 8.4 receives security fixes through December 31, 2028, and PHP 8.5 through December 31, 2029. Whichever you choose, run the latest patch release for your branch, and at minimum the PHP2Shell fix (8.4.27 or 8.5.12).

When does PHP 8.2 reach end of life?

PHP 8.2 reaches end of life on December 31, 2026. After that date, it will no longer receive security patches from the PHP project. Organizations should begin planning their upgrade to PHP 8.3, 8.4, or 8.5 now.

Which PHP versions are fixed for PHP2Shell?

The PHP project fixed PHP2Shell (CVE-2026-109618 and CVE-2026-109619) in PHP 8.2.35, 8.3.36, 8.4.27, and 8.5.12, released October 21, 2026. PHP 8.1, 8.0, and 7.4 received only minimal source backports with no official release. PHP 7.3 and older received nothing. Patched runtimes for end-of-life branches are available from Linux distributions for the versions they still maintain and from commercial vendors such as HeroDevs NES for PHP.

Is there a PHP 7.4.34 or PHP 8.1.35?

No. The last official releases are PHP 7.4.33 (November 2022), 8.0.30, and 8.1.34 (December 2025). The PHP project did not ship new releases of these branches for PHP2Shell. The only upstream fixes are source backports for teams that build PHP themselves.

Is PHP 8.1 still supported?

No. PHP 8.1 reached end of life on December 31, 2025, and its last release was 8.1.34. It did not receive an official PHP2Shell release.

Is PHP 7.4 still supported?

No. PHP 7.4 reached end of life on November 28, 2022. It has not received a security release since 2022 and is vulnerable to multiple critical CVEs, including CVE-2024-4577 (CVSS 9.8) and PHP2Shell. Organizations still running PHP 7.4 should upgrade to a supported version or adopt extended support through HeroDevs.

Does PHP have LTS versions?

No. PHP has no long-term support track. Every version gets two years of active support and two years of security support, ending on December 31. Support beyond that comes from Linux distributions (for the PHP versions they ship) or commercial extended support.

Does running EOL PHP affect compliance?

Yes. SOC 2, PCI DSS, HIPAA, ISO 27001, FedRAMP, NIS2, and the EU Cyber Resilience Act all have requirements around maintaining supported software and patching known vulnerabilities. Running EOL PHP is commonly flagged during audits, and vulnerability scanners will report it as a finding.

Why do so many sites still run PHP 7.4?

PHP 7.4 was the last version in the 7.x series, and the jump to PHP 8.0 introduced significant breaking changes (stricter type coercion, removal of deprecated functions, JIT compilation). Many WordPress plugins and themes were slow to declare PHP 8.x compatibility, and shared hosting providers were slow to enforce upgrades. The result is a long tail of sites running unsupported PHP, particularly in the WordPress ecosystem.

Taking Action

PHP's annual release cadence and four-year support windows mean that staying current requires ongoing planning. With PHP 8.2 reaching EOL at the end of 2026 and most internet-facing PHP still reporting 8.1 or older in October 2026, the gap between supported and deployed PHP continues to widen. PHP2Shell showed what that gap costs: a working exploit, fixes for four branches, and nothing official for everyone else.

Start with where you stand today. Run php -v on your servers, check that you are on at least the PHP2Shell fix releases (8.2.35, 8.3.36, 8.4.27, or 8.5.12), review your hosting provider's PHP version settings, and check your application's compatibility requirements. If you are on 8.2 through 8.5, update to the latest patch now. If you are on 8.1 or older, decide now whether you are upgrading, building from the source backports, or running a supported patched runtime, because the mitigations alone do not close PHP2Shell.

Whether you choose to upgrade, migrate, or adopt extended support, HeroDevs can help. Our NES for PHP provides ongoing security patches, compliance SLAs, and drop-in replacement runtimes for end-of-life PHP that require no code changes. If your organization is running end-of-life PHP and needs help evaluating your options, contact us.

This post is maintained by HeroDevs and will be updated as new PHP versions are released and existing versions reach end of life. Last updated: October 2026.

Table of Contents
Author
Greg Allen
Chief Technology Officer
Open Source Insights Delivered Monthly