"with defaults that leave applications unnecessarily exposed." — Jörg Sowa
Thursday's release and the October emergency patching
On Thursday, PHP 8.6 was released on its usual yearly schedule, arriving in the wake of a troubling October run of newly unearthed vulnerabilities that allowed unauthenticated attackers to crash PHP workers or execute arbitrary code. The PHP core development community and the PHP Foundation coordinated a multi-version patch push — releasing patched builds 8.5.13, 8.4.28, 8.3.37, 8.2.36 and 8.6 — that closed seven critical remote code execution (RCE) flaws in one sweep.
The PHP Foundation publicly acknowledged that “consensus-driven gridlock” had delayed complex fixes for months and said it would aim to deliver patches sooner should vulnerabilities leak ahead of previously agreed deadlines.
Strict session defaults: Strict Mode, HttpOnly, and SameSite
PHP 8.6 implements Sowa’s proposal to make session-related configuration safer by default. The session extension will now enable Strict Mode by default, preventing PHP from accepting uninitialized session IDs it did not create itself. As Sowa explained, previously “an attacker could just plant a made-up session ID on the victim to gain entry,” because the handler would generate a fresh random ID when no session file existed for the attacker-planted ID.
PHP will also add the HttpOnly flag by default to session Set-Cookie headers, blocking client-side JavaScript from reading session IDs. And servers will withhold session cookies on cross-site POST requests, subrequests, and iframes; cookies will be sent only on same-site requests and on top-level GET navigations, such as clicking a normal link. Collectively, these defaults are intended to make session hijacking and cross-site request forgery attacks harder to execute.

Audit-ready is a season. It shouldn't be.
Evidence in spreadsheets, controls drifting between audits, frameworks multiplying on flat headcount. Nubivance runs continuous compliance on Rapid7 Cyber GRC - SOC 2, HIPAA, ISO 27001, PCI, CMMC.
End the scrambleStricter string handling and louder failures to reduce RCE surface
Beyond cookie and session defaults, PHP 8.6 tightens how the engine treats null bytes in strings. The runtime will be much stricter when it encounters strings with null values (“\0”), throwing errors in many cases rather than silently permitting the problematic input. The source explains why that matters: null values have been a favored trick for triggering RCEs because a C function can treat the null as the end of the string and ignore anything that follows, creating exploitable inconsistencies.
PHP 8.6 also changes behaviour for several functions so they no longer stay silent on failure. Operations such as closing a file or copying data will explicitly return false when they terminate prematurely or fail, producing an alert developers can use to catch and prevent data-integrity bugs that might otherwise be overlooked.
New developer-facing features: Partial Function Application, polling, Duration, clamp()
The release is not all hardening. PHP 8.6 introduces Partial Function Application (PFA), which allows developers to pre-fill some of a function’s arguments to create a reusable closure on the fly — a capability the source notes will “leapfrog JavaScript in this ability.” Other additions include a native polling API for event-driven networking, a Duration class that can measure elapsed time across more than 250 years, and a clamp() function to constrain a value within a specified range.
What this means for administrators, application maintainers, and users of WordPress, Laravel, and Symfony
- Administrators and DevOps teams: The new defaults only take effect if they are not overridden elsewhere. As backend engineer Rajekevin Dourepoulle warns, many deployments reuse an old php.ini (for example, via Ansible templates, a COPY php.ini in a Dockerfile, or files copied server-to-server). An explicit configuration line such as session.use_strict_mode = 0 in an existing php.ini will continue to override the new default after upgrading to 8.6, leaving deployments exposed unless those files are updated.
- Application maintainers (WordPress, Laravel, Symfony): Sites built on PHP-based frameworks or content-management systems are among those that scrambled during the October vulnerabilities. The hardening in 8.6 reduces attack surface, but maintainers must ensure that application-level configuration, frameworks, and packaging do not reassert the old, laxer settings.
- End users and operators: The tightened defaults aim to make session hijacking and cross-site request forgery more difficult to perform, and the stricter handling of null bytes should reduce the opportunity for RCE-style exploitation — but these protections depend on correct deployment and configuration.
PHP 8.6 is a two-pronged response: a rapid patch sweep that repaired seven critical RCE flaws, and a set of defaults designed to make common exploitation paths harder to follow. The changes will blunt many classically easy attacks, but they do not eliminate the need for timely patching and careful configuration. Administrators who simply upgrade the engine without revisiting copied or templated php.ini files may gain none of the intended protections.
For the record and further reading: Original story at The Register




