· via dev.to (home feed)
PHP 8.6 ships partial function application and a polling API as security releases patch 7 critical bugs
PHP 8.6 adds partial function application, a nanosecond-precision Duration class and a multi-stream polling API, while security releases for every supported branch fix 17 advisories, seven of them critical.

PHP 8.6 arrives
PHP 8.6 was released on November 19, 2026, according to This Week in PHP Internals on dev.to, and the feature list leans heavily on ergonomics and concurrency.
The headline is partial function application: a developer can supply some of a function's arguments, mark the remaining ones with a question mark, and get back a closure that accepts the rest later. A new Duration class models elapsed time with nanosecond precision, so values such as timeouts no longer have to be bare microsecond counts. A new polling API can watch many streams at once, using epoll on Linux, kqueue on macOS and equivalents elsewhere, and it is intended as a common base for event-loop projects such as ReactPHP and AMPHP.
Smaller changes include clamp, which keeps a value inside a range, a SortDirection enum, and default values for readonly properties. Sessions ship safer defaults too, with strict mode and HTTP-only cookies enabled and SameSite set to Lax. The php.net release page documents every headline feature with before-and-after code and a link to the relevant RFC.
Security releases for every supported branch
The same day brought security releases for all supported versions — 8.5.13, 8.4.28, 8.3.37 and 8.2.36 — and PHP 8.6.0 carries the same fixes. There are 17 advisories in total, seven of them critical. The pre-announcement offered some comfort: the critical issues are said to require either non-default configuration or uncommon setups, and each advisory spells out which setup it applies to.
Three of the critical advisories concern sessions. One is the upload-progress problem PHP warned about in October, in which data written in one session format was read back in another. The fix goes further than October's advice and disables upload progress by default; anyone who turned it on manually keeps it on, but everything reading or writing those sessions must then use the same serializer. Another critical flaw sits in PHP-FPM and only matters when a web server keeps its connections to FPM open between requests — the post notes that standard nginx and Apache configurations close them and are not affected.
A timezone cache bug found by method
One critical bug was found by Sebastian Bergmann, creator of PHPUnit, who described the hunt in a write-up called 'The wrong crash'. Bergmann had earlier reduced a pair of PHP bugs to a machine-checkable rule: after a request ends, no data that lives on may hold a reference into that request's memory. While using the check to confirm an October fix, it crashed where it should not have — on the patched build too — which meant a new bug.
The cause was PHP's timezone cache. When PHP writes to its error log during startup, it can cache timezone data for the timestamp in memory that is discarded once startup ends. The pointer survives, and a fresh worker can follow it. The fix is a one-line change: outside a running request, such timestamps are written in UTC. Teams that cannot update immediately are advised to clear whatever PHP warns about at startup and restart, or to log to syslog. The advisory credits Bergmann and Go Kudo, and Bergmann handed his detection method to the PHP team along with the report.
Meanwhile in internals
Two RFCs moved in opposite directions. Sjoerd Langkemper's openssl_get_channel_binding proposal, meant to expose TLS channel-binding data that mail software such as Roundcube needs for SCRAM-PLUS logins, was withdrawn hours after a vote was announced, following objections from openssl maintainer Jakub Zelenka that one binding type fails on TLS 1.3 and that the API belonged in stream functions rather than the openssl extension. Separately, Xavier Leune proposed CURLOPT_OPENSOCKETFUNCTION, a curl callback that runs after DNS resolution and before each connection, so SSRF policies apply to the address actually being contacted, on every redirect hop, rather than to a URL that can be spelled many ways. Frode Børli's Scope RFC also churned through revisions in roughly 30 hours of debate with Larry Garfield, landing on request arrays becoming scope globals that start empty, like a new process's globals.
Why it matters
The feature set pushes PHP further into functional and asynchronous territory: partial application makes composition cheaper, and a shared polling primitive could consolidate event-loop plumbing that ReactPHP and AMPHP each maintain today. The security release is the more urgent half. Seven critical advisories is a lot, and although they mostly target non-default setups, the deployments most exposed are precisely the unusual ones — and each advisory now names its conditions, so operators can check quickly. Two defaults changed with 8.6 as well, upload progress off and stricter session settings, which may need attention from applications that relied on the old behaviour. With Bergmann's detection method now in the PHP team's hands, more bugs of the same class may surface in future releases.
- #php
- #security
- #release
- #open-source
- #web-development