Site icon GetPageSpeed

PHP November 2026 Security Release: Patched PHP for CentOS 7, CentOS 6, Amazon Linux 2, Ubuntu and Debian

PHP November 2026 Security Release: Patched PHP for CentOS 7, CentOS 6, Amazon Linux 2, Ubuntu and Debian

The PHP security release of November 19, 2026 fixes seven critical bugs (CVSS v4.0 9.2) and four more rated high. Upstream shipped the fixes only in PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13. Servers on older PHP, or on distributions that stopped getting free updates, received nothing. GetPageSpeed ships patched, drop-in compatible PHP for CentOS 7, CentOS 6, Amazon Linux 2, Remi’s collections on EL8 and EL9, Ubuntu 18.04 and 20.04, and Debian 10.

CVE-2026-129496  timezone cache use-after-free, RCE       (GHSA-gr4f-wgx5-jpfv)  CVSS v4.0 9.2
CVE-2026-126714  partially overwritten session files, RCE (GHSA-fm2m-fjf5-v3cp)  CVSS v4.0 9.2
CVE-2026-115560  session serializer mismatch, RCE         (GHSA-658j-r8rw-q6mx)  CVSS v4.0 9.2
CVE-2026-129289  PHP-FPM request smuggling                (GHSA-qc49-hpvq-g2w6)  CVSS v4.0 9.2
CVE-2026-129291  PHP-FPM epoll use-after-free, LPE        (GHSA-jm4m-qfqx-967m)  CVSS v4.0 8.8
Fixed upstream:  8.5.13, 8.4.28, 8.3.37, 8.2.36 only
GetPageSpeed:    CentOS 7 (PHP 5.4-8.5), CentOS 6 (5.3, 7.0, 7.1), Amazon Linux 2 (7.2, 7.4),
                 EL8/EL9 Remi collections (5.6, 7.0, 7.1), Ubuntu 18.04 (7.2),
                 Ubuntu 20.04 (7.4-8.4), Debian 10 (7.3)

Which servers need GetPageSpeed builds

Platform PHP Fix
CentOS 7 / RHEL 7 5.4 to 8.5 GetPageSpeed (below)
CentOS 6 5.3, 7.0, 7.1 GetPageSpeed (below)
Amazon Linux 2 (x86_64 and Graviton) 7.2, 7.4 GetPageSpeed (below)
AlmaLinux, Rocky, RHEL 8 and 9 Remi php56, php70, php71 collections GetPageSpeed (below)
Ubuntu 18.04 7.2 GetPageSpeed (below)
Ubuntu 20.04 7.4, 8.0, 8.1, 8.2, 8.3, 8.4 GetPageSpeed (below)
Debian 10 7.3 GetPageSpeed (below)
Debian 12 and 13 stock PHP Debian security update (8.2.36-1~deb12u1, 8.4.28-1~deb13u1)

Distribution status as of November 19, 2026, 18:30 UTC: Debian had shipped fixes for Debian 12 and 13; the Ubuntu CVE tracker listed every Ubuntu release as “needs triage”; Red Hat had not yet published an entry. Check those trackers for later changes.

Free to install; commercial production use requires a subscription. Without one, a small license notice appears on HTML pages after 30 days.

CentOS 7 and RHEL 7

Check which PHP package shape your server runs:

rpm -qa 'php*-common' --qf '%{NAME}-%{VERSION}-%{RELEASE}\n'

Base-name packages (php-common-7.4.33-15.el7.remi, from remi-php74 and friends) upgrade from the channel for your version:

yum -y install https://extras.getpagespeed.com/release-latest.rpm
yum --enablerepo=getpagespeed-extras-php74 upgrade 'php-*'
systemctl restart php-fpm

Replace php74 with your version, from php54 to php85. Enable the channel only for the transaction, as shown.

Stock CentOS 7 PHP 5.4 (php-common-5.4.16-48.el7) upgrades from the main repository to the patched 5.4.45 build, so a plain update is enough once the GetPageSpeed repository is installed:

yum -y install https://extras.getpagespeed.com/release-latest.rpm
yum upgrade php 'php-*'
systemctl restart httpd

Software collections (php74-php-common-…, from remi-safe) come from the always-enabled main repository:

