CVE-2026-115560 and CVE-2026-126714 are two PHP vulnerabilities, both named Remote Code Execution, that involve the way PHP writes and reads session data. CVE-2026-115560 occurs when an application stores attacker-controlled data in a session using one serialization format and later reads the same session with a different one, so a mismatched decoder can treat part of a session key as object data. CVE-2026-126714 occurs when PHP’s default file-based session storage is interrupted partway through writing, which can leave old and new session data mixed together on disk.
In both cases, if the application reading the resulting session data contains a suitable chain of existing code, known as an object gadget chain, an attacker can get PHP to run commands with the privileges of the PHP worker process, the same process that serves the website. Without such a chain, the result can instead be session corruption or a crash.
Is CVE-2026-115560 and CVE-2026-126714 being exploited in the wild?
As of November 20, 2026, no exploitation in the wild has been reported.
How did CVE-2026-115560 and CVE-2026-126714 come to light?
PHP disclosed the session serializer mismatch, now tracked as CVE-2026-115560, in an informational advisory published on October 23, 2026, two days after it shipped fixes for the separate PHP2Shell vulnerabilities. PHP Foundation executive director Elizabeth Barron told The Register that the issue needed an unusual combination of configuration and application code, so the project planned to fix it in its regular release cycle rather than issue an emergency patch. The fix shipped on November 19, 2026, alongside the related session file write vulnerability, CVE-2026-126714.
How is watchTowr helping PHP customers?
Adversary Sight engine identified PHP instances across client environments and assessed exposure.
Rapid Reaction identified exposure to this vulnerability across the watchTowr client base, giving teams the time they need to act.
PHP is a scripting language that runs on web servers to generate the content of websites and web applications. Enterprises use it to power customer-facing sites, internal portals, and content management systems that process logins, sessions, and user-submitted data.
Which PHP versions are affected?
CVE-2026-115560 requires an application to configure one session serialization format and then switch to a different one at runtime, before starting the session.
Session upload progress, the feature that tracks file upload status, must remain enabled for CVE-2026-115560 to be reachable.
CVE-2026-126714 affects any application using PHP’s default file-based session storage, and is not limited to session upload progress or any specific PHP version.
A remote attacker needs the ability to send a file upload request that influences the contents later written to the session.
Security teams running applications that keep PHP’s default file-based session handler, which covers nearly all PHP deployments, should prioritize updating, since CVE-2026-126714 does not need an unusual configuration. Deployments that also switch session serializer formats at runtime carry the added exposure from CVE-2026-115560.
How do I fix CVE-2026-115560 and CVE-2026-126714?
The fix is to update to PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13, or 8.6.0, depending on the branch in use. Until updated, PHP recommends disabling session upload progress as a workaround, though this does not fully protect applications that independently store attacker-controlled data in sessions through the default file handler.
Inventory every PHP installation across the organization and note its version and session configuration.
Disable session upload progress administratively if immediate patching is not possible.
Update PHP to version 8.2.36, 8.3.37, 8.4.28, 8.5.13, or 8.6.0 for the branch in use.
Restart every PHP worker process after applying the update or any configuration change.
Check whether any application changes the session serializer format at runtime.
Confirm with Linux distribution or hosting vendors that backported patches have been applied.
What other vulnerabilities does the same bulletin fix?
The same PHP release fixed further vulnerabilities, including additional session and backtrace use-after-free issues (CVE-2026-129481, CVE-2026-129182, CVE-2026-129474), a timezone cache use-after-free (CVE-2026-129496), PHP-FPM request smuggling and privilege escalation issues (CVE-2026-129289, CVE-2026-129291, CVE-2026-129292), a PHP-CGI out-of-bounds issue (CVE-2026-129538), and lower-impact issues in PHAR, SOAP, and URI handling (CVE-2026-128090, CVE-2026-15353, CVE-2026-129506, CVE-2026-128064, CVE-2026-127960, CVE-2026-129501, CVE-2026-129438, CVE-2026-48841).
Is CVE-2026-115560 and CVE-2026-126714 related to earlier vulnerabilities?
CVE-2026-115560 shares a mitigation, disabling session upload progress, that PHP had already recommended for one of the two PHP2Shell remote code execution vulnerabilities patched on October 21, 2026. PHP disclosed CVE-2026-115560 two days after that release, before fixing it in the regular November update alongside CVE-2026-126714.
What types of threat actors typically exploit these vulnerabilities?
No attribution has been made public.
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
