The PHP project had two releases on 19 November 2026. The first was PHP 8.6.0, the next major-feature version of the language. The second was a set of security updates for every supported branch: 8.5.13, 8.4.28, 8.3.37 and 8.2.36. According to The Hacker News, the updates fix seven flaws rated 9.2 on the CVSS severity scale, plus an eighth rated 8.8 that allows local privilege escalation.

The headline numbers look bad, but the details are more reassuring. The Hacker News says the maintainers' advance notice described exploitation under specific conditions, including non-default configurations or uncommon setups, such as a certain session configuration, a certain reverse-proxy setup, or a particular code path. None of the sources we reviewed report exploitation in the wild. These are critical-rated bugs in core runtime code, so this is a patch cycle to finish soon, not one to leave for the quarterly window.

The session serializer bug: CVE-2026-115560

The most widely applicable flaw is CVE-2026-115560, listed in the official PHP 8 ChangeLog as "Session serializer mismatch can lead to remote code execution" (advisory GHSA-658j-r8rw-q6mx). It is fixed in all five releases: 8.2.36, 8.3.37, 8.4.28, 8.5.13 and 8.6.0.

Some background helps here. PHP sessions store a user's state between requests. Before that state is written to disk or a session store, it is serialized, meaning converted into a byte string, and it is unserialized when read back. PHP supports several serialization formats, and the session.serialize_handler setting chooses which one is used. Unserializing untrusted data is a well-known risk, because a carefully crafted string can rebuild arbitrary PHP objects, and in the right codebase that can end in code execution.

The NVD record, sourced from [email protected], describes the problem this way. When session upload progress is enabled, PHP can write attacker-controlled data into a session key using the php_binary or php_serialize serializer. If the same session is later read with the plain php serializer, bytes from that key can reach the unserializer. That happens when the handler is changed at runtime, or when two applications share a session store but are configured differently. The NVD entry says a remote attacker who can submit a multipart upload can then inject objects, which may lead to code execution when the reading application contains a suitable gadget chain, or to session corruption or denial of service.

This explains why the bug is critical but not universal. It needs upload progress turned on and a mismatch between the serializer that writes a session and the one that reads it. Shared hosting, legacy applications sitting beside newer ones, and sites that set the handler in code instead of in php.ini are the places to check first.

The rest of the critical list

The Hacker News lists the other 9.2-rated bugs as follows:

  • CVE-2026-126714 is a time-of-check/time-of-use (TOCTOU) race in session writing, meaning the state PHP checked has changed by the time it acts on it. The changelog lists it as "Partially overwritten session files can lead to remote code execution". Exploiting it requires an attacker who can influence session data, an interruption at a useful point in the write, and a usable deserialization "gadget chain", which is a set of existing classes in the application that can be chained into harmful behaviour. Depthfirst, which codenamed the flaw "phpAfterShell", calls it critical.
  • CVE-2026-129289 is an HTTP request-interpretation flaw that only affects deployments where the front-end web server keeps persistent connections to the PHP backend. Examples given are nginx with fastcgi_keep_conn on, Apache mod_proxy_fcgi with enablereuse=on, HAProxy's FastCGI support, and LSAPI. It also requires an application code path that opens php://input (the raw request body) without reading all of it. The changelog describes it as PHP-FPM request smuggling through an unread HTTP request body. When one connection carries many requests, leftover bytes are a familiar way for one request to bleed into the next.
  • CVE-2026-129182 is a use-after-free fixed in 8.5.13 and 8.6.0. A use-after-free happens when code keeps using memory after it has been released. These bugs are a classic route to crashes and, in the worst cases, code execution. The changelog ties it to the last_fatal_error_backtrace global being repopulated after shutdown.
  • CVE-2026-129474 is a use-after-free that could result in remote code execution on PHP 8.5 and later, according to The Hacker News. Exploitation depends on the application and needs a reachable magic method call and a fatal error at the relevant point. It is fixed in 8.5.13 and 8.6.0.
  • CVE-2026-129481 is described in the changelog as "Use-after-free after interrupted session shutdown" (GHSA-g3vh-838c-65v7). The Hacker News lists it as fixed in 8.3.37, 8.4.28, 8.5.13 and 8.6.0.
  • CVE-2026-129496 is a use-after-free that The Hacker News says can allow an unauthenticated remote attacker to crash PHP workers or execute arbitrary code with their privileges. The changelog describes it as a timezone cache use-after-free. The sources we read do not give its trigger conditions, so treat it as a priority for internet-facing servers.

