A server that passed October’s PHP patch check can still need an update today.
PHP released security updates on Nov. 19 for its 8.2, 8.3, 8.4, and 8.5 branches. The release notices urge users to update within their branch. PHP rated the most severe issues critical, but its advance warning said those issues require nondefault configurations or uncommon setups.
That distinction can help teams decide what to patch first. The version that matters is the one actually serving the website, not necessarily the version an administrator sees when checking PHP from the command line.
Which PHP versions have fixes?
These are the upstream security releases for each existing branch. PHP also released 8.6.0 on Nov. 19 as a separate feature release. Teams running one of the branches below don’t need to move to 8.6 to get their branch’s security update.
If you run | Install this upstream security release |
| PHP 8.2 | 8.2.36 |
| PHP 8.3 | 8.3.37 |
| PHP 8.4 | 8.4.28 |
| PHP 8.5 | 8.5.13 |
If you get PHP from a Linux distribution or managed host, check that vendor’s advisory before deciding that your system is still vulnerable. A distributor can apply a security fix to an existing package without adopting PHP’s upstream version number. In that case, the vendor’s package revision is the number to verify. Our Linux patch management guide explains why patching can differ across distributions.
What makes the critical flaws different?
PHP’s published security advisories describe two critical session-handling flaws that can allow remote code execution under certain conditions. One depends on a particular configuration. The other affects PHP’s default file-based session handler, but using that handler alone does not establish that an application can be exploited. The advisory describes additional conditions that must be present.
The release notices and advisories do not report confirmed attacks using these newly disclosed flaws. That’s separate from the October PHP patch cycle, in which researchers reported exploitation attempts targeting earlier vulnerabilities. Don’t carry October’s attack claims over to the November fixes.
How to verify the fix reached production
Start with public-facing applications that use PHP, especially services your team can’t easily take offline. Then track runtime through deployment rather than treating a successful package installation as proof that every site is protected.
If you run a fleet of web servers, group the applications by how they get updates. A patch applied to one host may leave a separately managed site or a container on the old build. Give each group a named owner and a way to verify the fix. If a hosting provider hasn’t confirmed its rollout, keep that service on the open list rather than counting it as patched.
- Find the PHP runtime each application uses. Check web servers, containers, and managed hosting accounts. Two sites on the same machine can run different versions.
- Identify who applies the fix. For a managed site, ask the host which package or runtime it updated and when the change reached your environment. For containers, check the image actually running in production.
- Verify the live service after deployment. Confirm the running build against the upstream or vendor advisory. Test sign-ins, uploads, and other workflows your application depends on.
Follow your patch management process if testing uncovers a regression. If restoring an older build would remove the fix, record that as an open security exception with an owner and a date to retry the update.
PHP 8.2 operators have a second deadline. The branch’s upstream security support ends Dec. 31, 2026. Apply the November fix now, then schedule compatibility testing for a move to a newer supported branch. Those are separate jobs: one closes the known flaws, and the other keeps the site eligible for future upstream fixes.
Read more: See what Google found about how attackers can turn patch disclosures into a head start.





