The PHP team released PHP 8.6 on November 19. The new version brings partial function application, a Duration class for time spans, a polling API for scalable network servers and the long-awaited clamp() function, among other things. On the same day, security updates landed for every supported older branch: PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 fix a total of 17 vulnerabilities, seven of which the PHP project rates as critical. For anyone running PHP applications, the second item is the more urgent one.
PHP 8.6: The most important new features
The official release page sums up PHP 8.6 as “more expressive code, stronger types, and scalable I/O”. The main additions at a glance:
- Partial function application: Functions can be called with only some of their arguments. Placeholders such as
?and...mark the missing ones, and the result is a closure.fn ($v) => version_compare($v, '8.6', '>=')becomesversion_compare(?, '8.6', '>='). - \Time\Duration: A class for measured time spans, independent of clock time and time zone, with nanosecond precision over a range of more than 250 years. It suits timeouts and benchmarks. Durations are comparable, so
min()works directly. - Io\Poll: A new polling API monitors many streams at once via epoll, kqueue, event ports or WSAPoll, without the limits of
stream_select(), which typically struggles beyond about 1,024 connections. It is designed as a common foundation for event loop libraries such as ReactPHP and AMPHP. - clamp(): Restricts a value to a range, including non-numeric comparable values such as durations.
- SortDirection enum: A built-in, type-safe way to express sort order, instead of every library defining its own integers, strings or enums.
- Readonly defaults: Readonly properties can declare default values, so fixed values no longer have to be assigned in the constructor.
There are also smaller but practical improvements. Stream operations can now throw a StreamException with structured error objects instead of emitting warnings. Function parameters can carry their own DocComments, readable via reflection. The Sodium extension gains post-quantum key encapsulation with X-Wing and ML-KEM-768, and TLS streams support session resumption and TLS 1.3 early data. New builder classes make it easier to assemble URIs, and mysqli::quote_string() adds a counterpart to PDO::quote(). JSON error messages now include the location of the error in the input.
Breaking changes and deprecations
Reading the migration guide before upgrading pays off. Some changes directly affect existing code:
- Using
returninside afinallyblock is deprecated because it silently discards exceptions. - The mbstring regex functions such as
mb_ereg()andmb_split()are deprecated because the underlying Oniguruma library is no longer maintained. PCRE functions with theumodifier are the replacement. - Aliases such as
is_double(),is_long(),is_integer()anddoubleval(), as well asspl_object_hash()andstrcoll(), are deprecated. - Sessions are more secure by default:
session.use_strict_modeandsession.cookie_httponlyare enabled, andsession.cookie_samesiteis set toLax. trim()now also strips form feed characters, andfclose(),file_put_contents()andcopy()returnfalsewhen closing or flushing fails.
The new session defaults in particular may surprise older applications, for example where cookies were deliberately set without a SameSite attribute. Anyone who followed the release candidates will recognise many points from our report on PHP 8.6 RC3. According to the supported versions page, PHP 8.6 receives active support until the end of 2028 and security fixes until the end of 2030.
17 vulnerabilities: updates for PHP 8.2 to 8.5
Alongside the release, the PHP project published 17 security advisories on GitHub on November 19 at around 14:05 UTC. Seven are rated critical (CVSS 4.0: 9.2), four high and six medium. The flaws affect PHP-FPM, the session extension, time zone handling, SOAP, DOM and Phar, among others. The security team had announced the updates a day earlier, noting that the critical issues require non-default configuration or uncommon setups.
The most important critical vulnerabilities:
- CVE-2026-129289 (PHP-FPM request smuggling): Unread bytes from a request body can be interpreted as a separate request on reused FastCGI connections. An unauthenticated attacker can use this to execute PHP code with the worker’s privileges. Exploitation requires a front end with persistent backend connections, such as nginx with
fastcgi_keep_conn onor Apachemod_proxy_fcgiwithenablereuse=on. According to the advisory, standard configurations that close the connection after each request are not affected by the demonstrated attack. - CVE-2026-129474 (use-after-free in magic method backtraces): Affects PHP 8.5 only. Remote code execution has been confirmed but requires, among other things, a reachable magic method call and a fatal error at the right point. The PHP team lists
zend.exception_ignore_args=1orfatal_error_backtraces=0as workarounds. - CVE-2026-129496 (time zone cache): A use-after-free can crash workers or execute code when startup diagnostics occur and PHP errors are logged to a file.
- CVE-2026-115560 and CVE-2026-126714 (sessions): Mismatched session serializers or partially overwritten session files can lead to deserialisation and thus code execution if a suitable gadget chain exists. As a temporary measure, the project recommends disabling
session.upload_progress.enabledif the feature is not needed.
Among the high-severity flaws, CVE-2026-129291 stands out: an attacker who can already run PHP code in an FPM worker can execute commands with the privileges of the FPM master, which commonly runs as root, if catch_workers_output is enabled. CVE-2026-128090 allows bypassing the OpenSSL signature of Phar archives through an algorithm downgrade. The advisories do not list PHP 8.6 as an affected version.
What admins should do now
The clear recommendation is to update to 8.5.13, 8.4.28, 8.3.37 or 8.2.36, depending on the branch. Where that is not immediately possible, the workarounds above help, above all disabling FastCGI connection reuse in the web server. Anyone using packages from Linux distributions should check their security notices, as distributors often backport fixes without changing the version number. For PHP 8.2 the clock is ticking as well: the branch only receives security updates until December 31, 2026.
For new projects, PHP 8.6 is an obvious choice; for existing applications, a test run is advisable as always before frameworks and extensions officially catch up. Our Swoole benchmark already showed how capable PHP has become at asynchronous I/O. The new polling API could strengthen this area further once libraries such as ReactPHP and AMPHP adopt it.



