November 19, 2026

PHP Ships Fixes for 7 Critical Flaws: Which Servers First

At 9 a.m. Eastern on November 19, 2026, PHP released fixes for all four supported branches: PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 (PHP news). At the same time, 17 security advisories went up on GitHub (php-src security advisories). Seven are rated CRITICAL, all at 9.2 on CVSS v4.0. Four are HIGH and six are MEDIUM. This is the state of things as of 9 a.m. Eastern (11 p.m. in Japan) on November 19.

Supported branches only

The advance notice said the issues affect “all supported PHP versions” (PHP news, November 18 notice). Some coverage shortened that to “every version of PHP,” but fixes exist only for 8.2, 8.3, 8.4 and 8.5. PHP 8.1 reached end of life on December 31, 2025, and gets nothing this time (PHP end-of-life branches). PHP 8.2 follows on December 31, 2026 (supported PHP versions).

Unsupported versions are not out of the picture. One of the critical session bugs (CVE-2026-115560) comes from a feature added in PHP 5.4.0, and the advisory says older unsupported releases may also be affected (GHSA-658j-r8rw-q6mx). The PHP-FPM flaw CVE-2026-129289 traces back to behavior introduced in PHP 5.6.0 (GHSA-qc49-hpvq-g2w6). A site still on 8.1 or older may have the hole and will never get the patch.

Defaults are not a shield

The advance notice said the critical issues “require either non-default configuration or uncommon setups” (November 18 notice). Read the advisories one by one, though, and at least three of them reach installations that never touched their configuration.

The first is the magic-method flaw in PHP 8.5 (CVE-2026-129474). According to the advisory, a single crafted request, without logging in, can run arbitrary code with the PHP worker’s privileges. It needs fatal_error_backtraces=1 and zend.exception_ignore_args=0. The first is PHP 8.5’s default. For the second, PHP’s built-in default is also 0. Only the production config file, php.ini-production, sets it to 1 and closes this path (GHSA-8mjj-2r7p-4hg2). The official Docker images ship both the production and development files, but you have to copy one into place as php.ini yourself. If you never did, PHP runs on its built-in defaults (official PHP Docker image documentation). The advisory points to Laravel facades and Magento’s guest shipping estimate as examples of real code paths that make this kind of call. It also says exploitation of a complete Laravel or Magento installation has not been demonstrated.

The second is request smuggling in PHP-FPM (CVE-2026-129289). With PHP itself on default settings, one unauthenticated request can run attacker-controlled PHP code. It needs no memory corruption, no memory addresses and no race. The conditions are a front-end web server that reuses its connections to PHP-FPM, and an application path that opens php://input without reading it to the end. That means nginx with fastcgi_keep_conn on, or Apache mod_proxy_fcgi with enablereuse=on. The advisory notes that frameworks which create an input stream before routing or authentication can hit this even on endpoints that ignore the body (GHSA-qc49-hpvq-g2w6). Standard nginx and Apache setups close the connection after every request and are not affected. The servers at risk are the ones that turned on connection reuse for speed. Of everything in this release, we think this is the one most likely to work when someone actually tries it.

The third is the session-file flaw (CVE-2026-126714). It affects the files handler, which is PHP’s default. If a session write is interrupted, the file can end up with the start of the new data and the tail of the old, and the next read can rebuild objects the attacker planted (GHSA-fm2m-fjf5-v3cp). Getting to code execution needs attacker influence over session contents, an interruption at the right point, and a usable gadget chain in the application. The bar is high, but you are in scope without changing a single setting.

Two fixes PHP2Shell missed

The October 21 fix for CVE-2026-109619, one half of “PHP2Shell,” was incomplete. Two of today’s critical advisories finish the job.

CVE-2026-129481 leaves a pointer to the script filename behind when session shutdown is interrupted, and the next request on the same worker touches freed memory. The advisory calls it an incomplete fix for CVE-2026-109619 and says it affects 8.3 and later. Turning off session upload progress, one of October’s mitigations, does not help here (GHSA-g3vh-838c-65v7).

CVE-2026-129182 is the fatal-error backtrace use-after-free that 8.5.12 was supposed to close, reached by another route. It affects only 8.5 and needs a combination of administrator-side settings (GHSA-2fjv-p558-g82m).

A third issue, which PHP pre-announced on October 23, is now a full advisory. In the session upload progress feature, data written in one session format can be read back in another, and part of it gets rebuilt as objects (CVE-2026-115560, GHSA-658j-r8rw-q6mx). The October notice described it as limited to apps that switch session.serialize_handler at runtime (PHP news, October 23). The full advisory is broader. The same thing happens when separate applications, FPM pools or command-line jobs with different formats share one session store. Command execution was shown with Guzzle and Monolog classes on 8.2.35 through 8.5.12.

This fix changes PHP’s behavior in one way. Session upload progress (session.upload_progress.enabled) is now off by default. An explicit setting in your config still turns it on. If you use the feature, the advisory says every configuration that reads or writes the same sessions must use the same serializer, even after updating.

