PHP 8.3.37 (19 Nov 2026) fixes three security issues in PHP-FPM (Changelog). Each one needs a specific FPM or web server setting before it can be exploited, so the version number alone does not tell you whether you are exposed. This article shows how to check each one on an Ubuntu server running Nginx and PHP-FPM.
The Issue
| CVE | Issue | Severity (CVSS 4.0) | Exploitable when |
|---|---|---|---|
| CVE-2026-129289 | Request smuggling through an unread request body | Critical (9.2) | The web server reuses its connections to FPM |
| CVE-2026-129292 | XSS in the FPM status page | Moderate (5.3) | The status page is enabled and viewed as HTML |
| CVE-2026-129291 | epoll use-after-free, local privilege escalation | High (8.8) | catch_workers_output is enabled |
All three affect PHP-FPM below 8.2.36, 8.3.37, 8.4.28 and 8.5.13. CVE-2026-129291 also affects 8.1.20 to 8.1.34, and the 8.1 branch has no fix.
- Check the FPM version first.
php -vreports the CLI, which is a separate binary.
$ php-fpm8.3 -v
NOTE: On Ubuntu with the ondrej/php PPA the binary is php-fpm8.3. In the official Docker image it is php-fpm.
#1 Request smuggling (CVE-2026-129289)
When the web server keeps a FastCGI connection open and reuses it, a malformed multipart/form-data body that the app never reads can leave attacker bytes in the stream. FPM then parses those bytes as the next request. The advisory demonstrates arbitrary PHP execution, reaching scripts outside the web server's routes, and forging REMOTE_ADDR. (Reference)
Nginx only reuses connections to FPM when both of these are set. Both are off by default.
fastcgi_keep_conn on;in thelocationthat passes requests to PHP.- An
upstreamblock withkeepalive N;, whichfastcgi_passpoints to.
- Search the full Nginx config.
nginx -Tprints every included file, sosites-enabled/andconf.d/are covered.
$ sudo nginx -T 2>/dev/null | grep -nE 'fastcgi_keep_conn|upstream|keepalive|fastcgi_pass'
206: fastcgi_pass unix:/run/php/php8.3-fpm.sock;
NOTE: If this prints nothing at all, drop 2>/dev/null to see why nginx -T failed. A keepalive_timeout line in the http block is about browser connections and does not count.
- Read the result. In the sample above,
fastcgi_passgoes straight to the socket, with nofastcgi_keep_connand noupstream. Nginx closes the connection after every request, so this server is not affected.
#2 Status page XSS (CVE-2026-129292)
The FPM status page prints some request fields without escaping them.
- Check whether the status page is enabled:
$ sudo php-fpm8.3 -tt 2>&1 | grep -E 'pm.status_path'
[20-Nov-2026 11:34:42] NOTICE: pm.status_path = undefined
-
Read the result.
undefinedmeans the status page is off, so this server is not affected.-ttprints one line per pool, so check every line. -
If
pm.status_pathis set, search the Nginx config for alocationthat forwards it to FPM. Adjust the pattern to your path.
$ sudo nginx -T 2>/dev/null | grep -nE 'location.*(status|fpm)'
#3 epoll use-after-free (CVE-2026-129291)
Someone who can already run PHP code in an FPM worker can use this bug to take over the FPM master process. It needs catch_workers_output enabled in the pool and the epoll event backend, which FPM selects automatically on Linux. (Reference)
- Check both settings:
$ sudo php-fpm8.3 -tt 2>&1 | grep -E 'catch_workers_output|events.mechanism'
[20-Nov-2026 11:34:54] NOTICE: events.mechanism = epoll
[20-Nov-2026 11:34:54] NOTICE: catch_workers_output = no
- Read the result.
catch_workers_output = nois the default, so this server is not affected even though it uses epoll.
NOTE: The official PHP-FPM Docker images turn catch_workers_output on. Check containers separately from the host.
The Fix
-
Upgrade to PHP 8.3.37, or to 8.2.36, 8.4.28 or 8.5.13 on the other branches. On Ubuntu with the ondrej/php PPA, the steps are the same as in the previous article.
-
Verify the FPM version:
$ php-fpm8.3 -v
PHP 8.3.37 (fpm-fcgi) (built: Nov 19 2026 20:02:49)
Copyright (c) The PHP Group
Zend Engine v4.3.37, Copyright (c) Zend Technologies
with Zend OPcache v8.3.37, Copyright (c), by Zend Technologies
NOTE: -v reports the installed binary, not the running process. Reload FPM after the upgrade with sudo systemctl reload php8.3-fpm.
References
- php.net - PHP 8 ChangeLog: https://www.php.net/ChangeLog-8.php#8.3.37
- GitHub - GHSA-qc49-hpvq-g2w6 (CVE-2026-129289): https://github.com/php/php-src/security/advisories/GHSA-qc49-hpvq-g2w6
- GitHub - GHSA-3mg3-cr28-46gc (CVE-2026-129292): https://github.com/php/php-src/security/advisories/GHSA-3mg3-cr28-46gc
- GitHub - GHSA-jm4m-qfqx-967m (CVE-2026-129291): https://github.com/php/php-src/security/advisories/GHSA-jm4m-qfqx-967m