PHP security updates patch 18 flaws, including critical RCE bugs
The PHP project released updates that fix 18 vulnerabilities, including critical remote code execution bugs that affect certain web server configurations. Administrators should prioritize upgrading or apply documented mitigations.
The PHP development team released security updates addressing 18 vulnerabilities, including critical flaws that could allow unauthenticated attackers to run code on vulnerable servers, according to BleepingComputer. The fixes are available now for supported branches, and administrators are being urged to upgrade or apply mitigations immediately.
What the updates change
BleepingComputer reports the new releases are available for the supported branches and include versions 8.5.13, 8.4.28, 8.3.37, and 8.2.36. Security firm Aikido told BleepingComputer the updates cover 18 CVEs that touch PHP core, session handling, PHP-FPM, CGI, and other components. One of the most serious items, tracked as CVE-2026-129289, is a PHP-FPM request smuggling vulnerability with a high severity score that can let unauthenticated attackers execute PHP code remotely under certain conditions.
Other notable fixes listed by BleepingComputer include use-after-free and session handling flaws (for example CVE-2026-129474, CVE-2026-129496, CVE-2026-126714, CVE-2026-115560), an epoll use-after-free that could lead to local privilege escalation (CVE-2026-129291), and a PHAR OpenSSL signature bypass (CVE-2026-128090). The updates also address a range of memory corruption, information disclosure, cross-site scripting, denial-of-service, and unsafe URL handling issues.
Who is most at risk
According to BleepingComputer, successful exploitation of the most severe issues generally requires non-default or uncommon setups. As the PHP security team warned, "The issues rated CRITICAL require either non-default configuration or uncommon setups." In particular, the PHP-FPM request smuggling flaw affects deployments where the front end reuses backend connections to PHP-FPM, including some nginx, Apache mod_proxy_fcgi, HAProxy, and LSAPI setups that keep connections open between requests.
Standard nginx and Apache configurations that do not reuse backend connections are not affected by that specific attack path, BleepingComputer says. However, several other fixes cover vulnerabilities that could be triggered in different environments, including session handling and serializer mismatches, so a broad review is still warranted.
PHP security updates: what to do now
If you run PHP on any public-facing servers, take these practical steps right away:
- Upgrade to the patched supported releases listed by the PHP team (for example the versions noted by BleepingComputer) as soon as you can. Treat this as a priority security update.
- If you cannot install updates immediately, apply available mitigations: disable persistent backend connections between web servers and PHP-FPM so connections close after each request, and consider disabling session upload progress by setting session.upload_progress.enabled to 0 and restarting PHP workers, as recommended.
- Ensure PHP-FPM and LSAPI listeners are not directly exposed to untrusted networks, per Aikido's guidance reported by BleepingComputer.
- Review any non-default web server settings that reuse backend connections, for example nginx fastcgi_keep_conn or Apache mod_proxy_fcgi reuse options, and change them if you cannot patch quickly.
- After upgrading or applying mitigations, monitor logs and worker crashes for unusual activity and validate that your web server configuration behaves as expected.
If you want a quick external check of how exposed your site is, start with a free external scan on our site: Want to know how exposed your own site is? Start with a free external scan.
Longer term steps and options for unsupported PHP versions
BleepingComputer notes that third-party maintainers have provided patched packages for older, unsupported releases. Specifically, packages from Ondrej Sury and hardened container images from Aikido include backported fixes for versions going back to older branches. If you rely on unsupported PHP releases and cannot upgrade to a supported branch, use those trusted backports or migrate to a supported release as soon as possible.
Also review your application code for any reliance on unusual session or serializer configurations, and minimize attack surface by keeping internal admin interfaces and PHP-FPM listeners off public networks.
How we recommend you prioritize this work
- Identify all public-facing and internal servers running PHP.
- Patch supported PHP branches immediately where possible.
- Apply mitigations (disable persistent backend connections, turn off session upload progress) where patching is delayed.
- For unsupported versions, use trusted third-party backports or plan migration to supported releases.
- Confirm protections with logs and scans, and keep an eye on vendor and security firm advisories for follow-up details.
The updates released on Thursday address a range of high-severity problems and should be treated like a critical maintenance task for any organization running PHP-powered sites or services. For the technical report and CVE list, see the coverage on BleepingComputer linked in the reporting above.
Sources
- PHP security updates fix 18 flaws, including critical RCE bugs BleepingComputer
- PHP Fixes 7 Critical Flaws, Including Bugs That Could Allow Remote Code Execution The Hacker News
- PHP Readies Critical Security Updates to Patch Another RCE Flaw SecurityWeek
This post was drafted with AI from the reporting linked above and published by The Jones Foundry. For full details, read the original sources.