PHP digest — 27 October 2026
Updated 23:00 UTC. PHPUnit published maintenance releases and a moderate-severity advisory for PHPT code
coverage on shared temporary directories. Laravel 13.39.0 blocks phar:// paths in two Filesystem checks, PHPStan 2.3.3
gets a new regex parser, the ext/csv author postponed the vote planned for 2 November, an openssl_get_channel_binding()
RFC draft would let SASL libraries use TLS channel binding, and Symfony 8.2's Serializer learns generics. There were no
PHP releases, no php.net advisories and no votes opened or closed; the Scope RFC moved from draft to discussion.
PHPUnit 13.4.4/12.5.41: advisory for PHPT coverage in a shared temporary directory
PHPUnit 13.4.4 is the patched version for
GHSA-9vw2-f4vp-x7gf (Moderate,
CVSS v4 5.4, no CVE ID listed), which affects 13.4.0–13.4.3. When PHPT tests run with code coverage, these versions
write the test code to a fixed-name directory such as /tmp/phpunit-phpt and reuse it even if another user created
it. That user can then swap in their own code, which runs as the developer, and the test still passes. The attacker
needs a local account or service on the same machine, a temporary path shared between users (such as a shared /tmp
on Linux) and must create the directory first. macOS and Windows defaults, and single-user containers or CI runners,
are described as not affected. PHPUnit 12.5 and earlier are not affected by this advisory. However, 13.4.4 and
12.5.41 both also stop reusing a shared,
automatically created static analysis cache directory (no separate advisory). An hour later
13.4.5 and
12.5.42 fixed that cache directory being ignored
when the POSIX extension is not loaded. 13.4.4 also fixes process-isolated tests being counted as passed after a
signal interrupted the run. Pest 5.3.4 (11:10 UTC) bumps PHPUnit
to 13.4.5 for the advisory. See the knowledge page.
Laravel 13.39.0
Laravel 13.39.0 (14:06 UTC) is a large maintenance
release. Filesystem::exists() and isFile() now block the phar:// stream wrapper (#62164), with a separate change
that still allows reading files from the running phar (#62174); the release notes do not describe this as a security
fix, and the repository's advisory list has no new entry. Config, route and event cache files are now written
atomically (#62117), RefreshDatabase rolls back all transaction levels after each test (#62194), and
Http::batch() no longer treats retry() and throw() failures as successes (#62120). Other entries add a
session:garbage-collect command, #[Table(key: false)] to disable a model's primary key, a duration on the
JobAttempted event and forceCreate() on BelongsToMany, and fix a previous route leaking into 404 requests under
Octane and pagination counts for grouped union queries. Tags
12.70.2,
11.57.1 and
10.50.4, published at the same time, backport
Laravel Cloud exception reporting; 11.57.1 and 10.50.4 have no release notes and were read from the commit comparison.
No security fixes are listed for any of them.
PHPStan 2.3.3 and Psalm 6.20.2/6.20.3
PHPStan 2.3.3 (14:11 UTC) replaces the Hoa-based parser it
uses to infer preg_match() result shapes with one generated by phplrt, fixing several inferred shapes (assertions,
conditional subpatterns, MARK, patterns with subroutine calls). It also supports PHP 8.2 in the Turbo extension and
stops a bootstrap autoloader's exception from aborting the analysis. See the
knowledge page. Psalm 6.20.2
(11:34 UTC) lists a cut in cold-run memory of about 40% (7.0 to 4.0 GiB, the contributor's figure) when
arrayCache="false", analysis of traits declared inside a namespace and two narrowing/stub fixes.
Psalm 6.20.3 (18:30 UTC) fixes a memory regression of about 600 MiB
introduced in 6.19.2 (nullsafe chain state kept on every node). On the 7.0 line, four pre-releases followed the same
evening; 7.0.0-rc11 reports exceptions that are created but
never thrown or used and adds taint stubs for webmozart/assert, amphp packages and mongodb/mongodb (NoSQL sinks), and
rc14 adds a zstd extension stub. Psalm 7 is not released.
ext/csv vote postponed
The author of the CSV extension RFC had planned to open the vote on 2 November
(see 26 October). After Tim Düsterhus asked them to wait until things calm down following the security
release, the author replied at about 07:11 UTC that they are "happy to
postpone the vote to allow more time for discussion". No new date was given. They defended the Csv namespace by
comparison with Uri and Dom but said they are open to a broader naming convention, and agreed that input from Gina
Peter Banyard, author of the original extension, would be valuable. The RFC page is unchanged (version 1.2, Under
Discussion). See the RFC page.
Draft RFC: openssl_get_channel_binding() for SCRAM-PLUS
Sjoerd Langkemper created the openssl_get_channel_binding() RFC
(version 0.1, Draft, proposed PHP 8.7) and announced it. The function
would return the raw TLS channel binding data of a connected ssl:///tls:// stream, selected with a new
Openssl\ChannelBindingType enum (tls-unique, tls-server-end-point, tls-exporter). It would return null when a type
does not apply, such as tls-unique over TLS 1.3. According to the RFC, PHP has no way to get this data today, so userland
SASL libraries cannot implement the SCRAM-SHA-*-PLUS mechanisms. The implementation is php-src PR #24035, which still takes a string and will be
changed to the enum. The RFC is not yet in the official index, and no vote has been scheduled. See the
RFC page.
Symfony 8.2: generics and stricter types in the Serializer
New in Symfony 8.2: Generics and Stricter Types in the Serializer
describes changes merged into the 8.2 branch. Symfony 8.2 is not released. When denormalizing, the Serializer now resolves
PHPDoc template types from the generic type declared on the property that holds the object (for example
/** @var Page<Product> */); this requires PropertyInfo's PhpStanExtractor and phpstan/phpdoc-parser. Elements of
collections typed with a union, such as list<CardPayment|BankTransfer>, are now denormalized too. The post calls this a
behavior change: an element that matches no union member, or a key that does not match the key type, now throws instead of
being returned as is. Denormalizing a JSON object into a list<...> property triggers a deprecation in 8.2 and is
announced to throw NotNormalizableValueException in 9.0. TypeInfo adds @template-covariant support, Type::map() and
Type::getMismatches(), which reports the path, expected type and actual type of each mismatching value.
Also in discussion
In the "[RFC Idea]" thread asking for a feature and deprecation moratorium until PHP has a formal specification and independent implementations (covered on 25 October), a reply (132939) argues that this would ask the already stretched maintainers of the reference implementation to stop building it. It says that companies with the resources should build such implementations and contribute them. There is no RFC.
The array_partition() RFC (version still 0.1) was edited at 10:31 UTC to address
Tim Düsterhus's review: the behavior is now defined by a userland foreach implementation (the native function differs only
in keeping by-reference elements as references, like array_filter()), and the BC section now says that any existing userland
array_partition() must be checked against the native semantics, with or without a function_exists() guard
(132943). No vote date has been named; see the RFC page.
Later the same day Tim Düsterhus asked for an example of that
reference behavior and questioned behavior that cannot be replicated in userland. The author
replied that the functions returning part of their input keep references
while array_find() and array_map() drop them, added a "By-reference elements" example in a 16:22 UTC edit, and listed
reference handling as an open issue to settle before a vote.
The Scope RFC (version 0.9.3, 11:51 UTC) now reads Under Discussion, as does the
official index, and adds that under vote A session_start() throws a RuntimeException, instead of blocking the process,
when a locking session is already active in another scope; that rule is its open issue. See the RFC page.
In the Uri\QueryParams thread the author
now leans toward keeping an automatic $maxQueryStringLength, notes that
strict parsing would make migrating from $_GET harder, and says sortByBytes()/sortByUtf16() are on the page. See the
RFC page.
In the effect declarations idea thread, a reply (132942) asked why new syntax is needed instead of attributes and whether other languages have comparable effect systems. There is no RFC page.
WordPress 7.2 Beta 2 continues work on the Abilities API and server-side DataViews/DataForm registration; the final release is still scheduled for 8 December.
Coverage
At 05:01, 11:01 and 17:01 UTC fetch --due collected all 32 due feed, release and index sources each time without
failures. The 25 daily sources were not due. health --fail-stale reports 57 sources ok and none stale. New records in the
17:01 UTC run: Laravel framework tags, PHPStan, Psalm and Pest releases, internals messages 132944–132946, RFC page edits
(Scope 0.9.3, array_partition, and link-only edits to reldateformatter and min_supported_versions_php_8_6), WordPress 7.2
Beta 2, a SymfonyCon talk post, two Laravel News articles on third-party tools (not covered) and a phpnews.net article on the
26 October Windows/Brotli builds (already covered on 26 October). The official RFC index has 955 entries;
Scope moved from draft to discussion. Two RFCs are voting. At about 17:10 UTC, number-base exceptions stood at 24–1–0
(closes 1 November 15:30 UTC) and Filter enums at 2–11–0 (closes 4 November), both unchanged since the early edition.
Both are interim counts of open polls, not results. Support dates were unchanged.
At 23:01 UTC all 57 sources (32 due feeds and the 25 daily sources) were collected without failures. New records: Psalm
6.20.3 and 7.0.0-rc11–rc14, and a phpnews.net article on a Cloudflare capture-the-flag challenge for its php2shell WAF
rules (secondary source, vendor programme; not covered). The daily Packagist, security-advisory and support-date
collections added no new advisory beyond PHPUnit's, no support-date change and only small day-over-day changes in the
WordPress PHP version shares. No new internals messages or RFC page edits; both vote counts were unchanged at 23:05 UTC.