ALPINE-CVE-2026-129289: Critical severity alpine/php83 vulnerability
PHP-FPM request smuggling through an unread HTTP request body.
PHP does not discard the unread part of an HTTP request body at request shutdown when the application has opened php://input without reading it to the end. When the front end reuses backend connections, which is not the default in nginx or Apache (for example nginx with fastcgikeepconn on, or Apache modproxyfcgi with enablereuse=on), PHP-FPM can parse the leftover bytes as a new FastCGI request. An unauthenticated remote attacker can use a single crafted multipart/form-data request to forge a backend request with chosen parameters such as SCRIPTFILENAME, REMOTEADDR and PHPADMINVALUE, which can lead to execution of attacker-controlled PHP code. With LSAPI, subsequent requests on the connection can be disrupted.
This issue affects PHP versions before 8.2.36, 8.3. before 8.3.37, 8.4. before 8.4.28 and 8.5. before 8.5.13.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
alpine/php83to a version that resolves this vulnerability.Fixed in 8.3.37-r0 - Upgrade
Upgrade
alpine/php84to a version that resolves this vulnerability.Fixed in 8.4.28-r0 - Upgrade
Upgrade
alpine/php85to a version that resolves this vulnerability.Fixed in 8.5.13-r0 - Upgrade
Upgrade
PHPto a version that resolves this vulnerability.Fixed in 8.2.36 - Upgrade
Upgrade
PHPto a version that resolves this vulnerability.Fixed in 8.3.37 - Upgrade
Upgrade
PHPto a version that resolves this vulnerability.Fixed in 8.4.28 - Upgrade
Upgrade
PHPto a version that resolves this vulnerability.Fixed in 8.5.13
Event History
Frequently Asked Questions
Which PHP versions require remediation?
Update PHP 8.2 to 8.2.36 or later, PHP 8.3 to 8.3.37 or later, PHP 8.4 to 8.4.28 or later, and PHP 8.5 to 8.5.13 or later. Earlier versions in those branches are affected.
Are standard nginx or Apache PHP-FPM deployments exposed by default?
Backend connection reuse is required and is not enabled by default in nginx or Apache. Exposure increases when nginx uses fastcgi_keep_conn on or Apache mod_proxy_fcgi uses enablereuse=on.
What does an attacker need to exploit this issue?
An unauthenticated remote attacker can send a single crafted multipart/form-data request. Exploitation depends on the application opening php://input without reading the body to the end and on the frontend reusing the backend connection.
What can be done if PHP cannot be updated immediately?
Disable frontend-to-PHP-FPM backend connection reuse where possible, including fastcgi_keep_conn in nginx or enablereuse in Apache mod_proxy_fcgi. This removes the connection-reuse condition described for PHP-FPM exploitation.
How can I assess whether an application is currently at risk?
Check whether the installed PHP version is older than the fixed release for its branch, whether the frontend reuses PHP-FPM backend connections, and whether application code opens php://input without consuming the full request body. All of these conditions are relevant to the described PHP-FPM attack path.