Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
PHP will publish security releases for every supported branch on Thursday, Nov 19 between 6:00 and 6:30 AM PST (14:00–14:30 UTC), and rates the most severe issue critical. If your project runs PHP on a VM or server that you manage yourself, please update PHP as soon as your package source has the fix, and restart PHP-FPM or your web server afterwards.
Who needs to act:
- Projects that manage their own OpenStack VMs or colocated servers and run PHP (for example WordPress, Drupal, MediaWiki, Nextcloud, phpBB or DokuWiki).
- Hosts that OSL manages for you: we will patch these ourselves as soon as fixed packages are available, and contact you directly if your site needs changes.
What PHP has said:
The releases fix security vulnerabilities in all supported versions (8.2, 8.3, 8.4 and 8.5). PHP says the critical issues need either a non-default configuration or an uncommon setup, and it will publish the technical details and fixed version numbers with the releases. PHP 8.1 and older are end-of-life and get no new releases.
One issue is already known: CVE-2026-115560, which PHP disclosed on October 23 as an unlikely remote code execution vector in session upload progress. It only affects applications that set session.serialize_handler to php_binary or php_serialize and then switch it to php at runtime before starting the session. PHP advised setting session.upload_progress.enabled=0 until its next regular bugfix release, which is this one, and said it will publish the full advisory with that release. Put the setting in php.ini or your PHP-FPM pool configuration (not ini_set() or a .user.ini file) and restart PHP-FPM or the web server. If you set it for October's release, keep it.
If you have not updated PHP since October 21, please do so now: the two flaws fixed that day (CVE-2026-109618 and CVE-2026-109619, known as PHP2Shell) are being actively exploited and are on CISA's Known Exploited Vulnerabilities list.
What to do:
- PHP 8.2 or newer: install your vendor's update when it appears (Remi, Ubuntu or Debian security updates, or a rebuilt Docker image), then restart PHP-FPM or the web server.
- PHP 8.1 or older: plan a move to PHP 8.3 or 8.4 now. PHP 8.2's security support also ends on Dec 31, 2026. Remi's repository has backported security fixes to 7.4, 8.0 and 8.1 on a best-effort basis, most recently for October's critical PHP release, which can serve as a stopgap.
- An end-of-life OS (CentOS 7, Ubuntu 20.04 without Ubuntu Pro, Debian 11): no free fix is expected, so please plan an OS upgrade.
We will post an update once the details are out. If you are unsure whether you are affected or need help, email support@osuosl.org.
PHP published the fixes at about 6:05 AM PST (14:05 UTC): 8.2.36, 8.3.37, 8.4.28 and 8.5.13. The releases fix 17 security issues, seven of them rated critical. If you run PHP on a VM or server you manage, update to the fixed release for your branch as soon as your package source has it, then restart PHP-FPM or your web server.
The issues most likely to matter:
- CVE-2026-129289 (critical, PHP-FPM 8.2 to 8.5): if your web server reuses its FastCGI connections to PHP-FPM (nginx fastcgi_keep_conn on, or Apache enablereuse=on) and the application leaves part of a request body unread, a single crafted request can run attacker-controlled PHP code. Standard nginx and Apache setups, which close the connection after each request, are not affected. Until you update, turn connection reuse off.
- CVE-2026-126714 (critical, PHP 8.2 to 8.5): an interrupted write to a file-based session, PHP's default session storage, can leave attacker-controlled objects in the session. In an application with a suitable gadget chain this can lead to remote code execution. Keeping session.upload_progress.enabled=0 removes one way in, but only the update fixes it.
- CVE-2026-115560 (critical, PHP 8.2 to 8.5): the session upload progress issue PHP disclosed on October 23. The update turns session upload progress off by default. Keep session.upload_progress.enabled=0 in php.ini or your PHP-FPM pool settings. If you need the feature, every application and process that shares a session store must use the same session.serialize_handler, even after the update.
- CVE-2026-129496 (critical, PHP 8.2 to 8.5): a remote request can corrupt memory, and potentially run code, when PHP writes a startup warning to an error log file. Until you update, fix any warnings or deprecation notices PHP prints at startup, or send PHP's errors to syslog, then restart PHP.
- CVE-2026-129481 (critical, PHP 8.3 to 8.5): an incomplete fix for October's CVE-2026-109619 in session shutdown. Turning off session upload progress does not help with this one.
- CVE-2026-129182 and CVE-2026-129474 (critical): PHP 8.5 only.
- CVE-2026-129291 (high): with PHP-FPM's catch_workers_output enabled, PHP code running in a worker can gain the privileges of the FPM master, which commonly runs as root. The setting is off by default but on in the official PHP-FPM Docker images. Set catch_workers_output = no until you update.
Advisories: https://github.com/php/php-src/security/advisories
What to do:
- PHP 8.2 to 8.5: install your vendor's update (Remi, Ubuntu or Debian security updates, or a rebuilt Docker image), then restart PHP-FPM or the web server. Remi's fixed packages are out for AlmaLinux and RHEL 8, 9 and 10. Remi's mirrors are still catching up, so if dnf finds nothing new, try again later.
- PHP 8.1 and older: PHP has no release for these. Remi has published 7.4.33-32, 8.0.30-22 and 8.1.34-7 with backported fixes for today's issues, for EL8, EL9 and EL10. These versions are still end-of-life, so please plan a move to PHP 8.3 or 8.4.
What we are doing on the hosts OSL manages for you:
- Session upload progress stays turned off on every PHP host we manage, and our web server configuration for them does not reuse FastCGI connections.
- Today: we are installing Remi's fixed packages and restarting PHP.
- Hosts still on PHP 7.4 get Remi's backported fix, 7.4.33-32, at the same time. We will contact you directly if your site needs changes.
If you need help, email support@osuosl.org.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with