The short version
- The release. PHP plans security releases for all supported versions on 19 November, between 14:00 and 14:30 UTC, as part of its regular four-week cycle. The highest severity is critical, though PHP says those issues need non-default configuration or uncommon setups.
- One CVE is already public. One expected fix is CVE-2026-115560, a remote code execution vector in PHP's session upload progress feature. PHP published an informational advisory on 23 October and said the full advisory would come with the next regular release.
- Who is exposed. An application is exposed to CVE-2026-115560 only if its configuration sets session.serialize_handler to php_binary or php_serialize and its code switches the handler to php at runtime, with session upload progress still enabled.
- The October fixes are separate. CVE-2026-109618 and CVE-2026-109619 were fixed on 21 October in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Those releases do not include a fix for CVE-2026-115560.
- Still unpublished. PHP has not published the full CVE list, affected versions or fixed version numbers for the 19 November releases. It says technical details will appear alongside them.
Timeline
| Date | Event |
|---|---|
| 21 October | PHP releases 8.5.12, 8.4.27, 8.3.36 and 8.2.35, fixing critical remote code execution flaws CVE-2026-109618 and CVE-2026-109619. |
| 23 October | PHP publishes an informational advisory for CVE-2026-115560 and says a full advisory will follow with the next regular release. |
| 18 November | PHP announces critical security releases for 19 November; Aikido Security reports that CVE-2026-115560 is expected among them. |
| 19 November | Releases scheduled for 14:00 to 14:30 UTC, with fixed version numbers and technical details to be published then. |
What PHP has announced
PHP's security team said on 18 November that it will ship security releases for every supported PHP version on 19 November between 14:00 and 14:30 UTC, as part of its regular four-week cycle. The highest severity is critical. PHP says the issues rated critical require either non-default configuration or uncommon setups, and that fixed version numbers and technical details will be published alongside the releases.
At the time of the announcement the full CVE list and the fixed versions were not public. Aikido Security, which is tracking the release, says the same and notes that one CVE in the set is already known: CVE-2026-115560.
The flaw that is already public
On 23 October PHP published an informational advisory for CVE-2026-115560, a remote code execution vector in session upload progress, and said a full advisory would come with the next regular release. According to Aikido Security, the 19 November releases are that next regular release. PHP has not published affected versions or a severity score for this CVE.
PHP says an application can only be affected if its configuration sets session.serialize_handler to php_binary or php_serialize, then switches it to php at runtime with ini_set() before calling session_start(), and session upload progress is still enabled. Applications that never change the handler at runtime can keep the feature enabled. PHP advises setting session.upload_progress.enabled=0 until the fix lands, a mitigation it had already listed for CVE-2026-109619 in October. Aikido Security adds that the setting must apply before request parsing, so it has to go in php.ini, an FPM pool or server configuration rather than ini_set() or a .user.ini file, and that PHP workers need restarting.
The October flaws and what is unresolved
CVE-2026-109618 and CVE-2026-109619 are a separate pair of critical flaws that PHP fixed on 21 October in 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP describes one as an out-of-memory handling corruption and the other as stale global state surviving between requests; both allow unauthenticated remote code execution. PHP rated the risk highest for mod_php, where it said a demonstrated exploit can trigger before application code runs. Aikido Security refers to the pair as PHP2Shell. The 21 October releases do not fix CVE-2026-115560.
No source links the 19 November releases to the October flaws beyond both being part of the same release cycle, and the sources do not say what else the new releases address. PHP notes that version 8.1 and older no longer receive updates from the project, though some distributions and long-term-support vendors provide backported fixes; PHP published minimal source backports for 7.4, 8.0 and 8.1 for organisations that build from source.
What is not known yet
- Which CVEs, affected versions and fixed version numbers the 19 November releases cover, beyond CVE-2026-115560.
- The severity score and full impact of CVE-2026-115560.
- Whether any of these flaws have been exploited in the wild.
- Who reported or discovered the vulnerabilities.
- Whether the PHP 8.6.0 general release, also planned for 19 November, carries the same fixes.
What to do
If you run PHP
- Set session.upload_progress.enabled=0 in php.ini, an FPM pool or your server configuration, not through ini_set() or a .user.ini file, so it applies before request parsing.
- Restart every PHP worker so the setting takes effect.
- Search your code for runtime ini_set() calls that switch session.serialize_handler to php; applications that never do this can leave session upload progress enabled.
- Install the 19 November releases, or your distribution's packages, once PHP publishes them at 14:00 to 14:30 UTC.
If you have not applied the 21 October fixes
- Update to the 21 October releases, beginning with PHP 8.5.12 in the 8.5 branch, rather than waiting; see PHP's advisory for the other branches.
- If you run PHP 8.1 or older, contact your distribution or long-term-support vendor for backported fixes or move to a supported version, since the project no longer updates those branches.
- If you cannot update, apply PHP's interim measures for CVE-2026-109618, including memory_limit=-1 set where applications cannot override it, a low post_max_size, and request size and structure limits at the web server or proxy.
For everyone else
- Treat a critical rating that depends on non-default configuration as a prompt to audit how your systems are actually configured, not only which versions they run.
- Track PHP's four-week release cycle so critical patches can be scheduled and applied without waiting for the next maintenance window.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.