Last critical, four highs

The remaining critical issue is in the date extension (CVE-2026-129496). If PHP writes a warning to a file-based error log during startup, for a bad setting or a deprecated one, a reference to freed memory is left behind. A crafted request to a fresh worker can then crash it, and with the right conditions run code. Command execution was demonstrated under FPM and Apache mod_php (GHSA-gr4f-wgx5-jpfv). Servers that log warnings at startup are common. Fixing the warning and restarting removes this trigger.

Two of the four high-severity issues matter for operations. One is in PHP-FPM (CVE-2026-129291). Someone who can already run PHP code can take over the privileges of the FPM master process, which is often root. One condition is catch_workers_output, which the official PHP-FPM Docker images turn on. Root was obtained on the official 8.5.12 Docker images on both x86-64 and arm64 (GHSA-jm4m-qfqx-967m). It is not a way in from outside, but after another bug gives an attacker PHP execution, it turns that into control of the whole server.

The other is that a URL written with a capital “S,” such as HTTPS://, makes PHP send the request unencrypted (CVE-2026-128064). Calls to outside APIs through file_get_contents() and similar functions can leak passwords and tokens in plain text. It also happens when a redirect points to an uppercase URL (GHSA-f6gg-rchx-xw8j). The other two highs let a malicious HTTP server burn CPU with its response, and let a modified archive slip past OpenSSL signature checks on Phar files. The six medium issues involve SOAP, DOM, URI handling, php-cgi and the FPM status page (php-src security advisories).

Which servers to patch first

Everything needs the update, but if you have to pick an order, this is ours. First, servers where nginx or Apache reuses connections to PHP-FPM, because once the conditions are met the attack works reliably. Next, PHP 8.5 servers that are not using the production config. Official Docker images run in production without added config are the likely case. After that, any site that uses sessions.

Even if you don’t remember enabling fastcgi_keep_conn or enablereuse, search your server config for them. They often go in during performance tuning and get forgotten. php -v on the server shows the PHP version, but the PHP serving web requests can differ from the command-line one, so check the FPM or Apache module version too.

If PHP comes from your Linux distribution’s packages, the fix may arrive without a version bump. Look for these CVE numbers in your distribution’s security notices. On shared hosting, the host updates PHP for you, so watch the host’s announcements.

If you cannot update today

Each advisory lists a temporary workaround. None of them fixes the underlying bug. They buy time until the update.

On PHP 8.5, set zend.exception_ignore_args=1 in the configuration that FPM or Apache actually reads, then restart the workers. Setting fatal_error_backtraces=0 also blocks CVE-2026-129474, and closes CVE-2026-129182 as well. The advisories warn that changing only the CLI configuration is not enough, and that display_errors=0 does not help (GHSA-8mjj-2r7p-4hg2, GHSA-2fjv-p558-g82m).

; Stopgap for PHP 8.5 (in the FPM pool or the web php.ini)
zend.exception_ignore_args = 1
fatal_error_backtraces = 0

For PHP-FPM connection reuse, remove fastcgi_keep_conn in nginx or enablereuse in Apache (GHSA-qc49-hpvq-g2w6). If you don’t use session upload progress, set session.upload_progress.enabled=0 in the server-side configuration. Calling ini_set() from the application is too late (GHSA-658j-r8rw-q6mx). Turn off PHP-FPM’s catch_workers_output if you don’t need it (GHSA-jm4m-qfqx-967m). For startup warnings, fix the setting that causes them and restart the master process along with the workers (GHSA-gr4f-wgx5-jpfv).

On 8.3 and later with sessions, there is no single setting that closes CVE-2026-129481. The advisory suggests pm.max_requests=1 in FPM so each worker is replaced after one request, at a significant performance cost (GHSA-g3vh-838c-65v7). Updating sooner is the more realistic choice.

In the US and Japan

PHP’s 17 advisories don’t mention exploitation in the wild. After PHP2Shell in October, a successful attack on a honeypot was reported about a week after the fix shipped. We covered that timeline in where the PHP2Shell coverage diverged from the primary sources. Assume it won’t take long this time either for someone to work out an attack from the patch diff.

In Japan, IPA published a notice on November 19, ahead of the release, asking organizations to inventory their PHP systems and prepare to patch immediately. It said IPA had not confirmed any attacks at that point (IPA, in Japanese). As of 11 p.m. Japan time, JPCERT/CC had not issued an alert.

If your servers still lack the October fix, this update covers both. October’s details are in our engineer’s guide to PHP2Shell. For who should run updates and how, see keeping software up to date: finding, getting and deploying new versions. If you suspect a break-in, see what to do in the first 24 hours after you notice a compromise.

Free security consultations

We are currently taking free consultations on security. Questions like "Is our site safe?" or "Where should we start checking?" are welcome.

Super Sonic Design accepts consultations on website creation, application design, etc. Please feel free to contact us.
inquiring
他の最新記事
カテゴリー