Advisory checked: 19 November 2026. If you are searching for a practical PHP vulnerability fix following the 18 November 2026 PHP critical security release announcement, this step-by-step guide walks through how to audit your PHP runtime, mitigate CVE-2026-115560, apply the November 2026 security updates across Ubuntu, Debian, RHEL and Docker, and verify production safety for Laravel, Symfony, WordPress and custom PHP sites.
What does the November 2026 PHP critical security release cover?
The PHP Group scheduled its regular security window for 19 November 2026 (14:00–14:30 UTC) across all supported PHP branches (8.2, 8.3, 8.4 and 8.5), addressing flaws rated up to CRITICAL (primarily affecting non-default configurations or uncommon setups) alongside remediation for the session upload progress vulnerability (CVE-2026-115560).
| PHP branch | Status | Recommended action |
|---|---|---|
| 8.5 | Active support | Apply the 19 Nov 2026 security patch release as soon as vendor packages publish |
| 8.4 | Active support | Apply the 19 Nov 2026 security patch release and restart workers |
| 8.3 | Security fixes | Apply vendor security update and check session upload progress config |
| 8.2 | Security fixes | Apply vendor security update and plan upgrade to PHP 8.4/8.5 |
| 8.1 and earlier | End of life upstream | Verify OS/vendor LTS backports or schedule an urgent supported-version upgrade |
How to fix CVE-2026-115560 session upload progress vulnerability in php.ini
Before and during package rollout, inspect your effective startup php.ini files (separate files often apply to CLI, Apache mod_php and PHP-FPM). If your application does not depend on PHP session upload progress tracking, disable it at startup and verify your session serializer:
; Check active startup php.ini paths and current settings
php --ini
php -i | grep -E "session\.upload_progress\.enabled|session\.serialize_handler"
; Apply in startup php.ini for PHP-FPM and Apache (do not rely on ini_set)
session.upload_progress.enabled = 0
session.serialize_handler = php
An application-level ini_set() call runs too late because request upload parsing happens before PHP executes your script.
Step-by-step PHP vulnerability fix commands (Ubuntu, Debian, RHEL & Docker)
- Step 1 — Inventory active PHP runtimes: Check every environment (web server, queue workers, cron jobs and containers) so an unpatched secondary binary is not left running:
php -v systemctl list-units --type=service | grep -E "php|apache2|nginx" - Step 2 — Back up configuration and test in staging: Take a snapshot or backup of
/etc/php/and verify dependencies (composer check-platform-reqs) before updating production. - Step 3 — Apply vendor PHP security packages:
# Ubuntu / Debian (including Ondrej PPA or official Ubuntu security repo) sudo apt update sudo apt install --only-upgrade 'php*' # RHEL / AlmaLinux / Rocky Linux sudo dnf upgrade 'php*' # Docker / Containerised Laravel & Symfony apps docker compose build --pull --no-cache docker compose up -d - Step 4 — Restart PHP-FPM, Apache/Nginx and queue workers: Updating packages on disk does not replace PHP binaries already loaded in memory:
# Restart PHP-FPM (adjust version, e.g. php8.3-fpm / php8.4-fpm / php8.5-fpm) and web server sudo systemctl restart php8.5-fpm nginx # Or for Apache mod_php: sudo systemctl restart apache2 # Restart Laravel / Symfony background queue workers if used: php artisan queue:restart
How to verify your PHP vulnerability fix in production
- Confirm package build revision: On Ubuntu/Debian run
dpkg -l | grep php(orrpm -qa | grep phpon RHEL) and cross-check the package version against your Linux vendor security advisory. - Confirm web & CLI runtime parity: Verify
php -vmatches the active PHP-FPM pool or Apache module, and checksudo systemctl status php*-fpmshows a fresh start timestamp. Never leave a publicphpinfo()page exposed. - Run functional & log checks: Test logins, file uploads, checkout, API endpoints and scheduled jobs, then inspect
/var/log/apache2/error.logor/var/log/php*-fpm.logfor warnings.
Need emergency or managed PHP upgrade support? NSDIT is ready to help
If your business needs immediate assistance auditing configurations, applying the November 2026 PHP security patches without downtime, or upgrading legacy PHP 7.x/8.1 applications to supported PHP 8.3–8.5 builds, NSDIT's engineering team is ready to deploy support for companies across the UK, Europe and the USA.
Explore our PHP development and maintenance services, Laravel development team and Symfony engineering services, or review our PHP2Shell remediation guide and legacy PHP modernisation checklist. Request immediate PHP security & upgrade support with your PHP version and hosting environment (please do not share passwords or private keys).