Vulnerabilities

PHP Security Updates Fix Critical PHP-FPM RCE Flaw (CVE-2026-129289)

New PHP releases fix flaws, some of which can lead to remote code execution. Admins should also check the PHP packages their hosting provider ships.

PHP Security Updates Fix Critical PHP-FPM RCE Flaw (CVE-2026-129289)

On November 19, the PHP team released security updates for all supported branches of the language. The fixes address vulnerabilities that, in certain configurations, could allow remote code execution. The patched releases are PHP 8.2.36, 8.3.37, 8.4.28, and 8.5.13.

What’s the risk

The fixes cover several parts of the runtime, including session handling and PHP-FPM. According to BleepingComputer, one of the critical flaws, CVE-2026-129289, involves how PHP-FPM handles requests. Under certain connection-reuse configurations, it could let an unauthenticated attacker execute code remotely.

The actual server configuration matters. Running PHP doesn’t automatically mean every one of these flaws can be exploited in your environment. But PHP powers a huge number of websites and applications, and updating your content management system doesn’t necessarily update the PHP runtime underneath it.

Hosting providers may ship PHP in their own packages, and a single server can run more than one branch or build. Administrators should check more than the version shown in the terminal. They also need to confirm the version that applications and PHP-FPM processes are actually running.

What to do now

  • Build an inventory of PHP installations, including production, test, and container environments.
  • Update every branch in use to the matching patched release, or to a vendor package that includes the relevant fixes.
  • After deployment, check the running services and confirm which version is serving live application traffic.
  • If the update has to wait, review the guidance for your specific configuration. For CVE-2026-129289, the mitigation described by BleepingComputer is to disable persistent connections between the web server and PHP-FPM.

That configuration change only blocks one specific attack path. It does not fix the other vulnerabilities addressed in the release. Check with your hosting provider when the patched packages were rolled out for each service.

SecurHUB’s take

A dependency inventory shows which applications rely on a vulnerable component and who is responsible for updating it. Security audits can help you review your configuration and your patch management process.

Sources: BleepingComputer, Semgrep, cPanel

AuthorSecurHUB Team

Read more

Related articles

Want to know if this affects your company?

A free consultation with one of our experts — no obligation, in full confidence.

Let's talk