PHP · CVE-2026-129289
PHP-FPM smuggling
Patch now if…Only if FastCGI connections are reused. Fixed 19 Nov.
A bug in PHP-FPM can let an attacker with no login sneak a second, hidden request to PHP in one web request and run their own code. It only works where the web server reuses its connections to PHP-FPM (off by default in nginx and Apache) and the app opens the request body without reading all of it. PHP rates it Critical (CVSS 9.2); public test code runs PHP on a target, and the 19 Nov 2026 releases fix it.
How scary is it?
Are you affected? only if all are true
1PHP-FPM older than the 19 Nov 2026 fixcommand
Below 8.5.13, 8.4.28, 8.3.37 or 8.2.36. PHP 8.6.0 (19 Nov) is fixed. PHP says the bug has been in the code since 5.6.0, so older, unsupported PHP is affected too. The code-execution attack needs PHP-FPM; with LiteSpeed's LSAPI it only breaks later requests. Distros may backport the fix without changing the version number.1,2,3,10
php-fpm -v2The web server reuses FPM connectionscommand
nginx with fastcgi_keep_conn on, Apache mod_proxy_fcgi with enablereuse=on, or HAProxy keeping FastCGI connections open. Both nginx and Apache close the connection by default, which is not affected, but Apache's own PHP-FPM example turns reuse on. PHP's advisory doesn't mention Caddy. For Apache, look for enablereuse=on in your config.1,4,5
nginx -T 2>/dev/null | grep fastcgi_keep_conn3The app leaves the body unread
Some code path opens php://input and doesn't read it to the end. PHP says frameworks that open the input stream before routing or login checks can be affected; public test code worked against an unmodified Slim 4 app. Reading the body fully avoids it, but PHP says that isn't reliable on its own.1,6
What to do
1Update PHP and restart FPM
Update to 8.6.0, 8.5.13, 8.4.28, 8.3.37 or 8.2.36 (19 Nov 2026), then restart PHP-FPM. Debian has fixed packages (DSA-6641-1 for Debian 13, DLA-4916-1 for Debian 12); Ubuntu's supported releases were still "needs evaluation" on 20 Nov.1,2,10,8,9
Latest safe versions checked 20 Nov
2Turn off connection reusecommand
Until you've updated: in nginx, remove fastcgi_keep_conn on (off is the default); in Apache, remove enablereuse=on. Then reload the web server.1,4,5
fastcgi_keep_conn off;3Keep PHP-FPM off the network
Don't let untrusted networks reach PHP-FPM's port or socket directly.1
This page shows you how to check. It can't tell you you're safe.
Sources (10) and changelog
- PHP GHSA-qc49: full advisory, affected setups, mitigations 19 Nov
- PHP: 8.x ChangeLog, 19 Nov 2026 releases 19 Nov
- CVE record: affected versions, CVSS 9.2, CISA SSVC exploitation none 19 Nov
- nginx docs: fastcgi_keep_conn is off by default
- Apache docs: mod_proxy_fcgi reuse off by default; PHP-FPM example turns it on
- Public Nuclei templates; active one runs PHP on the target 19 Nov
- CISA KEV catalog: not listed
- Debian tracker: DSA-6641-1, DLA-4916-1
- Ubuntu: CVE tracker, needs evaluation
- PHP: 8.6.0 ChangeLog, fixes GHSA-qc49 19 Nov
- Published.