Skip to main content
BumbleTap
Add to ChromeInstall

PHP 8.6 End of Life (EOL): 31 December 2030, and What the New Release Changes

PHP 8.6 was released on 19 November 2026 and gets security fixes until 31 December 2030. What it adds, what breaks, where it runs yet, and whether to move from 8.5 now.

Written Shahzeb Umer

Subscribe

Status

Supported

Support ends .

Time left
1503 days
Latest release
8.6.0
Support type
Standard

4.1 years of support

  • Bug and security fixes19 Nov 2026 – 31 Dec 2028
  • Security fixes only31 Dec 2028 – 31 Dec 2030

Supported for 4.1 years, from 19 Nov 2026 to 31 Dec 2030.

Who still patches it

Four places PHP 8.6 runs, one deadline.

  • php.net (upstream): Security fixes to 31 Dec 2030
  • Docker image (php:8.6): Rebuilt, no end announced
  • deb.sury.org (Ubuntu 22.04 to 26.04, Debian 12 and 13): No end announced
  • Remi's repository (Fedora 43+, Enterprise Linux 8+): No end announced
Sources: php.net release process and supported versions, docker-library official images, packages.sury.org, Remi's repository. Checked 19 Nov 2026.

Where to move

Be on PHP 8.6.

The short version

  • PHP 8.6.0 was released on 19 November 2026. Under php.net's four-year cycle it gets bug fixes until 31 December 2028 and security fixes until 31 December 2030, a year more than PHP 8.5 on both counts.
  • It adds partial function application, clamp(), default values on readonly properties and a Time\Duration class. What breaks most: session cookies default to strict mode, HttpOnly and SameSite=Lax, warnings from built-in functions stop printing file paths, and spl_object_hash(), the mb_ereg*() functions and return inside finally are deprecated.
  • Test now, deploy where your stack is ready. WordPress supports 8.6 from 7.2, due 8 December 2026. Laravel's support table still ends at 8.5, Drupal lists no release for it, no Ubuntu or Debian release ships it, and Elastic Beanstalk plans it for January 2027. Stay on 8.5, supported until 31 December 2029, until yours catch up.
On this page
  1. How PHP 8.6's support dates are worked out
  2. How 8.6 got here
  3. Should you move to PHP 8.6 now?
  4. What PHP 8.6 adds
  5. What breaks from 8.5 to 8.6
  6. Where PHP 8.6 runs, as of 19 November 2026
  7. How to test your code on PHP 8.6
  8. What comes next
  9. Sources

PHP 8.6 was released on 19 November 2026, and php.net supports it until 31 December 2030: bug and security fixes until 31 December 2028, then security fixes only. That is a year more than PHP 8.5 on both counts.

It lands six weeks before a busy New Year's Eve. On 31 December 2026 PHP 8.2 reaches end of life and 8.4 drops to security fixes only, so 8.6 arrives while many teams are already planning an upgrade. This page covers how 8.6's dates are worked out, what it adds, what it breaks, and where you can run it yet.

How PHP 8.6's support dates are worked out

PHP's release-process policy, as changed by the RFC Release cycle update in April 2024, gives every branch three phases measured in calendar years after its planned release date, each ending on 31 December:

Phase What php.net ships Ends for 8.6
Active support, years 1 and 2 A release every four weeks, with bug and security fixes 31 December 2028
Security support, year 3 Security fixes, regression fixes and updated Windows libraries, released only when needed 31 December 2029
Security support, year 4 Security fixes, plus fixes for crashes and for regressions a security fix caused, released only when needed 31 December 2030

8.6's planned release date was 19 November 2026, so "the end of year 2" is 31 December 2028 and "the end of year 4" is 31 December 2030. The same arithmetic gives the dates php.net already publishes for the two previous branches: 8.4, released on 21 November 2024, ends active support on 31 December 2026 and security support on 31 December 2028, and 8.5, released on 20 November 2025, ends them on 31 December 2027 and 31 December 2029.

