blog

PHP's November update fixes the upload progress bug. Keep the setting off anyway

PHP released security updates for every supported version yesterday. They include the fix for the session upload progress bug I wrote about last month, plus a PHP-FPM flaw that depends on one setting in your web server.

If you turned upload progress off in October, leave it off. Here's why, and what else to check this week.

What happened

On 19 November PHP released 8.5.13, 8.4.28, 8.3.37 and 8.2.36. Each one is described simply as "a security release". The 8.4 changelog lists the fixes, and Aikido counts 18 in all. PHP warned the day before that the critical ones "require either non-default configuration or uncommon setups".

Two of them matter most for the sort of servers I look after.

CVE-2026-115560 is the upload progress bug. PHP's full advisory is now out, and it's broader than October's notice suggested. Back then, PHP said it needed an app to switch a session setting while running. The advisory now says "a runtime configuration change is not required". Two sites, FPM pools or scripts that share a session folder but use different session settings can trigger it too.

CVE-2026-129289 is a PHP-FPM request smuggling flaw. It only bites if your web server keeps its connections to PHP-FPM open between requests. If it does, a crafted upload can sneak a second request through, and that can end with an attacker running their own PHP code. PHP rates both of these 9.2 out of 10.

Neither advisory, nor anything else I've read, reports these being used in attacks yet. The upload progress advisory does include working proof-of-concept code, though, so I wouldn't wait long.

Does it affect you?

Shared hosting or a managed platform. Your host runs PHP, so it's theirs to patch. It's fair to ask when.

Your own server. Check your version with php -v. Anything below the versions above needs the update.

On Debian and Ubuntu the version number looks different, because they copy fixes into their own builds. Check the security trackers instead.

Debian was ahead this morning. The security tracker shows Debian 13 fixed in php8.4 8.4.28-1~deb13u1 and Debian 12 fixed in php8.2 8.2.36-1~deb12u1.

Ubuntu wasn't. Its CVE page still said "Needs evaluation" for php8.3 on 24.04 when I looked.

What to do this week

1. Install the update if you can. On Debian, sudo apt update && sudo apt upgrade and then restart PHP-FPM (sudo systemctl restart php8.4-fpm, or whichever version you run). Workers keep running the old code until they restart.

2. Keep upload progress off. The fix switches it off by default. But the advisory warns that "an explicit setting overrides the new default", so if a config file somewhere says On, it stays on. This finds it on Debian or Ubuntu:

grep -r upload_progress /etc/php/

If you added the 99-upload-progress.ini file from my October post, keep it. If you're on Ubuntu and still waiting for packages, it's your main protection. Set it in php.ini or the FPM pool, not in code. The advisory is blunt: "Calling ini_set() from the application is too late."

3. Check whether your web server reuses connections to PHP-FPM. This is the one most people won't know. On nginx:

sudo nginx -T | grep -n fastcgi_keep_conn

On Apache with PHP-FPM, look for enablereuse=on in your proxy settings:

sudo grep -rn enablereuse /etc/apache2/

If nothing comes back from either, you're on the safe side of this one. Both are off by default. If one is on and you can't update yet, the advisory's workaround is to turn it off and reload the web server. Expect a small cost in speed, nothing more.

4. Make sure PHP-FPM isn't reachable from outside. The advisory says not to expose FPM listeners to untrusted networks. If your pool listens on a TCP port rather than a socket file, check your firewall blocks it from the internet.

5. Plan off PHP 8.2. PHP says 8.2 stops getting security updates on 31 December, so this is close to the end for it.

The bigger point

October's notice said the upload progress bug needed "an unusual combination of configuration and application code". The full advisory has widened that a fair bit. That's no criticism of PHP. The detail only comes out when the fix does, and that's normal.

But it's why I'd rather switch a feature off on day one than wait to find out whether I really needed to. Dev Partners wrote recently about AI turning security patches into working attacks. The sooner you close the door, the less that matters.

If you run a bespoke PHP app and aren't sure whether it relies on upload progress, or opens php://input in odd places, the team at Dev Partners look after existing software and can check.

And if you'd rather someone else read the advisories and did the restarts, that's what my support retainers are for.