Critical PHP Security Release: CVE-2026-115560, Remote Code Execution Risks and WAYSCloud Preparedness
Summary
The PHP Security Team has announced a critical security release scheduled for 19 November 2026 between 14:00 and 14:30 UTC (15:00–15:30 CET), expected to address multiple vulnerabilities across supported PHP versions. The highest severity in the release is classified as Critical.
One publicly documented vulnerability expected to be addressed is CVE-2026-115560, a potential remote code execution issue involving PHP session upload progress and session serialization handling. It requires a specific combination of session configuration and runtime changes to the session serialization handler, so the presence of a vulnerable PHP version does not by itself mean that an installation is exploitable.
WAYSCloud is preparing to evaluate the release against its managed infrastructure, Shared Hosting services and eligible customer environments, while providing guidance for independently managed workloads. This advisory is published ahead of the release to give customers early technical information and recommended precautionary measures. This report will be updated in place — same URL — when the release is published, expected between 15:00 and 15:30 Norwegian time (14:00–14:30 UTC) on 19 November 2026.
PHP has confirmed that the release contains critical vulnerabilities, but has not attributed that severity to CVE-2026-115560 specifically. No CVSS score is assigned to that CVE in this advisory. No determination of WAYSCloud customer impact or compromise is made by this preliminary advisory.
Status and Expected Update
Update expected: 19 November 2026, 15:00–15:30 Norwegian time (14:00–14:30 UTC).
PHP is scheduled to publish the full advisories, affected versions and fixed releases in that window. This report will be updated in place, at the same URL, with the documented patch status: what WAYSCloud has deployed in managed scope, what remains for customer-managed workloads, and the verified outcome. No separate follow-up report will be published for the same event.
This is a preliminary advisory. It contains no CVSS score for CVE-2026-115560: PHP has confirmed that the release contains critical vulnerabilities, but has not attributed that severity to this specific CVE.
CVE-2026-115560: PHP session upload progress and RCE risk
CVE-2026-115560 concerns the interaction between PHP's session upload progress functionality and the mechanism used to serialize and deserialize session data.
PHP supports several session serialization handlers, including php, php_binary and php_serialize.
The vulnerability arises under a specific combination of application configuration and execution behaviour, in which session data may be processed using a serialization format different from the one used when the data was originally written.
According to PHP's informational advisory of 23 October 2026, the vulnerable condition requires:
- The application to configure session.serialize_handler as php_binary or php_serialize.
- Application code to subsequently change the handler to php using ini_set(), before calling session_start().
- The PHP session upload progress feature to remain enabled.
Under these conditions, attacker-influenced session upload progress data may be interpreted unexpectedly during session deserialization, potentially creating a remote code execution path.
The security implications depend on application behaviour and the availability of exploitable object-deserialization paths. PHP has characterised this as an unlikely configuration combination rather than a universally exploitable vulnerability affecting all PHP applications.
Why this matters
PHP is widely used across shared hosting environments, content management systems, web applications, APIs and custom application platforms. An RCE vulnerability within a PHP runtime can potentially affect the confidentiality, integrity and availability of the application and its associated data.
However, CVE-2026-115560 requires specific preconditions. Applications that do not modify the session serialization handler at runtime do not meet the configuration sequence identified by PHP for this vulnerability. Administrators should therefore evaluate the actual configuration and behaviour of their applications rather than assuming that every PHP deployment is exposed.
Recommended Immediate Mitigation
Before the security updates become available, PHP recommends disabling session upload progress as a precautionary measure against the identified vulnerability. The recommended configuration is:
- session.upload_progress.enabled=0
This setting should be applied through the appropriate PHP configuration, such as php.ini, a PHP-FPM pool configuration or another supported server-level configuration mechanism that takes effect before request parsing.
Changing this setting through application-level ini_set() calls or PHP-FPM .user.ini files is not sufficient for the relevant early request-processing stage. Affected PHP workers must be restarted to ensure that the configuration is applied.
Administrators should also review application code for runtime changes to session.serialize_handler, especially transitions from php_binary or php_serialize to php.
Disabling session upload progress may affect applications that explicitly depend on this functionality. Such applications should be tested accordingly.
This configuration change is a targeted mitigation for the known CVE-2026-115560 attack condition. It should not be considered a substitute for the complete security updates or protection against other vulnerabilities in the upcoming release.
Relationship to the October 2026 PHP2Shell Vulnerabilities
The November security release follows the critical PHP vulnerabilities disclosed in October 2026:
- CVE-2026-109618: Remote code execution risk involving out-of-memory handling and memory corruption.
- CVE-2026-109619: Remote code execution risk involving stale internal state and references between requests.
- CVE-2026-115560: A separately identified vulnerability involving session upload progress and serialization handler changes.
The mitigation involving session.upload_progress.enabled=0 was previously recommended in connection with CVE-2026-109619 and subsequently reiterated for CVE-2026-115560. Consequently, environments that implemented and retained this mitigation during the October response may already have protection against the specific CVE-2026-115560 attack condition.
However, the security updates deployed in October should not be assumed to resolve vulnerabilities scheduled for disclosure in November.
WAYSCloud's previous response
On 23–24 October 2026, WAYSCloud conducted an emergency remediation programme addressing CVE-2026-109618 and CVE-2026-109619. The initial patch deployment and runtime verification were completed across identified affected PHP installations within WAYSCloud's managed scope in approximately two hours. Additional application-level remediation and functional verification followed.
The response is documented in WAYSCLOUD-TR-2026-0029: Critical PHP Vulnerabilities: Emergency Response and Coordinated Remediation.
The November disclosure represents a separate vulnerability assessment requiring its own verification and remediation decisions.
WAYSCloud Assessment and Remediation Scope
WAYSCloud's assessment of the upcoming PHP security release will distinguish between directly managed infrastructure, services covered by individual management agreements and independently operated customer workloads.
Shared Hosting: PHP runtime security updates are managed by WAYSCloud for the underlying shared hosting infrastructure. Applicable fixes will be assessed and deployed through the platform's maintenance processes.
Managed Virtual Machines and SLA-Covered Services: Customer environments covered by relevant runtime or operating system management agreements will be assessed according to the agreed management scope.
Customer-Managed Virtual Machines: Customers administering their own guest operating systems and PHP installations remain responsible for applying applicable PHP security updates.
Kubernetes and Container Workloads: PHP runtimes embedded in customer-managed container images must be assessed, updated and redeployed by the workload owner. Updating the Kubernetes control plane, worker nodes or underlying cloud infrastructure does not automatically update PHP within application containers.
The applicability of the upcoming security fixes to individual environments must be established from the final vendor advisories and actual runtime configurations.
Customer Actions Before and After Release
Customers operating PHP environments are advised to review their installed runtimes and application configurations immediately.
Particular attention should be given to the session upload progress feature, non-standard session serialization settings and application code modifying session configuration at runtime.
Where appropriate, administrators should apply the targeted mitigation described above and verify that it takes effect across all relevant PHP worker processes.
Following publication of the security releases, administrators should:
- Review the final PHP security advisories and affected-version information.
- Deploy relevant updates using official PHP releases or vendor-maintained security packages.
- Restart affected PHP processes or redeploy container workloads.
- Verify the effective runtime versions and configuration settings.
- Perform functional checks on dependent applications and services.
- Review relevant security events and investigate unusual behaviour where appropriate.
Linux distribution maintainers may deliver backported security fixes without adopting the latest upstream PHP version number. Administrators should confirm patch status through the applicable vendor's security advisories.
Disclosure Status and Pending Information
At the time of this advisory, the PHP Security Team has confirmed the scheduled security release and its highest severity classification.
However, several important details remain pending official publication:
- The complete list of vulnerabilities addressed by the release.
- The final affected and fixed PHP versions.
- Individual severity ratings and exploitation prerequisites for each issue.
- The full technical advisory for CVE-2026-115560.
- The applicability of any additional vendor-specific mitigations.
No determination of WAYSCloud customer impact or compromise is made by this preliminary advisory. The available information warrants preparation and precautionary action, but does not establish active exploitation or compromise of any WAYSCloud-hosted environment.
Ongoing Security Monitoring
WAYSCloud will review the official PHP security disclosures as they become available and assess their applicability to the platform's managed service portfolio.
This advisory will be updated to distinguish confirmed vendor findings, verified remediation activity, remaining exposure and any material operational impact.
Our priority is to act early, communicate accurately and ensure that customers understand both the technical risks and their responsibilities under the shared responsibility model.
The WAYSCloud Trust Center provides a public record of relevant security responses, vulnerability assessments and remediation outcomes.