The count starts from the planned date, not the actual one. The policy's own example keeps 8.4's dates even if its release had slipped into January, so a late release candidate can't move a branch's end of life.

On Windows, year 4 is thinner. In 8.6's last year, 2030, php.net stops updating the third-party libraries bundled in its Windows builds when an update would break their binary interface. Linux distributions build those libraries themselves, so the gap only affects the php.net Windows downloads.

How 8.6 got here

8.6.0 shipped on the day the release managers' timetable had set: alpha 1 on 2 July, beta 1 on 13 August, the first release candidate on 24 September and general availability on 19 November. Daniel Scherzer was the veteran release manager, with Matteo Beccati and Joe Ferguson.

Two release-candidate numbers never reached users. RC1 was tagged with the wrong API version numbers, so the first candidate shipped as RC2. After RC5, the release managers had to bump the API number again: a security fix had grown an internal engine structure, and extensions compiled against earlier candidates would read the wrong memory in thread-safe builds. They tagged RC6 for it, then replaced it with RC7 before announcing it, to take one more regression fix. RC7, on 12 November, was the last.

8.6.0 includes the fixes for the two critical remote code execution flaws, CVE-2026-109618 and CVE-2026-109619, that php.net patched in 8.2 to 8.5 on 21 October 2026. 8.6 builds older than RC4 don't, and php.net told anyone running one to update immediately. 8.6.0 also has all 17 fixes php.net shipped on its release day in 8.5.13, 8.4.28, 8.3.37 and 8.2.36, seven of them rated critical, which no release candidate has, RC7 included.

Should you move to PHP 8.6 now?

Take it now if you build your own servers or containers, from Docker's official image, deb.sury.org or Remi's repository, and run your own code or Symfony, with a test suite that passes on 8.6. WordPress sites can follow once 7.2 is out on 8 December. It buys a year of support over 8.5.

Stay on 8.5 for now if you run Laravel or Drupal, which don't list 8.6 yet; install PHP from Ubuntu's or Debian's own archive; deploy to Elastic Beanstalk, whose 8.6 platform is planned for January 2027; or depend on Xdebug or another PECL extension without an 8.6 build. 8.5 is supported until 31 December 2029.

Or wait for the first patch. php.net makes a bug-fix release every four weeks, so 8.6.1 is about a month away.

Coming from 8.2, which ends on 31 December 2026, move to 8.5 first: frameworks, distributions and hosts already support it. The PHP 8.2 page covers that move.

Version Released Bug fixes until Security fixes until
8.4 21 November 2024 31 December 2026 31 December 2028
8.5 20 November 2025 31 December 2027 31 December 2029
8.6 19 November 2026 31 December 2028 31 December 2030

What PHP 8.6 adds

Partial function application. Put ? in place of an argument, or ... for all the remaining ones, and PHP returns a closure that waits for them instead of calling the function. The closure keeps the original function's parameter names and types. It pairs well with the pipe operator from 8.5:

// PHP 8.5
$slugs = array_map(fn (string $t): string => str_replace(' ', '-', $t), $titles);

// PHP 8.6
$slugs = array_map(str_replace(' ', '-', ?), $titles);
$slug = $title |> trim(...) |> strtolower(...) |> str_replace(' ', '-', ?);

Each ? becomes one required parameter. When a partial call with a single ? sits directly on the right of |>, PHP compiles it to a plain call with no closure at all. Constructors can't be partially applied: new Foo(1, ?) is a compile error.

clamp(). It returns the value, or the nearest bound when the value falls outside it. It throws a ValueError when $min is greater than $max or either bound is NAN:

$percent = clamp($value, min: 0, max: 100);

Readonly properties can have defaults. Until now a readonly property couldn't declare a default value and had to be assigned, usually in the constructor. That makes it easy to satisfy a get-only interface property with a fixed value:

