PHP CVE-2026-115560: CVSS 9.2 session flaw, upgrade now

A critical PHP flaw can let an attacker inject session objects and run code. See affected versions, how to check one server and how to fix it.

CVE-2026-115560: CVSS 9.2: upgrade PHP

TL;DR

  • What: a PHP flaw, CVE-2026-115560, where two parts of an application disagree on the session format, which can end in an attacker running code.
  • Impact: a remote attacker who can submit a multipart upload may inject objects into the session. That can mean code execution if the application holds a suitable gadget chain, or session corruption and denial of service.
  • Severity: a CVSS v4.0 score of 9.2, rated critical.
  • Exploited: no source we checked says it is exploited yet. It was published on November 19, 2026.
  • Fix: upgrade to PHP 8.2.36, 8.3.37, 8.4.28 or 8.5.13, whichever matches your line, and keep your session serializer settings identical across applications.

What the flaw is, in plain English

PHP stores a user's session data on the server and reads it back on later requests. It can write that data in more than one format, called a serializer. The session.serialize_handler setting chooses which one is used. CVE-2026-115560 is about what happens when the format used to write a session is not the format used to read it.

The trigger is a feature called session upload progress. When it is enabled, PHP records the progress of a file upload inside the session. According to the NVD description, with the php_binary or php_serialize serializer, an attacker can control bytes inside a session key. When that session is afterwards read with the plain php serializer, those bytes can reach the unserializer. That is the weakness catalogued as CWE-502, deserialization of untrusted data, alongside CWE-20, improper input validation.

In practice, that means an attacker who can send a multipart upload to your site may be able to place objects of their choosing into a session. Whether that becomes code execution depends on your application: it needs a suitable gadget chain, which is a class already loaded by the application that does something dangerous when it is rebuilt. Without one, the likely result is a corrupted session or a crash.

Why it matters now

PHP runs a very large share of public websites and back ends, including content management systems and online stores. A flaw that a remote attacker can start with nothing more than an upload request is attractive to automated scanners, and the fixed versions are now public, which lets attackers compare the patch with older code.

The conditions make this less universal than some bugs, and the CVSS v4.0 vector from NVD reflects that the attack is not trivial. But the conditions are not exotic. Many teams run several applications that share one session store, and many frameworks change PHP settings at runtime. If either describes your estate, you should assume you are in scope until you have checked. It is also the kind of issue that hides: nothing in a version banner tells you whether two applications disagree about their serializer.

We covered the previous wave of PHP trouble in CISA adds two PHP remote code execution flaws to its KEV list. That one was already being exploited; this one is not yet reported as exploited, which is exactly the window in which patching is cheapest.

Am I affected?

The description lists the affected releases as four lines of PHP: versions before 8.2.36, before 8.3.37, before 8.4.28 and before 8.5.13. NVD had not attached a structured list of affected products when we read the entry, so use the description and the vendor advisory linked below as the authority.

To check one machine by hand, start with the version and the two settings that matter:

php -v
php -i | grep session.serialize_handler
php -i | grep session.upload_progress.enabled

Remember that the command line PHP can differ from the one your web server uses. Check the version the web server actually loads, for example from a page that prints it, or from the package manager of the host. If your site runs under PHP-FPM, check the FPM binary and its pool configuration rather than the command line one.

Two further points help you judge exposure:

  • If upload progress is off and nothing changes it at runtime, the described trigger is not present. Still upgrade, because settings drift.
  • If several applications share one session store, compare their serializer settings. A mismatch between them is the situation the description warns about.

Distribution backports. Debian, Ubuntu, Red Hat and other distributions often fix a flaw without changing the upstream version number, so a package that still reports an older version may be patched. Do not decide from the version string alone: read your distribution's security tracker for this CVE and the changelog of the installed PHP package. Packages from vendor repositories such as Ondřej Surý or Remi follow the upstream numbering more closely.

How to fix CVE-2026-115560

  1. List every PHP runtime you operate: servers, containers and build images. Write down the version of each and which line it belongs to.
  2. Upgrade to the fixed release of your line: 8.2.36, 8.3.37, 8.4.28 or 8.5.13, or a later release. If your distribution ships its own package, install its security update instead and confirm in its changelog that this CVE is listed.
  3. Restart PHP-FPM or the web server so the new binary is actually loaded, then check the running version again with php -v and from the web server.
  4. Compare session.serialize_handler across every application that shares a session store, and make them identical. Avoid changing it at runtime inside application code.
  5. If nothing in your applications needs upload progress, turn off session.upload_progress.enabled. This removes the condition the description names, but it is a stopgap and not a replacement for the upgrade.
  6. Read the PHP project's security advisory, linked in Sources, for anything specific to your release, and review web logs for unusual multipart uploads from before you patched.

The NVD entry does not give a fixed version as structured data, so the version numbers above come from the description's own wording. Confirm them against the vendor advisory before you roll out.

How to check with Stackurity

Checking one server by hand is fine. Checking every server, container image and build pipeline owned by different teams is where this kind of issue slips through.

Stackurity keeps one live inventory of the software on your servers, deployed applications, repositories and container images, and matches it against new vulnerability advisories every hour. Its read-only agent finds PHP on Linux servers, including PHP from Ondřej Surý or Remi, and, when you opt in with the --docker flag, in the images of running containers. When an advisory matches, the finding names the version in use and the version to move to, and one fix groups every place that needs the same upgrade. The remediation documentation explains how fixes are ordered, most urgent first.

After you upgrade, Check again asks the agent for a fresh report and records whether the issue is really gone, so you do not have to take a ticket status on trust. There are limits. Stackurity does not cover appliance firmware or libraries copied into an application outside a package manager. It also does not read your serializer settings, so the configuration steps above are still a manual check.

Start a free trial of Stackurity to see which of your servers and images run PHP today.

FAQ

What is CVE-2026-115560?

It is a critical PHP flaw in how session data is read back. When session upload progress is enabled, attacker-controlled bytes can end up in a session key. If a different session serializer later reads that session, those bytes can be passed to the unserializer, which can let an attacker inject objects.

Which PHP versions are affected?

The advisory text names four lines: versions before 8.2.36, before 8.3.37, before 8.4.28 and before 8.5.13. Upgrade to the fixed release of your line or a later one.

Is CVE-2026-115560 exploited in the wild?

No source we checked says so, and we have not seen it in the CISA Known Exploited Vulnerabilities catalogue. It was published recently, so treat the patch as urgent anyway, especially for sites that accept file uploads from the internet.

Does every PHP site have this problem?

No. The description sets conditions: session upload progress must be enabled, and the session must later be read with a different serializer than the one that wrote it. That can happen when the setting is changed at runtime or when applications that share a session store use different settings.

Is there a workaround if I cannot patch today?

The description gives no official workaround. Checking that every application on a shared session store uses the same serializer, and turning off upload progress where nothing needs it, removes the conditions it names. Both are stopgaps, so still plan the upgrade.

Does Stackurity find vulnerable PHP versions?

Yes, for server software it finds on Linux servers and in images, including PHP from Ondřej Surý or Remi. It does not cover appliance firmware or libraries copied into an application outside a package manager.

Sources: NIST National Vulnerability Database, CVE-2026-115560; PHP project security advisory. See also our end-of-life guide for an older PHP line.