#2026
230 posts · Last used 6d
Set session.upload_progress.enabled=0 until the next PHP release to block an unlikely RCE vector (CVE-2026-115560).
We already recommended this for CVE-2026-109619 from Wednesday: keep it disabled.
Only applications with non-default serialize_handler switching it to php at runtime can be affected.
There is more information in the advisory on the PHP website by the PHP security team: https://www.php.net/archive/2026.php#2026-10-23-1
The PHP vuln advisory is a textbook example of how to do it right. Huge props to them!
https://www.php.net/archive/2026.php#2026-10-21-5
Specifically, it details:
-
what went wrong
-
what is and isn't known about who is affected (e.g. for the OOM one, Apache mod_php definitely is, FPM may be but isn't known)
-
what mitigations are available if patching/updating is not possible, and whether they are partial or full
-
sufficient information to roll your own further mitigations if needed (e.g. I think you could setup policies to terminate the process on OOM rather than letting it continue to the vulnerable OOM handler)
📣 Announcing the immediate availability of:
- PHP 8.2.35
- PHP 8.3.36
- PHP 8.4.27
- PHP 8.5.12
‼️ These address the following critical security issues:
- Remote Code Execution via Out of Memory corruption (CVE-2026-109618)
- Remote Code Execution via Stale Global State (CVE-2026-109619)
📝 https://www.php.net/ChangeLog-8.php
🎁 https://www.php.net/downloads?source=Y
Windows: https://www.php.net/downloads.php?os=windows
Read more: https://www.php.net/archive/2026.php#2026-10-21-5