final readonly class SourceOneIngestor implements Ingestor
{
    public string $name = 'Source One';
}

Time\Duration. An immutable, nanosecond-precise "stopwatch" duration, as opposed to DateInterval's calendar units. It has fromMilliseconds(), fromSeconds() and similar constructors, add(), sub(), multiplyBy(), divideBy() and compare(), and parses ISO 8601 durations up to hours. So far only the new polling API's wait() timeout accepts one; sleep() and other existing functions don't.

use Time\Duration;

$delay = Duration::fromMilliseconds(100)->multiplyBy(2 ** $attempt);

Smaller additions:

  • A global SortDirection enum, with Ascending and Descending cases, for libraries to share.
  • #[\Override] on class constants and enum cases, and __debugInfo() on enums.
  • Objects stored in constants can have their properties written, as in FOO->bar = 1.
  • An event-polling API under Io\Poll, and a structured stream-error API (StreamError, StreamException, stream_last_errors()).
  • TLS session resumption, pre-shared keys and TLS 1.3 early data for streams, and a $salt_length argument for RSA-PSS in openssl_sign().
  • mysqli_quote_string(), grapheme_strrev(), ReflectionProperty::isReadable() and isWritable(), ReflectionParameter::getDocComment(), and JSON error messages that say where the error is.
  • pack() and unpack() endianness modifiers for signed integers and floats, CURLOPT_SEEKFUNCTION, and ML-KEM-768 and X-Wing key encapsulation in Sodium with libsodium 1.0.22 or later.
  • The built-in development server accepts the HTTP QUERY method.

Faster in places. array_map() with a first-class callable or partial application compiles to a plain loop, printf() with only %s and %d compiles to string interpolation, and thread-safe (ZTS) builds are faster. The JIT now works in thread-safe builds on Apple Silicon.

What breaks from 8.5 to 8.6

From php.net's UPGRADING notes for 8.6 and the RFCs behind them. 8.6 removes no extensions. A deprecation logs an E_DEPRECATED notice and the code keeps running.

1. Sessions get secure defaults. High for SSO and cross-site forms, low otherwise. Three defaults changed, both in PHP itself and in the bundled php.ini-production:

  • session.use_strict_mode is now 1. PHP rejects a session ID it didn't create and issues a new one. Custom session handlers that accept externally supplied IDs need validateId() and create_sid(), or this set back to 0. The default Redis and Memcached handlers don't implement validateId(), so they accept any ID as before.
  • session.cookie_httponly is now 1, so JavaScript can no longer read the session cookie through document.cookie.
  • session.cookie_samesite is now Lax. Browsers no longer send the session cookie on cross-site POST requests, which breaks service-provider-initiated SAML logins and old cross-site form posts. Those endpoints need SameSite=None with session.cookie_secure = 1.
  • session.upload_progress.enabled is now 0, a fix for a critical flaw, CVE-2026-115560, that 8.5.13 and the other 19 November releases make too. If your configuration turns it on, changing session.* settings with ini_set() throws an Error. UPGRADING doesn't mention it.

Laravel and Symfony already set HttpOnly and Lax on their own session cookies. A server that carries over a php.ini based on 8.5's php.ini-production keeps the old values, because that file set all three explicitly. Check what you actually run:

php -i | grep -E 'session\.(use_strict_mode|cookie_httponly|cookie_samesite|upload_progress\.enabled)'

2. Warnings stop showing their arguments. Medium for logs and tests. A few functions used to print an argument inside the parentheses, most usefully the path in file warnings. 8.6 drops it unless the new error_include_args setting is on:

# PHP 8.5
Warning: file_get_contents(/no/such/file): Failed to open stream: No such file or directory
# PHP 8.6
Warning: file_get_contents(): Failed to open stream: No such file or directory

With error_include_args = On, every built-in function's warning lists all the arguments it was called with, such as unlink('/tmp'), truncated by zend.exception_string_param_max_len and hiding parameters marked #[\SensitiveParameter]. Log alerts and tests that match the old text need updating either way.

