PHP prepares a critical patch: how to reduce the risk of CVE-2026-115560

PHP prepares a critical patch: how to reduce the risk of CVE-2026-115560

PHP announced a security update for all supported versions, scheduled for November 19, 2026, between 14:00 and 14:30 UTC. The CVE-2026-115560 vulnerability may allow remote code execution, but it requires an unusual combination of options and application code.

Who may be affected

The advisory applies to all supported PHP versions, but the presence of the vulnerability does not depend on the version alone. According to PHP, an application must set session.serialize_handler to php_binary or php_serialize and, before calling session_start(), change it to php using ini_set().

In addition, session upload progress must remain enabled. PHP says this option is enabled by default. If the application never changes the serialization handler at runtime, it can keep the upload progress feature enabled, according to the project's advisory.

Therefore, simply checking the interpreter version number is not enough to determine whether a particular application uses this path. You need to review the session configuration and the code that initializes sessions, including changes made at runtime.

What to do before the patch

  1. Check the mitigation setting. PHP recommends setting session.upload_progress.enabled=0 until the next regular bug-fix release. If you already made this change in response to the earlier advisory about CVE-2026-109619, PHP says you should keep it and do not need to repeat the action.

  2. Review the effective configuration. Check the configuration files used by each PHP instance and environment, and confirm whether upload progress is disabled. Do not assume that development, testing, and production share the same settings. The official advisory specifies the directive's value, but does not provide a menu path or a specific file that applies to all installations.

  3. Look for handler changes in the code. Find uses of ini_set() related to session.serialize_handler and verify whether the program changes the value to php before executing session_start(). Compare that code with the initial configured value: the combination described by PHP includes php_binary or php_serialize as the starting configuration.

  4. Determine whether the conditions match. The described path requires both a runtime handler change and session upload progress to be enabled. If the application does not change the handler at runtime, PHP says it can keep this feature enabled. If the code does make the change, keep the mitigation in place until you install the fix.

  5. Restart PHP processes. The Hacker News notes that PHP workers must be restarted for the mitigation setting to take effect. Do this after changing the configuration and check that the instances serving the application have restarted with the updated value.

  6. Install the released update. PHP scheduled the release for November 19, between 14:00 and 14:30 UTC, and recommends applying updates as soon as they are available. Check the announcement and the package for your installation before deploying it; the available material does not specify target version numbers.

  7. Remove the mitigation only with care. PHP recommends disabling upload progress until the next regular bug-fix release. After updating, consult the full CVE-2026-115560 advisory and the instructions for the installed version before deciding whether to re-enable the feature.

PHP prepara un parche crítico: cómo reducir el riesgo de CVE-2026-115560
© php.net

The combination to check

ConditionWhat to check
Configured handlersession.serialize_handler uses php_binary or php_serialize.
Runtime changeThe code changes the handler to php with ini_set() before session_start().
Upload progresssession.upload_progress.enabled remains enabled.

PHP describes the flaw as an unlikely remote code execution path that requires this combination. The critical rating for the upcoming release covers vulnerabilities whose exploitation may require a non-default configuration or uncommon environments; the project did not publish further details about the other issues before the update.

Mistakes to avoid

Do not rely solely on the configuration being standard. The condition includes application code that changes the handler at runtime. A review limited to configuration files may miss this part; inspect session initialization as well.

Do not forget to restart the workers. Changing the value without restarting PHP processes may leave the mitigation unapplied in processes that are still handling requests. Verify the restart on every relevant instance.

Do not confuse the security advisories. CVE-2026-115560 is the issue addressed in the upcoming release described here. PHP2Shell refers to CVE-2026-109618 and CVE-2026-109619, which were fixed the previous month; The Hacker News reported limited exploitation of those earlier vulnerabilities. They are not the same flaw and do not eliminate the need to check for the new patch.

Do not leave the mitigation in place indefinitely as a substitute for the update. The PHP setting is temporary, until the next regular bug-fix release, and the project recommends installing updates as soon as they become available.

Sources: The Hacker News, theregister, php.net, PHP.net, PHP.net