← All updates

Security / News explained

PHP’s November security releases reach beyond one configuration switch

PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 fix several security issues. Session storage and persistent backend connections need different readings of the advisories.

By Zyel · Published · 4 min read

PHP released security updates for four existing branches on November 19, 2026: 8.5.13, 8.4.28, 8.3.37 and 8.2.36. The same day also brought PHP 8.6.0’s feature release. Application owners can therefore distinguish a security patch on an existing branch from a separate decision to adopt a new language release. [1]

The changelog covers several different components, including sessions, PHP-FPM, CGI, SOAP and archive handling. Their prerequisites differ. A single mitigation for one advisory cannot stand in for the entire release, and a component name in the changelog does not establish that a particular application exposes its vulnerable path. [2]

Session storage has more than one boundary

CVE-2026-126714 concerns the built-in files session handler, which is the default handler. An interrupted replacement write can leave a mixture of old and new serialized data. Code execution requires attacker influence over session contents, interruption at a useful point, and suitable deserialization behavior in the application’s available classes. [3]

PHP’s report explains that a file lock does not make that replacement atomic. The fix clears the previous file contents before writing and stops if that clearing operation fails. An interruption can still lose session data; the security change prevents the dangerous old suffix from remaining. [3]

Imagine a hypothetical upload workflow that also stores user-supplied descriptions in its session. Turning off upload-progress tracking would remove one route by which a client influences session data. It would not establish that every other stored string is harmless. The relevant question is what the application actually saves and how the handler replaces it.

CVE-2026-115560 addresses a different problem: session data written with one serialization format and read with another. The full advisory covers shared stores across applications or processes with different fixed configurations. A runtime serializer change is one possible route, rather than a required condition in every case. [4]

The updated default disables session upload progress, but an explicit configuration can enable it again. PHP warns that the fix does not enforce agreement between separate configurations sharing session storage. That makes effective settings and shared storage part of the remaining review, even after the package update. [4]

Persistent connections change the request boundary

CVE-2026-129289 concerns unread request-body bytes on persistent PHP-FPM connections. The reported attack requires backend connection reuse and an application path that opens the input stream without consuming it fully. Under those conditions, the backend can interpret leftover data as a request the front end never authorized. [5]

The report also discusses LSAPI’s request-cleanup behavior, while distinguishing it from the PHP-FPM code-execution mechanism. That distinction matters. A shared cleanup defect is not evidence that two server interfaces have identical exploitation paths or impact. [5]

For an operator, this is a reminder that the web server, PHP interface and application form a combined request path. A familiar PHP configuration file is only one part of that path. The front end’s connection behavior can change the answer without changing the application’s login page.

Keep the release and its evidence specific

Our earlier October article covered a different pair of critical runtime fixes and a then-informational serializer notice. It was explicitly dated to the guidance available on November 4. Today’s security release is a new batch, and its complete advisories provide the current conditions. [6]

The serializer report now explicitly explains the cross-application case. Applications that never switch formats at runtime can still share incompatible session data with another writer. A review limited to searching for a runtime configuration call would miss that possibility. [4]

The four maintained-branch security releases give teams an upgrade path that need not be bundled with the PHP 8.6 feature migration. That separation is useful when a language-version change needs broader compatibility work. It does not reduce the urgency of addressing the applicable security fixes. [1]

The practical evidence should identify the package supplied by the deployment’s vendor, the running web or worker process that uses it, and the application checks completed afterward. A host package, a container image and a scheduled worker can describe different environments. One updated version string cannot speak for all three.

The useful maintenance outcome is concrete: the affected runtime paths are understood, the vendor’s fixed package is in use, and representative workflows still behave as expected. Several advisories can arrive in one release. Their operating conditions deserve separate attention before anyone calls that release verified.

Sources + further reading

Source dates describe the original material. Publication above is the date this Zyel article went live.

  1. PHP release announcementsPHP · Checked Nov 19, 2026
  2. PHP 8.3.37 security changesPHP · Checked Nov 19, 2026
  3. Partially overwritten session files advisoryPHP · Checked Nov 19, 2026
  4. Session serializer mismatch advisoryPHP · Checked Nov 19, 2026
  5. PHP-FPM request-smuggling advisoryPHP · Checked Nov 19, 2026
  6. October PHP security contextZyel · Checked Nov 19, 2026

Reader discussion

What would you ask next?

Questions, useful corrections and thoughtful disagreement are welcome. Comments are reviewed before they appear.

No reader comments yet.

10–2,000 characters. Plain text. Leave out passwords, private project data and personal contact details. A blank display name appears as Anonymous.

Complete the CAPTCHA before sending. Verification runs on your device.