3. A long list of deprecations. Medium. Most are flagged for removal in PHP 9.0, which has no date. The ones most code will hit:

  • spl_object_hash(); use spl_object_id().
  • Every mbstring regex function, mb_ereg(), mb_ereg_replace(), mb_split() and the rest, because the Oniguruma library behind them is no longer maintained. Use preg_*() with the /u modifier.
  • return inside a finally block, and returning a value from __construct() or __destruct().
  • Classes implementing SessionHandlerInterface without create_sid() and validateId().
  • is_integer(), is_long(), is_double() and doubleval(); use is_int(), is_float() and floatval().
  • SplFileObject::fgetcsv(), fputcsv(), setCsvControl() and getCsvControl(), and the sort, flag and serialization methods ArrayIterator inherits from ArrayObject.
  • Passing an object to array_walk() or http_build_query(), an object for a static method to ReflectionMethod::invoke(), a class-name string to is_a() without $allow_string, or a third argument to define().
  • strcoll(), SORT_LOCALE_STRING, metaphone(), mysqli_get_charset(), mysqli_stmt_init(), and more than 16 filters in one php://filter URL.

Built-in functions report the version and the replacement:

Deprecated: Function spl_object_hash() is deprecated since 8.6, consider using spl_object_id() instead in /app/src/Registry.php on line 42

4. New global names can collide with yours. Medium for helper files. PHP now defines a global clamp() function and global SortDirection, StreamError, StreamException and StreamPollHandle classes. A global helper function clamp() declared without a function_exists() check, or an unnamespaced class with one of those names, stops the script with a fatal error.

5. Failed stream writes now report failure. Medium for custom stream wrappers. fclose(), file_put_contents() and copy() return false when flushing or closing the stream fails, where 8.5 ignored it. WordPress found that a stream wrapper without a stream_flush() method now reports every write as failed, so add one that returns true.

6. Stricter argument checks. Low. Dozens of functions now throw ValueError or TypeError instead of warning or silently truncating: file functions such as file_exists() and is_file() given a path with a NUL byte, setlocale() given a locale with one, number_format() and sleep() with out-of-range values, and many GMP, Intl, Zip and SOAP options. preg_grep() returns false on a regex error instead of a partial array, trim() also strips form feeds, and bindec(), hexdec(), octdec() and base_convert() raise a notice when they can't convert a number exactly.

7. Extensions must be rebuilt. Medium if you use PECL. 8.6 has a new extension API number, so every compiled extension needs an 8.6 build, and anything built against a release candidate before RC6 must be rebuilt. As of 19 November 2026 Xdebug supports 8.6 only in 3.6.0alpha1, and packages.sury.org has no 8.6 builds of Xdebug, Redis, Imagick or APCu. Remi's repository has all four for Enterprise Linux, Xdebug as the alpha.

8. Smaller operational changes. Low. On a hard out-of-memory error PHP now calls abort(), so the exit code is 134 and the system may write a core dump. The bundled libmagic, file 5.48, detects TrueType fonts as font/ttf instead of font/sfnt, which upload allow-lists may need to accept. The php.net Windows builds move to Visual Studio 2026, OpenSSL 4 and libxml2 2.15.3, which makes DOMDocument::$documentURI a native path for local files.

Where PHP 8.6 runs, as of 19 November 2026