yum -y install https://extras.getpagespeed.com/release-latest.rpm
yum upgrade 'php74-php*'
systemctl restart php74-php-fpm
PHP Base-name channel Patched build (both shapes) What it carries
5.4 getpagespeed-extras-php54 5.4.45-29.el7 9 fixes ported to 5.4
5.6 getpagespeed-extras-php56 5.6.40-54.el7 10 fixes ported to 5.6
7.0 getpagespeed-extras-php70 7.0.33-56.el7 11 fixes ported to 7.0
7.1 getpagespeed-extras-php71 7.1.33-46.el7 11 fixes ported to 7.1
7.2 getpagespeed-extras-php72 7.2.34-41.el7 11 fixes ported to 7.2
7.3 getpagespeed-extras-php73 7.3.33-35.el7 11 fixes ported to 7.3
7.4 getpagespeed-extras-php74 7.4.33-45.el7 12 fixes ported to 7.4
8.0 getpagespeed-extras-php80 8.0.30-32.el7 12 fixes ported to 8.0
8.1 getpagespeed-extras-php81 8.1.34-16.el7 12 fixes ported to 8.1
8.2 getpagespeed-extras-php82 8.2.36-1.el7 upstream 8.2.36
8.3 getpagespeed-extras-php83 8.3.37-1.el7 upstream 8.3.37
8.4 getpagespeed-extras-php84 8.4.28-2.el7 upstream 8.4.28
8.5 getpagespeed-extras-php85 8.5.13-2.el7 upstream 8.5.13

Remi’s EL7 builds froze at 8.2.20 and 8.3.8 and never had 8.4 or 8.5, so yum update against Remi delivers nothing.

CentOS 6

If yum can’t reach any repository, point it at the vault first. Stock PHP 5.3 (php-common-5.3.3-50.el6_10 and older) updates from the main repository:

yum -y install https://extras.getpagespeed.com/release-latest.rpm
yum update 'php*'
service httpd restart   # or: service php-fpm restart

Remi PHP 7.0 or 7.1 updates from the channel for your version:

yum -y install https://extras.getpagespeed.com/release-latest.rpm
yum --enablerepo=getpagespeed-extras-php71 update 'php*' libicu-last libwebp
service php-fpm restart   # or: service httpd restart

Replace php71 with php70 if that is your version. Patched builds: 5.3.3-57.el6, 7.0.33-56.el6 and 7.1.33-46.el6, x86_64.

Amazon Linux 2

PHP 7.2 from amazon-linux-extras or PHP 7.4 from Remi or Amazon’s php7.4 topic upgrades in place, on x86_64 and Graviton alike:

sudo yum -y install https://extras.getpagespeed.com/release-latest.rpm
sudo yum -y update getpagespeed-extras-release
sudo amazon-linux-extras install -y epel
sudo yum --enablerepo=getpagespeed-extras-php74 upgrade 'php-*'
sudo systemctl restart php-fpm

Replace php74 with php72 for PHP 7.2. The software collections (php72-php-*, php74-php-*) come from the main repository: sudo yum upgrade 'php74-php*'. Patched builds: 7.2.34-41.amzn2 and 7.4.33-45.amzn2, both shapes.

Remi collections on EL8 and EL9

Remi’s php56, php70 and php71 collections on AlmaLinux, Rocky Linux and RHEL 8 (and php56 on EL9) are replaced in place by GetPageSpeed builds with the same package names:

dnf -y install https://extras.getpagespeed.com/release-latest.rpm
dnf update 'php56-php*'
systemctl restart php56-php-fpm

Replace php56 with php70 or php71 on EL8. Patched builds: 5.6.40-54.el8, 5.6.40-54.el9, 7.0.33-56.el8 and 7.1.33-46.el8, x86_64.

Ubuntu and Debian

Add the GetPageSpeed repository, then upgrade the PHP branch you already run:

wget https://extras.getpagespeed.com/release-latest.deb
sudo apt install ./release-latest.deb
sudo apt update
sudo apt upgrade 'php7.4-*'
sudo systemctl restart php7.4-fpm

Replace 7.4 with your branch: 8.0 to 8.4 on Ubuntu 20.04, 7.2 on Ubuntu 18.04, 7.3 on Debian 10. Running Apache mod_php? Restart apache2 instead.

The upstream version in these packages does not change: the fixes are carried as patches. Compare the package revision instead, with dpkg -l 'php*-cli'. A version ending in +stable.5 or later is patched, for example 1:7.4.33-31+gps1+ubuntu2004+stable.5 or 7.3.33-35+gps1+deb10+stable.5.

