
On November 18, 2026, PHP warned users about several serious security flaws. All supported PHP versions are affected, though the most critical issues apply only to servers with specific settings. Fixes are expected on November 19, when PHP will also share more details about the bugs.
Impact: The upcoming fixes will cover multiple remote-code-execution (RCE) vulnerabilities. One expected CVE is CVE-2026-115560, an RCE in PHP’s session upload-progress feature that requires a specific session configuration to exploit. Other critical CVEs were not disclosed until patch time. Previously (Oct 21), PHP patched two CVSS 9.2 RCE flaws (PHP2Shell: CVE-2026-109618/109619) in versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35. This new release targets additional critical issues across PHP 8.2–8.5 branches.
Affected Versions: All supported branches will be updated (PHP 8.5, 8.4, 8.3, 8.2). (EOL versions such as PHP 8.1 and older remain unsupported and unpatched.) Users of any affected PHP release should plan to upgrade.
Remediation: Server administrators should install the new PHP security updates as soon as they are released on November 19. Until then, you can change some settings to reduce the risk of attacks.
One option is to disable PHP's session upload-progress feature. To do this, set session.upload_progress.enabled = 0 in your php.ini file and restart the PHP workers. This can help prevent attacks that use this feature.
Administrators should also check for custom session settings, such as session.serialize_handler, and return them to the default settings where possible.
Check PHP.net for the latest security updates and install the patched versions as soon as they become available.are available.
Immediate Actions for Sysadmins:
- Disable session upload progress: Set session.upload_progress.enabled=0 and restart PHP workers.
- Update PHP: Install the November 19 security updates as soon as they become available.
- Check session settings: Look for custom settings such as session.serialize_handler and switch back to the defaults where possible.
- Follow security updates: Check PHP.net for the latest information about the vulnerabilities, CVE numbers, and fixed PHP versions.