The eighth fix is CVE-2026-129291, an 8.8-rated PHP-FPM epoll use-after-free that can lead to local privilege escalation. "Local" means the attacker already needs some foothold on the machine: The Hacker News says exploitation requires local code execution in an FPM worker, a pool with catch_workers_output enabled and the epoll event backend. That still matters on shared hosting or any multi-tenant server where several users' PHP code runs on the same host. The changelog also lists SOAP fixes for an information disclosure and a use-after-free.

PHP 8.6 itself: new features and changed session defaults

Teams thinking about moving straight to 8.6 should read Help Net Security's rundown first. The new version adds partial function application, a Time\Duration class, a polling API for event loops and a clamp() function.

The security-relevant changes are in the defaults. PHP 8.6 turns on session.use_strict_mode and session.cookie_httponly by default and sets session.cookie_samesite to Lax. Strict mode rejects session IDs the server did not create, which closes off session fixation. HttpOnly keeps session cookies out of reach of JavaScript. SameSite=Lax stops browsers sending the cookie on most cross-site requests. Each is a sensible hardening step, and each can break login flows, single sign-on redirects, or embedded apps that relied on the old behaviour. Functions such as fclose(), file_put_contents() and copy() now return false when a flush or close fails, which can catch out code that never checked those return values. Help Net Security's advice is to test login flows before upgrading.

The practical takeaway is that you do not have to jump to 8.6 to get the security fixes. Every supported branch got its own patched release.

What It Means for Defenders

Who is affected: All supported PHP branches, 8.2 through 8.5. The serializer flaw, CVE-2026-115560, is fixed on every branch. Some bugs are limited to newer code: CVE-2026-129474 affects 8.5 and later, and CVE-2026-129182 is listed as fixed in 8.5.13 and 8.6.0.

What to patch: Move to the fixed release for your branch:

  • PHP 8.2 → 8.2.36
  • PHP 8.3 → 8.3.37
  • PHP 8.4 → 8.4.28
  • PHP 8.5 → 8.5.13
  • New deployments, or teams ready for the feature upgrade → 8.6.0 (test the new session defaults first)

If you get PHP from a Linux distribution, a container base image or a hosting control panel, check that the package you install actually includes these fixes rather than relying on the upstream version number alone. Restart PHP-FPM, LSAPI or Apache workers after updating, because a patched binary on disk does nothing until the old processes are gone.

What to check while you wait:

  • Session serializer consistency. Confirm that session.serialize_handler is the same everywhere a session is written or read, including any applications that share a session store, and that no code changes it at runtime. If you don't use session upload progress, check whether it is enabled anyway; The Hacker News advises turning it off if immediate patching is not possible.
  • Persistent FastCGI connections. Find out whether your nginx, Apache, HAProxy or LSAPI front end reuses backend connections. If it does, these servers should be near the top of your patch list because of CVE-2026-129289.
  • Shared hosts. Multi-tenant servers face the local privilege escalation (CVE-2026-129291) as well as the remote bugs. Patch them early.
  • Inventory. PHP often turns up in places nobody tracks, such as vendor appliances, old WordPress installs and internal tools. CMMC-bound contractors should record the update under their flaw-remediation process and check that it reached every in-scope system.

No workaround replaces the update. The configuration checks above reduce exposure until patching is done, and they are worth keeping afterwards.

Sources