PHP 8.6 tightens session defaults and patches seven critical RCE flaws
Original title: PHP 8.6: Things are gonna get a lot more strict around here
Builds 8.5.13, 8.4.28, 8.3.37 and 8.2.36 were released with 8.6 to close those remote code execution bugs.
PHP 8.6, released Thursday, changes session defaults so Strict Mode, HttpOnly and SameSite start in more secure settings. The same coordinated release patched 8.5.13, 8.4.28, 8.3.37, 8.2.36 and 8.6, closing seven critical remote code execution flaws that could crash PHP workers or run code. Copied php.ini files can override the new defaults. Null-byte strings now raise errors instead of being ignored.
Unconfirmed: The article does not name the seven CVEs or say whether attackers exploited them.
- Strict Mode rejects session IDs that PHP itself did not create.
- Session cookies default to HttpOnly and are withheld on cross-site POST requests.
- An explicit session.use_strict_mode = 0 line overrides the new default.
- WordPress, Laravel and Symfony users had to update their PHP instances.
- Null bytes in strings now throw errors rather than passing silently.
Impact: Unauthenticated crash of PHP workers or remote code execution
| Product | Affected | Fixed in |
|---|---|---|
| PHP | — | 8.5.13, 8.4.28, 8.3.37, 8.2.36, 8.6 |
- 1.Install PHP 8.5.13, 8.4.28, 8.3.37, 8.2.36, or 8.6.
- 2.Remove overriding session.use_strict_mode = 0 lines in reused php.ini files.
- 3.Confirm applications do not disable the new HttpOnly and SameSite session defaults.
- Organizations
- PHP Foundation
From the original article
4 min read at theregister.comLike a parent disciplining a misbehaving child, PHP’s annual update clamps down on loose default behaviors to curb malicious hacker horseplay.
By Joab Jackson · theregister.com
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.