PHP 8.6.0 was released on November 19, 2026, the same day as security releases 8.5.13, 8.4.28, 8.3.37 and 8.2.36. With the release, the supported versions table on php.net now reads: 8.2 gets security fixes only until December 31, 2026; 8.4 leaves active support on that same date and gets only security fixes through the end of 2028; and 8.6 has active support until December 31, 2028 and security support until December 31, 2030.
On November 9 I wrote here about what changes in the PHP 8.6 session defaults. What is new is that the version has shipped and the 8.2 deadline is now six weeks away.
The schedule after November 19
Version | Active support until | Security until |
|---|---|---|
8.2 | ended (12/31/2024) | 12/31/2026 |
8.3 | ended (12/31/2025) | 12/31/2027 |
8.4 | 12/31/2026 | 12/31/2028 |
8.5 | 12/31/2027 | 12/31/2029 |
8.6 | 12/31/2028 | 12/31/2030 |
Active support includes ordinary bug fixes. In the security phase, the project only ships fixes for security issues. After that, no fix comes from php.net at all. The critical-severity flaws fixed on November 19 show the effect: from January on, a server running 8.2 will not get the next fix of that kind.
Who needs to act
Anyone still running PHP 8.2 in production, including on servers the team manages itself, is the group with a deadline. Teams on 8.3 have another year of security fixes, but have had no ordinary bug fixes since the end of 2025. Teams on 8.4 or 8.5 have no urgency.
Linux distributions and hosts that maintain their own packages may keep shipping fixes for 8.2 after December. That depends on each vendor and has to be confirmed with them; php.net does not guarantee it.
Where to migrate
To leave 8.2 there are two reasonable choices. Moving to 8.4 or 8.5 gives two to three years of security fixes and avoids, for now, the behavior changes in 8.6. Going straight to 8.6 gives the longest window, until 2030, but adds three versions of incompatible changes to a single round of testing, and the release is days old. With six weeks left, the first option fits most teams better. I wrote about this kind of choice in a supported version still calls for a migration decision.
Teams that choose 8.6 need to test more than sessions. The migration guide lists changes that do not show up as syntax errors:
trim(),ltrim()andrtrim()now also strip the form feed character (\f);fclose(),file_put_contents()andcopy()returnfalsewhen flushing the buffer fails, instead of ignoring the failure;- 19 file functions, such as
file_exists()andfilesize(), throwValueErrorwhen the path contains a null byte; - with
session.lazy_write, empty, unchanged sessions callupdateTimestamp()instead ofwrite(), which affects handlers that relied onwrite()to delete sessions; - in PDO for PostgreSQL, persistent connection state (
SETvalues, temporary tables) is reset when the last PDO object using it is destroyed.
8.6 also deprecates return inside finally, the mbstring regular expression functions (mb_ereg(), mb_split()), the is_integer(), is_long(), is_double() and doubleval() aliases, and custom session handlers that do not implement create_sid() and validateId(). Deprecated code still runs, but it logs a notice and signals removal in a future version.
What to do before December 31: list where 8.2 still runs (production, queue workers, scheduled jobs, CI images), pick the target, and run the test suite on it. After the move, check the deprecation notices in the log, since they show what will break at the next upgrade.
What is still unknown
WordPress's compatibility table, updated on November 4, goes up to PHP 8.5 and does not yet include 8.6. Until the project publishes its rating, WordPress sites should treat 8.6 as unvalidated. For plugins, themes and Composer packages, compatibility depends on each maintainer, and the only way to know is to test or wait for each announcement.
There is also no date for managed hosts to offer 8.6 or to remove 8.2 from their control panels.
If your company is weighing something similar, reach me on LinkedIn or WhatsApp.