PHP Security Update – November 19, 2026: MioriticHost Servers Already Patched
The short version: what happened and where things stand
On November 19, 2026, the PHP project published versions 8.5.13, 8.4.28, 8.3.37, and 8.2.36, fixing 17 security issues, 7 of which are classified as critical. The nightly automatic update installed the packages on MioriticHost servers on November 20, 2026 at 04:11 Romania time, the night right after the release, with no manual intervention. On November 20 we ran a manual check: installed versions matched the repaired package list published by CloudLinux, no PHP updates were pending, and every PHP process running at that point had been started after the update — no process was still using an old binary from memory. Shared hosting customers do not need to take any action; the PHP version selected in cPanel remains unchanged.
What the November 19 release fixes and its connection to PHP2Shell
- CVE-2026-115560 — remote code execution via the session upload progress feature (requires session.upload_progress.enabled to be on). This issue was disclosed in October 2026 with no fix available at the time; it is patched now for the first time.
- CVE-2026-126714 — code execution through partially written session files.
- CVE-2026-129481 — use-after-free memory error on interrupted session shutdown, affecting PHP 8.3–8.5. This is a follow-up to the October PHP2Shell fix (CVE-2026-109618 and CVE-2026-109619), which turned out to be incomplete.
- CVE-2026-129496 — memory corruption in the timezone cache.
- CVE-2026-129474 and CVE-2026-129182 — memory errors related to fatal error backtraces, specific to PHP 8.5.
- CVE-2026-129289 — request smuggling via PHP-FPM (CVSS score 9.2), requiring the front-end web server to reuse connections to PHP-FPM.
- CVE-2026-129291 — a serious PHP-FPM issue that requires catch_workers_output to be enabled.
- According to CloudLinux, as of November 19 none of the 17 issues appeared in the CISA catalog of actively exploited vulnerabilities. Also this week, critical vulnerabilities in nginx were patched (NGINX2Root, November 18, 2026) — we are covering those in a separate blog post.
Why some of these issues could not have affected us anyway
MioriticHost servers run CloudLinux with cPanel. CloudLinux published repaired packages for every PHP branch from 5.5 to 8.5. For versions no longer maintained by the PHP project (8.1 and older), CloudLinux backports the fixes: the version number stays the same, but the installed package includes the patch.
Some of these issues did not have the conditions they need on our servers even before the update. First: session upload progress has been disabled across all PHP versions on our servers since October 21, 2026, as a hardening measure taken during the PHP2Shell response and kept in place deliberately. We confirmed it remained disabled and that no site re-enables it. Also since October, on PHP 8.5 we have had fatal_error_backtraces disabled, which is the prerequisite for CVE-2026-129474 and CVE-2026-129182. Second: the conditions required by the PHP-FPM issues are not met in our setup. Sites run PHP via LSAPI (CloudLinux mod_lsapi), not per-site PHP-FPM pools; our web servers do not reuse connections to PHP-FPM, and catch_workers_output is not enabled. CloudLinux notes that on LSAPI the bug behind CVE-2026-129289 could disrupt subsequent requests, with no code execution reported; the installed packages include the fix for that case as well.
What customers should do
Shared hosting: nothing. Your sites do not need any changes, and the PHP version you selected in cPanel stays as it is.
Sites still running PHP 7.x or 8.0–8.1: you are protected against these issues by CloudLinux backports. However, these branches no longer receive updates from the PHP project itself. It is worth planning a move to PHP 8.3 or 8.4 via MultiPHP Manager in cPanel, after testing your site for compatibility. MioriticHost support can help with that process.
VPS customers: you manage your own environment. If PHP is installed, update to 8.5.13, 8.4.28, 8.3.37, or 8.2.36 (or to your distribution's patched package) and restart PHP-FPM or your web server afterwards — an updated package has no effect if the old process is still running in memory. Check your current version with php -v. As a temporary measure before updating, if you do not use session upload progress, set session.upload_progress.enabled = 0 in php.ini.
Closing notes
MioriticHost servers have been running the patched versions since the morning of November 20, and the configuration hardening applied in October had already reduced the attack surface before the patches were even available. If you have questions or need help migrating to a newer PHP version, open a support ticket from the client area at mioritichost.com.
Category: Hosting






