JM Tech Power

新闻

PHP security releases: update to 8.5.13, 8.4.28, 8.3.37 or 8.2.36

← All articles Email RSS Atom

News · written 21 November 2026. A summary for readers, not technical advice — check the sources at the end for the details.

On 19 November 2026 the PHP development team released PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36. Each announcement says the same thing: This is a security release, and all users of that branch are encouraged to upgrade. A day earlier, the project had warned that the highest severity is CRITICAL, adding that the critical issues need either a non-default configuration or an uncommon setup.

What is fixed

The changelog for 8.5.13 lists 18 security entries; the older branches get the ones that apply to them (14 in 8.4.28, 13 in 8.3.37, 12 in 8.2.36). Among them:

  • PHP-FPM: request smuggling through an unread HTTP request body (CVE-2026-129289), a use-after-free that can lead to local privilege escalation (CVE-2026-129291), and cross-site scripting on the status page (CVE-2026-129292).
  • Sessions: a serializer mismatch and partially overwritten session files that can each lead to remote code execution (CVE-2026-115560, CVE-2026-126714).
  • Date: a timezone cache use-after-free that can lead to remote code execution (CVE-2026-129496).
  • PHP-CGI: an out-of-bounds read and write while correcting PATH_INFO (CVE-2026-129538).
  • Phar, SOAP and the standard library: a Phar signature bypass, two SOAP bugs, and mixed-case HTTPS and FTPS URLs that could send data in plain text.
  • PHP 8.5 only: two use-after-free bugs in error backtraces, one of which can lead to remote code execution.

What to do

  • Run php -v and update to the fixed version for your branch, through your Linux distribution, container image or hosting panel. Then restart PHP-FPM or your web server so the new version is actually in use.
  • Until you can update, Mattias Geniar's patch-status page (not the PHP project) suggests turning off FastCGI connection reuse, for example by removing fastcgi_keep_conn on from nginx. He stresses that this is a workaround, not a fix.
  • PHP 8.1 and older get no updates from the PHP project. PHP 8.2 reaches end of life on 31 December 2026, so plan a move to a newer branch.
  • PHP 8.6.0 came out the same day. It is a major release, not a security release, and already includes these fixes.

Sources

More news at https://jmtechpower.com/articles.

Comments (0)

No comments yet. Be the first to comment!