phpstorm.dev

PHP ecosystem insights

PHP knowledge

Versioned PHP knowledge with primary sources and explicit verification dates.

Source checks through 2026-10-27 · 57 sources · This published snapshot is over 48 hours old.

Verified 2026-10-21 Permanent entry

PHP digest — 21 October 2026

PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 fix two critical remote code execution vulnerabilities, released at 14:00 UTC as announced in the 20 October edition. Also: a critical Laravel advisory for the token auth guard, disclosed on 19 October for a fix released in August, the formal acceptance of the End PEAR Project Endorsement RFC, Symfony 8.2 moving Messenger message signing from handlers to transports, PHP 8.6.0RC4 (which also carries the fixes), and two RFC vote updates.

PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 fix two critical RCE vulnerabilities

At about 14:00 UTC the PHP project released PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 and asked all users to update immediately. Both php-src advisories are rated critical (CVSS v4 9.2) and list every version below those releases on each branch as affected:

php.net lists PHP-FPM, mod_php, php-cgi, FrankenPHP and LiteSpeed as at risk, highest for mod_php. The project says updating is the only complete mitigation; its interim measures (for example session.upload_progress.enabled=0 or, on 8.5, fatal_error_backtraces=0) only reduce specific paths and are listed with their conditions in the announcement and advisories. 8.2.35 and 8.3.36 contain only these fixes; 8.4.27 and 8.5.12 were scheduled bug-fix releases and carry many other fixes. There are no releases for PHP 8.1 and older, but the security team provided minimal source backports for 7.4, 8.0 and 8.1. The ChangeLog still dates the releases 22 October.

A PHP Foundation post says the release was moved forward from 22 October after the CVE IDs, with a wrong CVSS score of 10.0, leaked on 20 October; that the OOM root cause was first seen in 2024 and work on a fix stalled until Calif and OpenAI independently reported RCE on 11 August; and that Chainguard published patched images at 07:41 UTC today, before the coordinated release. These are the Foundation's statements. Details: release page.

Laravel: critical auth bypass in the token guard (fixed in 13.29.0 and 12.68.0)

On 19 October Laravel published GHSA-f9x3-7vq9-cph6 for laravel/framework, rated critical (CVSS v4 9.2). It concerns Illuminate\Auth\TokenGuard, the class behind the token guard driver. According to the advisory, on MySQL/MariaDB an attacker can send a specially crafted non-string credential that the authentication lookup mishandles, so the query matches an unintended user instead of failing. An unauthenticated attacker could then authenticate as an existing user without that user's API token, on any route the guard protects. Affected: below 13.29.0 and below 12.68.0; patched: 13.29.0 and 12.68.0. Those releases were tagged on 25 August (12.68.0 the same day), nearly two months before disclosure. In the v13.29.0 source both user() and validate() reject a token that is not a string before querying the user provider. The advisory names no CVE. It covers only the framework's token driver; this edition makes no claim about other guards or packages.

The same day Laravel published GHSA-5wcm-3v2w-8362 (moderate, CVSS v3.1 6.5, no CVE): a crafted request to a read-only endpoint could trigger a destructive operation on a related table through the way relationship inclusion is processed. The advisory lists affected versions as ">= 12.45.0" and "< 13.27.0" and patched versions as 12.68.0 and 13.27.0; it does not name the feature, and Laravel News (secondary) links it to the JSON:API resources added in 12.45.

Neither advisory was in the Packagist advisory data collected at 22:01 UTC on 20 October.

End PEAR Project Endorsement RFC accepted

At 02:06 UTC the author announced on internals that the End PEAR Project Endorsement RFC was accepted 40 Yes, 0 No, 0 abstentions; it needed 2/3 on its single question. The poll had closed on 19 October at 13:15 UTC (19 October edition). The RFC page now says Accepted (last modified 2026-10-21 02:02 UTC), and the official RFC index collected at 04:01 UTC lists it as accepted. The RFC proposes a static pear.php.net archive (browsable until 2027-12-31), no longer installing PEAR with PHP source from PHP 8.7, removing PEAR from official PHP websites, and moving the PEAR mailing lists to inactive. Acceptance is a decision, not an implementation. The php-src pull request it formalises was last seen as an unmerged draft, and nothing in released PHP has changed. See the RFC page.

Symfony 8.2: signed Messenger transports and per-feature secret rotation

A Symfony blog post (07:16 UTC) describes changes merged into the 8.2 branch; Symfony 8.2 is not released. In Symfony 7.4, signing is enabled per handler (#[AsMessageHandler(sign: true)]), so on receipt Symfony has to read the unverified message type, and autoload the class it names, before it knows whether a signature is required. According to the post:

PHP 8.6.0RC4 and RFC vote updates

Coverage

At 04:01 UTC the 32 due feed, release and index sources were collected; the 25 daily package, adoption, support-window and advisory sources were not due and keep their data from 22:01 UTC on 20 October. The RFC-wiki changes feed (php-rfc-changes) timed out on three attempts and succeeded on a fourth at 04:09 UTC; its only new entry is the end_pear_endorsement edit at 02:02 UTC. The official RFC index (952 entries) was collected and now lists three RFCs as voting: Filter enums, IntlRelativeDateTimeFormatter (closes 22 October) and invalid number-base input. New records since the 20 October edition were internals message 132884, the End PEAR status in the index, and a Laravel News preview of today's PHP security release that adds nothing beyond the php.net notice. One older Laravel News record (20 October, 00:24 UTC) pointed to the Laravel advisories above, which earlier editions missed.

At 10:01 UTC the 32 due feed, release and index sources were collected again without failures (health --fail-stale: 57 ok, none stale); the daily sources were not due. The only new record was the Symfony post above. The RFC index (952 entries, the same three voting) and internals had no new entries, and the php.net feed still shows the 20 October notice as its newest entry; the PHP security release was not yet due.

At 16:01 UTC the 32 due feed, release and index sources were collected again; the daily sources were not due. The three php.watch feeds failed with HTTP 502 (their data from 10:01 UTC is kept), and news-web.php.net returned 502 for individual internals messages, which were read on externals.io instead. New records covered the PHP security release (php.net, internals, php-src tags, release JSON, the PHP Foundation post, Laravel News, WordPress News, phpnews.net and Laravel's hosting status page), PHP 8.6.0RC4, the two RFC threads above, Laravel 12.70.1 (one change, "Prevent escaping from bypassing protection", a 12.x backport of a security fix; no advisory was read, not covered) and a SymfonyCon post. The phpnews.net articles are secondary and were not used for facts. The RFC index (952 entries) still lists the same three RFCs as voting. The Packagist advisory data was not due, so whether it lists the PHP or Laravel advisories was not checked.

At 22:01 UTC all 57 sources were collected without failures, including the daily sources and the three php.watch feeds (health --fail-stale: 57 ok, none stale). New records were the 8.6.0RC4 announcement and the two Io\Terminal messages above, plus daily package statistics and support-window data. The Packagist advisory data still contains neither Laravel advisory above and has no record newer than 14 October; it does not cover php-src. endoflife.date still lists PHP 8.5.11/8.4.26/8.3.35/8.2.34 as latest and Laravel 12.70.1 (21 October); Drupal 11.4.11, 11.3.20 and 10.6.20 are dated 21 October (not inspected, not covered). The RFC index (952 entries) lists the same three RFCs as voting.