· via Hacker News – Front Page (native)
PHP 8.6.0 ships with globals padding ABI fix, three CVE patches and partial function application
PHP 8.6.0 pads the engine's global structures to keep future patch releases ABI-compatible, fixes three CVEs including a CGI out-of-bounds flaw, and lands partial function application.

PHP 8.6.0 lands with engine-wide changes
Version 8.6.0 of PHP went out on 19 November 2026, according to the official changelog on php.net, which was surfaced on the Hacker News front page. (The Hacker News item itself carries the title "PHP 8.5.13", but the changelog text it points to opens with the 8.6.0 entries.) The release is more than routine maintenance: it changes how the engine lays out its internal globals, closes three security holes, adds a batch of language features and marks a long list of behaviours as deprecated.
Padding protects the engine's ABI
The first core entry in the changelog deals with a binary-level hazard: growing the engine's globals structures in patch releases risked breaking ABI compatibility, so 8.6.0 adds padding to those structures. That matters because compiled extensions assume the exact memory layout of the structures the engine exposes. If a patch release inserts a field, every offset after it shifts, and an extension built against the old layout can read and write the wrong memory — the kind of breakage that surfaces as sporadic crashes. Reserved padding gives future patch releases somewhere to put new fields without moving existing ones, which is exactly the sort of insurance production operators want. A related fix, GH-22422, addressed a zend_arena layout mismatch that leaked memory in separately built extensions under AddressSanitizer.
Three CVEs closed
The release fixes three security vulnerabilities. CVE-2026-129474 covers a use-after-free in backtraces of magic methods, which the changelog warns could enable remote code execution. CVE-2026-129182 covers a use-after-free triggered when the last_fatal_error_backtrace global is repopulated after shutdown. CVE-2026-129538 affects PHP's CGI executable, with an out-of-bounds read and write possible while PATH_INFO is being corrected. Anyone serving PHP through CGI has particular reason to schedule the upgrade.
Language and runtime additions
The headline feature is the partial function application RFC, which lets developers bind some arguments to a callable and receive a new callable back; as a bonus, array_map() calls that pass a partially applied callback now compile into a plain foreach loop. Elsewhere, the changelog lists clamp() as a new built-in, readonly properties gaining support for default values, and reference assignment on WeakMap no longer requiring the key to exist beforehand. Two caching additions — a stateless closure cache and a first-class callable cache that shares instances for the life of a request — aim at trimming object churn. A new error_include_args INI setting makes the display of function arguments consistent in error output. On the build side, the TAILCALL VM is enabled when compiling with GCC 16 or later, and on Windows with Clang 19 or later on x86_64, while ZTS builds move their allocator and scanner globals into native __thread storage and several TSRM structures become compile-time offsets.
Deprecations and behaviour changes
Reserved names take the brunt of the deprecations: "let" and "is" as names for classes, functions, constants or aliases; "_" as a constant name or alias; "namespace" as a class constant name; and "readonly" as a function name. Also deprecated: returning values from constructors and destructors, using return inside a finally block, passing a third argument to define(), declaring a nullable return type on __debugInfo(), and calling is_a() or is_subclass_of() with a string first argument while $allow_string is false. On the behaviour front, a hard out-of-memory now calls abort() rather than exit(), base-conversion functions such as base_convert(), hexdec() and octdec() emit a notice when a value cannot be converted precisely, and run-tests.php runs in parallel by default with up to ten auto-detected workers, falling back to -j1 for sequential execution.
Fixes production teams should note
Among the many bug fixes, several stand out. Incompatible OPcache file cache entries could be reused after an Apache graceful restart because a system ID was not reinitialized (GH-24184). Fibers saw two corrections: a catch block could be skipped when execution switched fibers during exception unwinding, and fibers started with error_reporting set to 0 when the INI directive was unset. A segfault in the tracing JIT when the memory limit is reached mid-call (GH-18847) and a stack overflow when internal functions recurse through zend_call_function are both fixed. The curl extension gains CURLOPT_SEEKFUNCTION, letting libcurl rewind streamed request bodies for redirects, multi-pass authentication or retried connections; it can now post bodies larger than 2GB on some platforms and fixes use-after-frees on cloned handles. BCMath functions also gained NUL-byte validation.
Why it matters
A x.y.0 release is where PHP's language moves, and 8.6.0 delivers real additions in partial function application and clamp(), while its deprecations are advance notice of stricter enforcement to come. But the quieter entries carry the operational weight. The globals padding is insurance against extension breakage across patch updates, the three CVEs argue for bumping deployments sooner rather than later, and the switch from exit() to abort() on hard OOM changes what a memory-limit death looks like in logs and crash reporting — monitoring tuned for clean exits should be reviewed. Teams running compiled extensions or PHP via CGI have the most to gain from moving early.
- #php
- #security
- #release-notes
- #runtime
- #web-development