Preload by Agence Web Performance

Topic · 5 items

PHP

This page gathers news about PHP and the tools built on it: releases, security fixes, end-of-life dates and changes that affect your code. It's for back-end developers and teams maintaining WordPress, Drupal, Symfony or PrestaShop sites, and Preload tracks the dates you shouldn't miss.

Follow this topic By RSS, in your feed reader

Preload #04 ·

Brotli flaw: WordPress is exposed through the server, not its updates

A flaw in the Brotli compression library affects sites that an up-to-date CMS doesn't protect: CVE-2026-111497, an out-of-bounds write in the decoder, affects versions 1.0.3 to 1.2.0, fixed on October 21 in 1.0.10, 1.1.1 and 1.2.1, and the US agency CISA has listed it as exploited since October 27. WordPress doesn't ship Brotli, but reaches it through PHP's cURL extension whenever it fetches a URL supplied from outside: an unauthenticated pingback to xmlrpc.php, an oEmbed, a feed. A crafted response at least crashes the PHP worker; code execution hasn't been demonstrated through this path.

Next step

Update the system Brotli package (libbrotli1 on Debian and Ubuntu, checking the patched revision for your distribution), rebuild your Docker images and restart PHP-FPM. If you don't use pingbacks, remove pingback.ping with the xmlrpc_methods filter: the xmlrpc_enabled filter doesn't block them.

Read the source

Preload #03 ·

php-rust: PHP rewritten in Rust already runs WordPress, just more slowly

The open source project php-rust reimplements PHP 8.5 in Rust, without reusing the Zend Engine's C code, with memory safety as the goal: Rust rules out use-after-free bugs and buffer overflows by design, two classes of flaws in the C engine. It runs WordPress 7.0.1 on a real MySQL and passes the core PHPUnit suite (30,472 tests single-site, 31,278 multisite), along with Composer, PHPUnit and Symfony's http-kernel; Laravel is next. It's still slower than official PHP: about 1.77 times the CPU on the WordPress suite, and 2.4 to 4.6 times on micro-benchmarks.

Next step

Keep it out of production and watch it as a lead; if you maintain a PHP plugin or library, running its test suite on it will show you where behavior differs.

Faster performance is a goal, not a given; the real value is memory safety, and parity on the WordPress suite is already a serious result.

Read the source

Preload #03 ·

Claude API: the first new version since 2023 breaks existing calls

If your tools call the Claude API, moving to the new SDKs can break your requests: on October 21, Anthropic released API version 2026-10-21, the first since 2023-06-01, and new major SDKs send it by default (Python 2.0, TypeScript 1.0, PHP 1.0, Go 2.0, among others). In this version, temperature, top_p and top_k return a 400 error, even at their default values, and the SDKs send the key in Authorization: Bearer instead of X-Api-Key. No end date has been announced for 2023-06-01.

Next step

Remove temperature, top_p and top_k from your calls, and update your proxy, gateway and log filters for the Authorization header. In PHP, composer update stays within your version constraint: use composer require to get 1.0, then replace MessageParam with the per-role classes, or you'll hit a TypeError.

Check your log filters first: masking set up for X-Api-Key would let the key through in plain text in the new header.

Read the source

Preload #03 ·

PHP2Shell: update PHP itself, not just your CMS

Every PHP site stays exposed until its server runs PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35, released October 21: they fix CVE-2026-109618 and CVE-2026-109619 (“PHP2Shell”), an unauthenticated remote code execution flaw in the engine, scored 9.2 in CVSS 4.0, whatever the application. Found by Wiz Research, OpenAI Codex Security and Calif with the help of AI models, the flaws saw an exploitation attempt spotted by Amazon as early as October 17, before disclosure. A third flaw, CVE-2026-115560, with an unlikely attack vector, will be fixed in the next regular release; PHP 8.1 and older get no new release, only minimal patches published as source.

Next step

Update PHP (updating WordPress, Drupal or PrestaShop fixes nothing, and WordPress.org has no update planned), then restart PHP-FPM, Apache and long-running PHP processes; on shared hosting, ask your host. Set session.upload_progress.enabled=0 in php.ini or the pool config, never with ini_set(). On Plesk, the panel's own PHP needs 18.0.81 Update 4 or 18.0.80 Update 11.

A site still on PHP 8.1 or older can be patched this time, thanks to backports from Ondřej Surý's repository (a fixed PHP 7.4 package on October 21) or from Plesk. That's neither an official nor a lasting solution: nothing guarantees the next fix, so now is the time to plan the migration.

Read the source

Preload #03 ·

Published vulnerabilities nearly doubled in 2026: triage from your inventory

The volume of vulnerabilities to track can no longer be handled by hand: according to the NVD, the US government's vulnerability database, 86,554 CVEs were published in 2026 as of October 26, against 48,151 for all of 2025. On October 21, the day of the PHP2Shell fixes, Node.js 26.12.1, 24.22.1 and 22.23.4 also fixed ten vulnerabilities.

Next step

List the building blocks you actually run in production (PHP, Node.js, web server, hosting panel) and subscribe to those projects' security lists. Prioritize with CISA's KEV catalog (exploited vulnerabilities) and EPSS (likelihood of exploitation) rather than the CVSS score alone.

The bottleneck is no longer discovery, which AI speeds up, but patching: automate updates and shrink your exposed surface.

Read the source

Eroan Boyer
Founder of Agence Web Performance

What comes next, Tuesday morning.

Items on this topic land in Preload every week, two weeks before they go public. Free, one-click unsubscribe.