PHP 8.2 End of Life (EOL): 31 December 2026, What Changes and What to Do
PHP 8.2's security support ends on 31 December 2026. Code keeps running, but hosts are already removing it. PHP 8.5 is the version to move to.
Written Updated Shahzeb Umer
SubscribeStatus
SupportedSoon
Support ends .
- Time left
- 42 days
- Latest release
- 8.2.36
- Move to
- PHP 8.5fixed until 31 Dec 2029
4.1 years of support
- Bug and security fixes8 Dec 2022 – 31 Dec 2024
- Security fixes only31 Dec 2024 – 31 Dec 2026
Supported for 4.1 years, from 8 Dec 2022 to 31 Dec 2026.
Who still patches it
Seven places PHP 8.2 runs, six deadlines.
- php.net: Security fixes to 31 Dec 2026
- Amazon Linux 2023 (php8.2): Patched to 31 Dec 2026
- Google App Engine (php82): Deprecated 31 Dec 2027
- Elastic Beanstalk (PHP 8.2 on AL2023): Retired 31 Mar 2027
- Debian 12 (php8.2, Debian LTS): Patched to 30 Jun 2028
- RHEL 8.10, 9.4+ (php:8.2 stream): Patched to May 2029
- Docker image (php:8.2): Still rebuilt, no end announced
Where to move
Be on PHP 8.5.
The short version
- PHP 8.2 reaches end of life on 31 December 2026. It has had security fixes only since 31 December 2024, and the latest, 8.2.36 on 19 November 2026, fixed 12 vulnerabilities, four rated critical, a month after 8.2.35 fixed two critical remote code execution flaws. After 31 December php.net ships nothing more for 8.2.
- Hosts are moving first: Acquia removed 8.2 on 1 October 2026, Pressable and WP Cloud follow on 8 and 15 December, and Google App Engine stops php82 deployments on 31 December. Debian 12 (until 30 June 2028) and RHEL 8 and 9 (until May 2029) keep patching their own packages.
- Move to PHP 8.5, supported until 31 December 2029 and supported by WordPress 6.9 and later, Laravel 12 and 13 and Drupal 11.3 and later. PHP 8.4, supported until 31 December 2028, is the fallback.
On this page
PHP 8.2 reaches end of life on 31 December 2026. php.net stops making security releases for the branch that day, and its 8.2.35 announcement says so plainly: PHP 8.2 "will receive no further security fixes after that date."
8.2 has been in security-only support since its active support ended on 31 December 2024, so nothing about how it runs changes. Your code keeps working on 1 January 2027 exactly as it did the day before. What ends is the patch supply, and some hosts are removing 8.2 before php.net's date.
What stops on 31 December 2026
php.net gives each branch two years of active support, with regular bug and security fixes, then two years of fixes for critical security issues only, released as needed. That four-year cycle, with every end date moved to 31 December, comes from the RFC Release cycle update, accepted in April 2024 and applied to every branch from 8.2 on. Before it, php.net listed 8 December 2025 as 8.2's last day, the date older articles still give.
For 8.2, that has meant this. The last bug-fix release was 8.2.27, on 19 December 2024. Since then php.net has published nine security releases, from 8.2.28 on 13 March 2025 to 8.2.36 on 19 November 2026, sometimes five months apart. Together they fixed more than 45 CVEs, in the HTTP stream wrapper, SOAP, Phar, PHP-FPM and the OpenSSL extension among others. 8.2.35 fixed CVE-2026-109618 and CVE-2026-109619, which php.net said "can allow unauthenticated remote code execution". Four weeks later 8.2.36 fixed 12 more, four of them critical, and turned session upload progress off by default to close one of them.
That supply is what stops. The next flaw like those gets fixed in 8.3 to 8.6 only. Windows builds have had less all through 2026: in a branch's second year of security support, the RFC leaves ABI-incompatible updates of bundled Windows libraries to users.
Who still patches PHP 8.2
Where your PHP came from decides who patches it after 31 December.
| Where it runs | Patched until | What happens after | Source |
|---|---|---|---|
| php.net builds | 31 December 2026 | No more releases | php.net |
Debian 12, php8.2 |
30 June 2028, by Debian LTS | Debian LTS ends | Debian LTS |
| Ubuntu | Not shipped | 22.04 has 8.1, 24.04 has 8.3, 26.04 has 8.5 | Ubuntu |
RHEL 8.10 and RHEL 9.4 or later, php:8.2 stream |
May 2029 | The stream retires | Red Hat |
Amazon Linux 2023, php8.2 |
31 December 2026 | No further updates | AWS |
Docker image php:8.2 |
Still rebuilt; last pushed 6 November 2026 | php:8.1 was dropped two days after its end of life; old tags still pull but are no longer rebuilt |
Docker |
Google App Engine, php82 |
31 December 2026 | Apps keep serving, with no patches and no new deployments | Google Cloud |
| Elastic Beanstalk, PHP 8.2 on AL2023 | 31 March 2027 | No updates, no new environments, 90 days' grace for existing ones | AWS |
| Freexian PHP LTS, paid | No end date set | From €1,200 a year for 1 to 30 systems | Freexian |
| Zend PHP LTS, paid | December 2028 | Quote only | Zend |
Debian has tracked upstream closely: DLA-4848-1 shipped 8.2.35 the day php.net released it. Distribution support covers the distribution's package only. A container, a binary you compiled or a third-party repository depends on whoever builds it, and Freexian, which works with deb.sury.org's maintainer, describes deb.sury.org as best-effort. Remi Collet's php-src-security repository backports fixes to end-of-life branches up to 8.1, with no 8.2 branch yet. Azure App Service follows php.net's date.
What breaks first
Nothing inside 8.2 switches off. The pressure comes from around it.
Hosts remove it on their own dates. Acquia removed 8.2 on 1 October 2026 and converted remaining environments to 8.4. Pressable retires it on 8 December 2026 and moves remaining sites to the next version. WP Cloud, Automattic's platform for WordPress hosts, removes it on 15 December 2026. In a forced upgrade, the host picks the target and the date.
Frameworks raise their floor. On Packagist on 11 November 2026, Laravel 13 requires PHP 8.3, and Laravel 12, which allows 8.2, gets security fixes until 24 February 2027. Symfony 8 requires 8.4; Symfony 7.4 LTS accepts 8.2 until November 2029. Drupal 11 requires 8.3. Drupal 10, the last major to run on 8.2, ends on 9 December 2026, the week Drupal 12 arrives requiring 8.5. PHPUnit 12 needs 8.3. On 8.2, Composer refuses them:
- laravel/framework v13.42.0 requires php ^8.3 -> your php version (8.2.35) does not satisfy that requirement.
WordPress 7.1 still runs on PHP 7.4 to 8.5, so core forces nothing. On 11 November 2026, 22.5% of WordPress sites reporting to WordPress.org ran 8.2. With the 32.2% already on 8.1 or older, more than half will be on an unsupported PHP on 1 January 2027.
Scanners flag the version. Tenable's Nessus plugin 58987, PHP Unsupported Version Detection, is rated Critical (CVSS v3 10.0) and fires on the version alone, so only a newer PHP clears it.
Site Health stays mild. WordPress already calls 8.2 "an older version of PHP" that "should be updated", but its API still reports 8.1 as receiving security updates almost a year after 8.1's end of life. Do not wait for it to turn critical.
How to check what you run
The command-line PHP and the PHP serving your site can differ, so check both.
php -v
php -r 'echo PHP_VERSION, PHP_EOL;'
ls /usr/bin/php[0-9]* /usr/sbin/php-fpm* # Debian and Ubuntu: one binary per version
composer show --platform | grep -E '^php '
composer check-platform-reqs # do installed packages accept this PHP?
grep -rn --include='Dockerfile*' 'FROM php:8\.2' .
phpinfo() shows the web server's version at the top, along with your entire configuration, so delete the file once you have read it; <?php echo PHP_VERSION; exposes less. In WordPress, open Tools > Site Health > Info > Server.
Which version to move to: PHP 8.5
| Version | Released | Bug fixes until | Security fixes until | Latest |
|---|---|---|---|---|
| 8.2 | 8 December 2022 | 31 December 2024 | 31 December 2026 | 8.2.36 |
| 8.3 | 23 November 2023 | 31 December 2025 | 31 December 2027 | 8.3.37 |
| 8.4 | 21 November 2024 | 31 December 2026 | 31 December 2028 | 8.4.28 |
| 8.5 | 20 November 2025 | 31 December 2027 | 31 December 2029 | 8.5.13 |
| 8.6 | 19 November 2026 | 31 December 2028 | 31 December 2030 | 8.6.0 |
Target 8.5. It is a year old, on its thirteenth patch release, with bug fixes until the end of 2027 and security fixes until 31 December 2029. WordPress supports it from 6.9, Laravel 12 and 13 and Drupal 11.3 and 11.4 support it, and Drupal 12 requires it. Ubuntu 26.04 LTS packages it.
Use 8.4 if something blocks 8.5. It is supported until 31 December 2028 and is the newest PHP that Debian 13 packages and Red Hat offers for RHEL 9 and 10.
Skip 8.3, which ends on 31 December 2027. Hosts that upgrade automatically may still pick it: Pressable moves sites to the next version in sequence.
Leave 8.6 for later. It came out on 19 November 2026, but no Laravel or Drupal release supports it yet, and Elastic Beanstalk plans its 8.6 platform for January 2027.
Skipping versions is reasonable: the changes since 8.2 are mostly deprecations, and one test cycle costs less than three.
How to upgrade
Test on the target first. Add 8.5 to CI next to 8.2, with the extensions your app needs. --fail-on-deprecation makes PHPUnit exit with a failure when passing tests triggered deprecations:
docker run --rm -v "$PWD":/app -w /app php:8.5-cli vendor/bin/phpunit --fail-on-deprecation
Find blocking packages with composer why-not php 8.5. If composer.json sets config.platform.php, raise it, or Composer keeps resolving as if you were on 8.2.
Run PHPCompatibility. Its last stable release, 9.3.5, is from 2019 and predates PHP 8, so install the 10.0 pre-release as its README says:
composer config allow-plugins.dealerdirect/phpcodesniffer-composer-installer true
composer require --dev phpcompatibility/php-compatibility:"^10.0.0@dev"
vendor/bin/phpcs -ps src --standard=PHPCompatibility --runtime-set testVersion 8.2-8.5
Let Rector do the mechanical edits. Install rector/rector, put ->withPhpSets(php85: true) in rector.php and review with vendor/bin/rector process --dry-run. Its sets also adopt new features, such as array_find() from 8.4, so apply them once you no longer deploy to 8.2.
Upgrade dependencies, then PHP, and compare php -m on both runtimes so a missing extension does not surprise you.
Changes most likely to bite from 8.2 to 8.5
From php.net's migration guides. A deprecation logs an E_DEPRECATED notice and the code keeps running, until a test runner or error handler treats it as a failure.
Implicitly nullable parameters (High, deprecated in 8.4). function find(User $user = null) should become ?User $user = null, which also runs on 8.2. Rector's ExplicitNullableParamTypeRector fixes them all.
Four extensions left the core (Medium, 8.4). IMAP, OCI8, PDO_OCI and PSpell moved to PECL. Without the PECL build, imap_open() is a fatal Call to undefined function error.
PDO driver constants (Medium, deprecated in 8.5). PDO::MYSQL_ATTR_SSL_CA and similar give way to Pdo\Mysql::ATTR_SSL_CA, a class added in 8.4. Laravel's skeleton up to 11.x puts that constant in config/database.php.
CSV escape parameter (Medium, deprecated in 8.4). fgetcsv(), fputcsv() and str_getcsv() now need escape passed explicitly; '\\' keeps the current behaviour.
null as an array key (Medium, deprecated in 8.5). $map[null] and array_key_exists(null, $map) are deprecated; use an empty string.
OPcache built in (Low, 8.5). A zend_extension=opcache.so line now emits a startup warning.
Slower default hashing (Low, 8.4). The default bcrypt cost for password_hash() rose from 10 to 12, about four times the work per hash. Existing hashes still verify.
Sources
- Supported versions, branches data, ChangeLog and 2026 news: dates, releases and the 8.2.35 announcement
- GHSA-w8hw-w9fx-j79w and GHSA-6wmf-4rv5-p3rp: the critical 8.2.35 fixes
- RFC: Release cycle update and php.net in February 2024: the cycle and the old date
- PHP 8.6 timetable and migration guides for 8.3, 8.4 and 8.5
- Debian LTS, Debian tracker, Red Hat, Ubuntu, Amazon Linux 2023 and Docker: distributions and images
- App Engine, Elastic Beanstalk, Azure, Acquia, Pressable and WP Cloud: platforms and hosts
- Freexian, Zend and php-src-security: extended support
- Packagist, Laravel, Symfony, Drupal with its schedule, and WordPress: framework requirements
- WordPress PHP statistics, read 11 November 2026, and Tenable plugin 58987
- Composer, PHPCompatibility, Rector and PHPUnit: upgrade tools
- endoflife.date: PHP: the dates in the status box, MIT licensed
Common questions
Is PHP 8.2 still supported?
When does PHP 8.2 reach end of life?
Is PHP 8.2 safe to use after December 2026?
Which PHP version should I upgrade to?
Does WordPress support PHP 8.4 and 8.5?
Will my host keep running PHP 8.2?
Do Debian, Ubuntu and RHEL keep patching PHP 8.2?
What is the last version of PHP 8.2?
Also on the calendar
End-of-life dates for the rest of your stack.
- Kubernetes end of life3 supportedNext to end: 1.35, 28 Feb 2027
- Microsoft .NET end of life2 supportedNext to end: 11, 14 Nov 2028
- Node.js end of life3 supportedNext to end: 22, 30 Apr 2027
- OpenSSL end of life3 supportedNext to end: 4.0, 14 May 2027
- PHP end of life5 supportedNext to end: 8.2, 31 Dec 2026
- PostgreSQL end of life5 supportedNext to end: 15, 11 Nov 2027
- Python end of life5 supportedNext to end: 3.11, Oct 2027
- Ubuntu end of life4 supportedNext to end: 22.04, 1 Jun 2027
Dates checked against endoflife.date (MIT). How we check datesReport a wrong dateEvery PHP version