What the November 2026 release fixes

CVE-2026-129496, timezone cache use-after-free. When PHP logs to a file (error_log), it timestamps each line in the configured timezone. A diagnostic during module startup, such as an invalid date.timezone or a deprecated session setting, caches that timezone in memory that is freed when startup ends. Fresh FPM or mod_php workers then use the freed cache on the first request that triggers an early warning, such as the max_input_vars warning, and that memory may hold the attacker’s request data. The PHP team demonstrated code execution through both PHP-FPM and Apache mod_php.

CVE-2026-126714, partially overwritten session files. PHP’s default files session handler wrote new session data over the old file without clearing it first. An interrupted write left a prefix of the new session followed by the tail of the old one, and carefully arranged data turns that mix into attacker-controlled serialized objects on the next session_start(). With a suitable gadget chain in the application, that is code execution.

CVE-2026-115560, session serializer mismatch. Session upload progress can write attacker-controlled data with one session serializer while another application, pool or script reads the same session with a different one, so part of a session key is decoded as serialized objects.

CVE-2026-129289, PHP-FPM request smuggling. When an application opened php://input without reading it to the end, PHP skipped discarding the unread request body. On a kept-alive FastCGI connection, those attacker-controlled bytes were parsed as a new FastCGI request, bypassing the web server’s routing and running attacker-chosen PHP code. No authentication is needed.

CVE-2026-129291, PHP-FPM epoll use-after-free. With catch_workers_output enabled, an attacker who can already run PHP code in an unprivileged FPM worker can make the master dispatch an event into a freed worker record and run commands as the FPM master, which commonly runs as root.

The release also fixes mixed-case HTTPS://` andFTPS://URLs silently using plaintext, a PHAR signature downgrade, a CGIPATH_INFO` out-of-bounds write, XSS on the FPM status page, folded-header denial of service, and two SOAP memory bugs.

Fixes for code that does not exist in an older branch are not counted in the tables; each version’s page lists exactly which ones it carries and why the rest do not apply.

One difference from upstream, on purpose. Upstream closes CVE-2026-115560 by turning session.upload_progress.enabled off by default. Builds of PHP 8.1 and older keep your session settings unchanged: the session upload-progress writer has been disabled there since the PHP2Shell fix, so the serializer mismatch cannot happen. PHP 8.2 and newer follow upstream, so if an application polls upload progress on those versions, set session.upload_progress.enabled = On in php.ini.

Check whether your server is patched

On RPM systems:

php -v | grep 'Built by'

Compare the release with the tables above, or run CVEfox, the free GetPageSpeed scanner:

yum -y install https://extras.getpagespeed.com/release-latest.rpm
yum -y install cvefox
cvefox scan

Restart PHP-FPM or Apache after upgrading: an already running master process keeps the vulnerable timezone state until it is restarted.

Interim mitigations

Until you upgrade: fix any configuration warning PHP prints at startup (an invalid date.timezone, deprecated session settings), send PHP errors to syslog instead of a file, and restart the PHP master process. These narrow the timezone cache bug only; the other fixes need the update.

FAQ

Is PHP 7.4 affected by CVE-2026-129496?

Yes. The vulnerable code is identical in every branch back to 5.3, and upstream fixed only 8.2 and newer. GetPageSpeed builds of PHP 7.4 carry the fix on CentOS 7 (7.4.33-45.el7), Amazon Linux 2 (7.4.33-45.amzn2) and Ubuntu 20.04 (1:7.4.33-31+gps1+ubuntu2004+stable.5).

Do I need a subscription?

Not for personal, development or evaluation use: the packages are free to install from the public GetPageSpeed repository. Commercial production use requires GetPageSpeed Ultra ($500/year, up to 10 servers running your own services) under the repository terms. Administering servers for clients, or more than 10? GetPageSpeed Fleet starts at $800/year.

Will PECL extensions and ionCube Loader keep working?

Yes. None of the fixes changes a structure layout or API number.

Conclusion

Seven critical PHP bugs, fixed upstream only for 8.2 and newer. GetPageSpeed carries the fixes for every EOL PHP line it ships, on CentOS 7, CentOS 6, Amazon Linux 2, EL8/EL9 Remi collections, Ubuntu 18.04 and 20.04, and Debian 10, in place. Read the PHP2Shell write-up for how these builds are validated.

Exit mobile version