Where it runs PHP 8.6 status Notes Source
php.net, source and Windows builds 8.6.0 since 19 November 2026 Bug fixes to 31 December 2028, security fixes to 31 December 2030 php.net
Docker official image php:8.6, 8.6.0, since 19 November 2026, on Debian 13 and 12 and Alpine 3.24 and 3.23; no ZTS variant latest, 8 and cli moved to 8.6 the same day, as they did for 8.5 official-images
packages.sury.org 8.6.0 for Ubuntu 22.04, 24.04 and 26.04 and Debian 12 and 13; Debian 11 still has a release candidate Ondřej Surý's repository, and the supported route on Ubuntu 26.04; no 8.6 builds of PECL extensions yet packages.sury.org
ppa:ondrej/php Release candidates only, 8.6.0~rc3, for Ubuntu 22.04 and 24.04 Being merged into packages.sury.org; unlike for 8.5, no 8.6.0 on release day Launchpad
Ubuntu archive Not shipped. 26.04 LTS and 26.10 have 8.5, and so does 27.04, in development until 22 April 2027 No announced plan for 8.6 Ubuntu archive
Debian Experimental only, 8.6.0~rc5-1 Testing and unstable still default to 8.4; 8.5 is also experimental-only Debian tracker
Remi's repository, Fedora 43+ and Enterprise Linux 8+ 8.6.0, as the php:remi-8.6 module stream and the php86 Software Collection, with 8.6 builds of APCu, Imagick, Redis and Xdebug's alpha Fedora itself has 8.5; 8.6 is planned for Fedora 46 Remi
Alpine php86 8.6.0_rc7, a release candidate, in edge's testing repository No stable Alpine release has it Alpine
AWS Elastic Beanstalk Planned for January 2027, on Amazon Linux 2023 AWS calls the date tentative AWS

latest has moved. On release day, the update that added php:8.6 also moved latest, 8 and cli to it, as it did for 8.5. A Dockerfile that says FROM php:latest, php:8 or php:cli builds on 8.6 the next time it's rebuilt, session defaults and all. Pin php:8.5 until you've tested.

On Ubuntu and Debian, Ondřej Surý is the source. No Ubuntu or Debian release ships 8.6 in its own archive, and Ubuntu 26.04 will stay on 8.5 for its life. packages.sury.org has 8.6.0 for 26.04, 24.04 and 22.04, and installs with the script at https://packages.sury.org/php/README.txt; the PPA's description now sends users there. sudo add-apt-repository ppa:ondrej/php still works on 24.04 and 22.04, but on release day it had only a release candidate. Then:

sudo apt install php8.6-cli php8.6-fpm php8.6-mysql php8.6-xml php8.6-mbstring

These are third-party packages, not covered by Ubuntu's or Debian's security support.

Framework and tool support

Project PHP 8.6 status Source
WordPress Supported from 7.2, due 8 December 2026: core declared support on 10 November 2026. 7.1 supports PHP 7.4 to 8.5 Changeset 65384, compatibility table
Laravel Not listed: the support table gives PHP 8.3 to 8.5 for Laravel 13 and 8.2 to 8.5 for Laravel 12, and Laravel 13's tests run on 8.3 to 8.5. Its Composer constraint, ^8.3, doesn't block 8.6 Laravel
Symfony No formal statement. 7.4 and 8.2 are tested on 8.6, and 8.6 fixes are merged into 6.4, 7.4, 8.1 and 8.2 Symfony CI
Drupal Not supported by 10.4 to 11.3; the cells for 11.4 and 12.0 are blank, and the page points to issue #3608511 Drupal
Xdebug 3.6 needed; only 3.6.0alpha1, from 8 September 2026, so far Xdebug
Rector php86 set; the renames of deprecated aliases since 2.8.4, released 3 November 2026 Rector

How to test your code on PHP 8.6

Run your tests on 8.6 next to your current version. --fail-on-deprecation makes PHPUnit fail when passing tests trigger deprecations:

docker run --rm -v "$PWD":/app -w /app php:8.6-cli vendor/bin/phpunit --fail-on-deprecation

Find blocking packages with composer why-not php 8.6, and inside the 8.6 container run composer check-platform-reqs to see whether installed packages accept it.

Look for the deprecations most code hits:

