PHP digest — 20 October 2026
Advance notice of a PHP security release for two critical vulnerabilities on 21 October, one internals message on how the PEAR archive should be run, the Filter enums vote opening a day after its announced date, the API of Symfony 8.2's new JsonSchema component, Laravel 13.38 with an opt-in middleware against stale replica reads, four Psalm 7.0 release candidates and WordPress 7.2 Beta 1.
Critical PHP security release announced for 21 October
At 20:32 UTC php.net gave advance notice of a security release, also posted to internals by the PHP security team. It is scheduled for Wednesday, 21 October 2026 at 14:00 UTC and addresses two vulnerabilities, both rated critical with CVSS v4.0 9.2. The team says it may release earlier if details become public or exploitation is seen in the wild. The notice names no CVEs, affected branches or fixed versions; those are to be published with the release. Users are asked to prepare to upgrade as soon as it is available. This edition makes no claim about which versions are affected or whether the release replaces the 8.5.12 and 8.4.27 releases expected on 22 October (see the 9 October edition).
PEAR archive: suggestions on integrity and the sunset
At 03:52 UTC Sebastian Bergmann posted suggestions for the static pear.php.net
archive that the End PEAR Project Endorsement RFC proposes. The RFC
leaves its technical details to the infrastructure team. The message notes that the RFC's results have not been
officially announced. It points out that until 2027-12-31 the archive would keep serving executable code from
php.net, including go-pear.phar, which was replaced with a malicious copy in January 2019. The suggestions are:
- publish a signed SHA-256 manifest of every file the archive serves, with a copy in the archive's Git repository;
- check the
install-pear-nozlib.pharthat php-src downloads against a pinned SHA-256 hash in every branch that still supports--with-pear, and plan for branches supported after 2027-12-31; - announce short brown-outs of the CLI endpoints and
go-pear.pharbefore the cut-off, and afterwards replacego-pear.pharwith a PHAR that explains the shutdown and exits non-zero instead of returning 404; - publish aggregate request counts per path and user agent, without IP addresses.
This run checked pear/Makefile.frag on php-src
master: when the PHAR is not in the source or build tree, make install-pear downloads it from
https://pear.php.net/install-pear-nozlib.phar (with wget, fetch or a bundled PHP script) and then runs it, with no
hash check in that file. Other branches were not checked. These are proposals on the list, not decisions; nobody had
replied by this run. See the RFC page.
Filter enums RFC vote opens
At 08:54 UTC the author opened the vote on the
Add Filter\Filter and Filter\Flag Enums RFC, one day after the
date given in the 19 October intent-to-vote message (at 04:05 UTC the page still
said Under Discussion). The RFC proposes int-backed Filter\Filter and Filter\Flag enums that filter_var(),
filter_var_array(), filter_input() and filter_input_array() would accept alongside the existing FILTER_*
constants, for PHP 8.7. There is one question, which needs a 2/3 majority, and the page says voting ends on
2026-11-04 at 00:00 UTC. At about 10:05 UTC five people had voted: 1 Yes, 4 No, 0 Abstain; at about 16:05 UTC seven had
voted: 1 Yes, 6 No, 0 Abstain; at about 22:05 UTC nine had voted: 1 Yes, 8 No, 0 Abstain. That is an interim count of an open poll, not a result. The flag-combination design objected to on 9 October (flags combined through their
->value backing integers) is unchanged in the page text. See the RFC page.
Symfony 8.2: JsonSchema component API
A Symfony blog post describes the JsonSchema component first noted in the 18 October edition. It generates JSON Schema from TypeInfo types, and the post says its engine comes from API Platform's json-schema package without the API Platform-specific parts. According to the post:
SchemaGenerator::create()->generate(Type::object(Book::class))reads properties through PropertyInfo, so the schema follows serializer metadata (groups, name converter, discriminator maps) and validation constraints; in the example#[Assert\NotBlank]becomesminLength: 1, and a promoted property without a default is required. The default output is JSON Schema draft 2020-12.- A
Configurationselects a dialect (OpenAPI 3.1 or 3.0 instead of JSON Schema 2020-12), serialization groups and a direction (Direction::InputorDirection::Output). Passing the sameSchemaDocumentto everygenerate()call lets schemas share definitions in one OpenAPI document. generateForParameters()describes a method's parameters, for example the input of an AI-agent (MCP) tool, using types, defaults,@paramdescriptions (which needphpstan/phpdoc-parser) and a new#[JsonSchemaConstraint]attribute;flatten()inlines$refdefinitions into one self-contained schema, andallowExtraAttributes: falserejects unknown properties.- In applications,
composer require symfony/json-schemamakesSchemaGeneratorInterfaceinjectable with no configuration; with the Serializer and Validator enabled it follows their mapping and the serializer'sdatetime_formatanduid_normalization_formatdefaults. - The component requires PHP 8.2 and works with the Symfony 7.4 components.
The post does not mention experimental status; the 18 October edition found the component marked experimental in its 8.2 changelog, which this run did not re-check. Symfony 8.2 is not yet released.
Laravel 13.38: opt-in PreventStaleDatabaseReads
Laravel v13.38.0 was tagged on 20 October at 10:47 UTC.
Its one new middleware, PreventStaleDatabaseReads (#62078), is for
applications with separate read and write database connections. In the v13.38.0 source, after a request that modified
records it stores a timestamp in the session (_database_modified_at); for the next 2 seconds by default
(PreventStaleDatabaseReads::for($seconds) changes this) that session's reads use the write connection. It must be
added to a middleware group or route. The PR description lists its limits: it covers only the user's own writes, only
the default connection, and depends on the session, so it suits stateless APIs poorly.
Other entries in the release include usingWritePdo on Connection (#62099), CountCrashesAsExceptions support for
queued listeners, mailables and notifications (#62048), and releasing the unique lock when dispatching a scheduled job
fails (#62083). Fixes cover whereBetween()/whereNotBetween() with collection bounds (#62062), mode() truncating
floats (#62063), lazy()/lazyById() freeing the previous chunk (#62086), SQLite table alterations with a foreign key
to a table name that needs quoting (#62084) and a TypeError in date comparison rules on non-date values (#62103).
Only the middleware's source was read; the other entries are summarised from their titles.
Psalm 7.0.0-rc3 to rc6 and 6.20.1
Psalm published 7.0.0-rc3, rc4, rc5 and rc6 on 20 October, together with 6.20.1. rc3 collects the changes since rc2 (9 October). According to its notes:
- a PHP 8.6 call map (#12407) and permission to run Psalm on PHP 8.6 (#12323);
- a configuration list of issues that cannot be suppressed by
@psalm-suppress, issue handlers, the error level or the baseline (#12130; the PR description calls the section<unsuppressibleIssues>, and this run's text extraction of the release notes dropped the exact names, so check the 7.0 documentation); - many taint-analysis additions, including custom taints declared in
psalm.xml(#12330), more@psalm-flowforms and lower memory use for taint resolution (20.5 GB to 3.1 GB on Psalm's own code, #12393); - a
timecapability for code that reads the clock (#12261) andCapabilities::allowsrenamed toallowsAnyOf(#12328).
rc4 fixes reading WordPress hash notation after a @return or @var type and requires psalm/psalm-plugin-api 0.4.1;
rc5 adds global constant wildcards in types. rc6 (17:10 UTC) adds decimal-int-string and non-decimal-int-string
types (#12417), conditional types on a type that depends on a template (#12420) and exact intersections of scalar and
conditional types (#12418), plus a fix for virtual-call overrides (#12427). 6.20.1 is a 6.x bug-fix release, among others keeping the config unchanged
when --set-baseline runs with --use-baseline and no longer reporting PropertyNotSetInConstructor for virtual hooked
properties. The notes of both lines include a CI change to "release master and 6.x every hour when all their checks
passed" (#12422/#12423), consistent with three release candidates within about an hour; a new tag therefore need not
mean a large change. No 7.0.0 final date is given.
WordPress 7.2 Beta 1
WordPress 7.2 Beta 1 was published at 16:02 UTC for testing only; the final release is scheduled for 8 December 2026. For developers, the announcement lists a new Secrets API for storing credentials such as API keys (it describes encryption at rest, rotation and pluggable storage providers; Trac #66187), Abilities API additions for querying WordPress data, Interactivity API additions for rendering trusted HTML and reactive navigation, and HTML API improvements. Editor changes include wider responsive controls, text shadows, and client-side image resizing and conversion in the Media Library. These are the announcement's descriptions of a beta; the tickets were not read and details may change before release.
Coverage
At 22:01 UTC all 57 feed, release, index, package, adoption, support-window and advisory sources were collected
successfully (the due feed sources were also collected at 04:01, 10:01 and 16:01 UTC). health --fail-stale reports all 57 sources ok and none stale. New collected records
since the 19 October edition are internals messages 132881 and 132882, the RFC-wiki change to
invalid_filter_options, the Symfony JsonSchema post, Laravel v13.38.0 and Psalm 7.0.0-rc3/rc4/rc5 and 6.20.1, and,
between 16:01 and 22:01 UTC, the php.net and internals security-release notice (132883), Psalm 7.0.0-rc6 and WordPress
7.2 Beta 1, all covered above, plus a SymfonyCon Warsaw talk announcement (not covered). No RFC-wiki change arrived after
08:55 UTC, the daily advisory collection added no new records, and the daily support-window data changed only Laravel's
latest release (13.38.0). The official RFC index still has 952
entries and now lists four RFCs as voting: Filter enums, IntlRelativeDateTimeFormatter, invalid number-base input and
End PEAR, whose poll closed 40–0–0 on 19 October; its page header still said Voting when re-checked at about 16:05 UTC, with no result announced.