PHP pre-announced a CRITICAL-rated security release for 19 November, 14:00–14:30 UTC — the first regular-cycle update since October's emergency PHP2Shell patches (CVE-2026-109618/109619, CVSS 9.2, pre-auth RCE, KEV-listed). One flaw was known ahead of the window: CVE-2026-115560, a session-related RCE.
It shipped at 14:05 UTC: 8.5.13, 8.4.28, 8.3.37 and 8.2.36 — 18, 14, 13 and 12 CVEs respectively per the php.net changelog. Four of them are remote code execution:
Worth noting: 8.2 leaves security support on 31 December 2026 — six weeks out. If you are still on it, this is the ride-up release; plan the 8.3 jump now.
The interpreters were public at 14:05. The application images most people actually run were not. Three hours later: nextcloud:35-apache still on the pre-release interpreter, invoiceninja:5 still on PHP 8.5.12, mailcow's phpfpm image still 8.2.35. That is not negligence — it is the app-repo → Dockerfile-bump → CI → registry chain, and it routinely costs hours to days after every PHP release. If your exposure is "PHP inside an application image", the CVE is public knowledge while your fix does not exist yet.
So we closed the gap: four fixed PHP base images plus three application images rebuilt on them. Everything pinned, sha256- and GPG-verified in the build, reproducible from a public repository:
Build repo (Dockerfiles + CI): github.com/tobias-weiss-ai-xr/php-fixed-images
Images — two public registries, anonymous pull:
| Image | ghcr.io/tobias-weiss-ai-xr/php-fixed-images/… | registry.openedusuite.org/php-fixed/… |
|---|---|---|
| PHP 8.5.13 FPM (Alpine 3.24) | php:8.5.13-fpm-alpine3.24 | php-fixed/php:8.5.13-fpm-alpine3.24 |
| PHP 8.2.36 FPM (Alpine 3.24) | php:8.2.36-fpm-alpine3.24 | php-fixed/php:8.2.36-fpm-alpine3.24 |
| PHP 8.5.13 Apache (Trixie) | php:8.5.13-apache-trixie | php-fixed/php:8.5.13-apache-trixie |
| PHP 8.5.13 Apache (Bookworm) | php:8.5.13-apache-bookworm | php-fixed/php:8.5.13-apache-bookworm |
| Nextcloud 35.0.3 | nextcloud:35.0.3-apache-php8.5.13 | php-fixed/nextcloud:35.0.3-apache-php8.5.13 |
| Mailcow PHP-FPM | mailcow-phpfpm:8.2.36 | php-fixed/mailcow-phpfpm:8.2.36 |
| Invoice Ninja 5 | invoiceninja:5-php8.5.13 | php-fixed/invoiceninja:5-php8.5.13 |
docker pull ghcr.io/tobias-weiss-ai-xr/php-fixed-images/php:8.5.13-fpm-alpine3.24
docker pull registry.openedusuite.org/php-fixed/mailcow-phpfpm:8.2.36
The GitHub Actions workflow in the build repo rebuilds the whole set from pinned upstream sources and pushes to both registries on every run. Swap it into your pipeline and the next PHP release costs a workflow dispatch instead of a multi-day wait.
Our own infrastructure was patched and verified the same day — running interpreters checked, not just image tags:
One subtlety worth knowing if you rebuild the mailcow image yourself: Alpine 3.24's apk del sweeps transitive runtime dependencies that Alpine 3.21 kept, which silently removed libwebp.so.7 from under PHP's gd extension. The fix is one line — request libwebp explicitly alongside libwebp-dev — and it is in the repo.
PHP2Shell in October forced shops to build patch pipelines. This release is the first scheduled test of them. The interpreters shipped on the minute; the containers took the rest of the afternoon. Until upstream application images close that gap, owning a rebuild pipeline for the images you actually run is the difference between "CVE published" and "CVE fixed" — and it is roughly thirty minutes of work per release.
The next cycle lands in four weeks. Our pipeline is ready.