Hackerparagraph,IT-Security, Linux  Image © DALL-EHackerparagraph,IT-Security, Linux (Image © DALL-E)

Although today's release addresses critical security vulnerabilities, the PHP Foundation points out that the systemic risk is lower than during the PHP2Shell crisis in October. PHP2Shell affected millions of systems worldwide and forced many administrators to take servers offline until patches could be installed. It was utter chaos because the information was leaked prematurely and patches were not immediately available.

In contrast, the vulnerabilities in the current cycle are said to depend largely on specific and unusual system configurations. While the impact on users with vulnerable configurations remains severe, the total number of affected systems is expected to be significantly lower than in previous critical incidents.

PHP Versions and End-of-Life Dates

Security patches are being provided for all supported main branches, specifically versions 8.5, 8.4, 8.3, and 8.2. Administrators are urged to exercise caution regarding version 8.2, as its end-of-life date is December 31. Users currently running version 8.2 are advised to plan a migration to a newer, supported branch in order to continue receiving security updates beyond the end of the year. Technical details and specific version numbers are expected to be announced alongside the release.

CVE-2026-115560

One of the main focuses of this release is the resolution of CVE-2026-115560. The PHP Foundation had previously indicated that a patch for this specific vulnerability would be delayed until the regular release cycle due to the very limited attack vector.

The vulnerability can only be exploited under very specific conditions:

    1. The system configuration for session.serialize_handler must be set to either php_binary or php_serialize.
    1. The handler must then be changed to php at runtime using the ini_set() function.
    1. This change must be made before the session_start() function is called.

For environments that meet these criteria and cannot apply the upcoming patch immediately, the PHP Foundation recommends a temporary workaround. Disabling upload progress for sessions by setting session.upload_progress.enabled=0 in the configuration file can effectively neutralize the attack vector until the official update is released.