grep -rnE --include='*.php' '\b(spl_object_hash|mb_ereg\w*|mb_split|mb_regex_\w*|is_integer|is_long|is_double|doubleval|strcoll|metaphone)\s*\(' src/
grep -rnE --include='*.php' '^\s*function\s+clamp\s*\(|^\s*(class|enum)\s+SortDirection\b' .

Let Rector do the renames. With ->withPhpSets(php86: true) in rector.php, Rector 2.8.4 or later replaces is_integer() and the other deprecated aliases and drops define()'s third argument. The set also adopts clamp() and readonly defaults, so apply it once you no longer deploy to 8.5.

Check sessions and logs by hand. Log in through any cross-site flow, such as SAML or a payment provider's return POST, and check that alerts matching file paths in warnings still fire.

What comes next

On 31 December 2026, PHP 8.2 reaches end of life and 8.4 moves to security fixes only. php-src's main branch already identifies itself as 8.7.0-dev, but php.net hasn't published a timetable for it. Under the yearly cycle, the next branch would arrive in late 2027, and 8.6 keeps its own dates either way. The PHP hub has every version's dates.

Sources

Common questions

When was PHP 8.6 released?
On 19 November 2026, as PHP 8.6.0, the date the release managers' timetable had set. Five release candidates came first, numbered RC2 to RC5 and RC7: RC1 was dropped because it was tagged with the wrong API version numbers, and RC6 was built but replaced before it was announced.
When is PHP 8.6 end of life?
On 31 December 2030. php.net fixes bugs and security issues in 8.6 until 31 December 2028, then only security issues, in releases made as needed, until 31 December 2030. After that php.net publishes no more 8.6 releases.
Is PHP 8.6 a long-term support (LTS) release?
No. PHP has no LTS releases: every branch gets the same four years, two of active support and two of security fixes only, each ending on 31 December. Longer support comes from Linux distributions that package a branch, and no stable distribution release packages 8.6 yet.
What's new in PHP 8.6?
The headline is partial function application: str_replace(' ', '-', ?) creates a closure that waits for the missing argument, which pairs well with 8.5's pipe operator. 8.6 also adds clamp(), default values on readonly properties, a Time\Duration class, a SortDirection enum, a polling API and structured stream errors.
What breaks when upgrading from PHP 8.5 to 8.6?
Mostly configuration and deprecations. Sessions default to strict mode and HttpOnly, SameSite=Lax cookies, which can break cross-site POST logins such as SAML. Warnings from built-in functions drop their arguments, so logs lose file paths. spl_object_hash(), the mb_ereg*() functions and return in finally are deprecated, and your own global clamp() function or SortDirection class now collides with PHP's.
Should I upgrade to PHP 8.6 now?
Test now, and deploy where your stack is ready. 8.6 is supported a year longer than 8.5, but Laravel and Drupal don't list it yet, Xdebug supports it only in an alpha, and Ubuntu, Debian and Elastic Beanstalk don't offer it. PHP 8.5 is supported until 31 December 2029, so waiting for your framework and host costs little.
Do WordPress, Laravel and Symfony support PHP 8.6?
WordPress declared support on 10 November 2026, for WordPress 7.2, due 8 December 2026; 7.1 supports up to 8.5. Laravel's support table lists PHP 8.3 to 8.5 for Laravel 13. Symfony has made no formal statement, but its 7.4 and 8.2 branches are tested on 8.6 and it has merged 8.6 fixes into every maintained branch.
How do I install PHP 8.6 on Ubuntu?
Not from Ubuntu's own archive: 26.04 LTS and 26.10 ship PHP 8.5. Ondřej Surý's packages are the usual route: packages.sury.org has 8.6.0 for Ubuntu 22.04, 24.04 and 26.04, while his ppa:ondrej/php PPA had only a release candidate on release day. Or run the official php:8.6 Docker image.

Also on the calendar

End-of-life dates for the rest of your stack.

Dates checked against php.net’s own data, because endoflife.date doesn’t list this version yet. How we check datesReport a wrong dateEvery PHP version