Azure Linux 3.0 carries the PHP-FPM fix for CVE-2026-129291

A server enclosure with a row of smaller modules beneath its controller.

If a server runs PHP-FPM, a low-privilege worker should stay on its side of the privilege boundary. This flaw can let someone who already runs code in a worker reach the privileges of the master process.

What changed

PHP disclosed CVE-2026-129291 on November 19, 2026. Microsoft initially listed Azure Linux 3.0 php 8.3.36-1 on November 20 UTC and revised the advisory November 21 UTC. Its FixedBuild field remains blank. Microsoft’s production base repository carries php-fpm 8.3.37-1.azl3 for x86-64 and ARM64. Both RPMs matched repository checksums and were already hosted November 20. PHP confirms the fix in upstream 8.3.37. The Microsoft source recipe reviewed still showed 8.3.36-1.

Check the running service and pool

The affected path requires an attacker who can run PHP code in an unprivileged FPM worker, an affected pool with catch_workers_output enabled, and the epoll event backend. Successful escalation inherits the FPM master’s privileges, which can be root. In a container, the resulting privileges are those of the container’s master process. The flaw by itself does not establish a container escape.

PHP lists affected upstream versions 8.1.20–8.1.34, 8.2.7 through versions below 8.2.36, and 8.3.0, 8.4.0, and 8.5.0 through versions below 8.3.37, 8.4.28, and 8.5.13, respectively. PHP lists fixes at those upper bounds and supplies no 8.1 fix. The full older Azure Linux package range is unspecified.

Microsoft rates the Azure Linux row Important and supplies no numeric score. PHP’s CNA rates it High, CVSS 4.0 8.8. PHP documents lab reproduction. Confirmed malicious exploitation and vendor-directed compromise checks or credential rotation were not verified. The CVE is absent from CISA KEV as of November 22, 2026. There is no federal KEV deadline.

MSP action

Suggested priority: High for affected deployments where tenant or application code can run in PHP-FPM and the master is privileged. Inventory package and image builds, running master privileges, and effective pool configuration. If suspicious activity is present, isolate the affected application where feasible and preserve evidence. If you must delay patching, review the affected pool’s output capture and logging dependencies before considering a temporary configuration change. No vendor workaround was verified. Pilot the supported package update, restart or redeploy PHP-FPM, and verify the running build, tested requests, logging and active pools. Rebuild and roll out copies in container images separately.

Official sources

Microsoft November CVRF · PHP advisory · PHP 8.3.37 changelog · PHP CNA record · Microsoft x86-64 repository metadata · Microsoft ARM64 repository metadata · CISA KEV data

Last verified November 22, 2026 ET.

Share this article