# PHP's security release, patched the same evening

PHP fixed every supported version on 19 November 2026. How the patched PHP reached Brewless's images and applications within hours, and what you do yourself.

## In short

- On 19 November 2026 PHP released 8.5.13, 8.4.28, 8.3.37 and 8.2.36, a security release for every supported version, among its fixes a remote code execution flaw in session upload progress (CVE-2026-115560).
- A PHP release reaches a container only after a new base image is built on it, so for a FrankenPHP application the clock starts when FrankenPHP publishes its images, not when php.net does.
- FrankenPHP published its patched images about three hours after PHP's release window; Brewless's own images were rebuilt on them in three minutes, and Brewless itself ran the patched PHP within the hour.
- The base image refuses to build on a PHP older than the patched release, so a patched image cannot quietly be replaced by an older one.
- A deploy after new base images builds your application again, even of a commit that was deployed before; your Composer and npm packages stay yours to update.

On 19 November 2026 PHP published a security release for every version it still supports. The advisory had gone out the day before, so nobody was surprised by it, but a release like this is still a race. The fixes are public, and anyone can read in them what was broken.

This is how that afternoon went for the Laravel applications on Brewless, with the times as they happened, and what of it is ours to do and what is yours.

## Which PHP versions does the 19 November release fix?

PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36, released between 15:00 and 15:30 Amsterdam time. Every supported branch got a patch. Among the fixes is CVE-2026-115560, a remote code execution flaw in the way PHP handles session upload progress.

| Branch | Fixed in | Security support until |
| --- | --- | --- |
| 8.5 | 8.5.13 | 31 December 2029 |
| 8.4 | 8.4.28 | 31 December 2028 |
| 8.3 | 8.3.37 | 31 December 2027 |
| 8.2 | 8.2.36 | 31 December 2026 |

Brewless builds for 8.3, 8.4 and 8.5. An application on 8.2 elsewhere gets this fix and very few after it.

> [!NOTE]
> Brewless's images have had `session.upload_progress.enabled` off since October 2026, as a mitigation for an earlier PHP flaw. That closes the published path of CVE-2026-115560, but not the other fixes in this release. The patched PHP is the real fix.

## When does a PHP release actually reach your container?

When a base image is built on it, not when php.net publishes it. A Laravel application on Brewless runs on FrankenPHP, from Brewless's public base image, which is built on FrankenPHP's own images. So the chain has three links, and each one waits for the one before.

| Amsterdam time | What happened |
| --- | --- |
| 15:00–15:30 | PHP releases 8.5.13, 8.4.28, 8.3.37 and 8.2.36 |
| 16:23 | The official `php` images on Docker Hub carry 8.4.28 |
| 18:11 | FrankenPHP's images carry 8.4.28 (and 8.3.37 and 8.5.13) |
| 18:14 | Brewless starts rebuilding its base and builder images |
| 18:17 | All six images, for 8.3, 8.4 and 8.5, are published |
| 18:59 | Brewless itself runs PHP 8.4.28 in production |
| 19:12–19:35 | The applications we run ourselves are redeployed on the patched images |

The three hours between PHP and FrankenPHP is not something to engineer away. Building PHP ourselves would get there sooner, and leave us with a PHP build nobody else runs. We would rather be three hours behind a build that thousands of others use and test.

## What makes sure the patched image is the one that runs?

Two things. The first is in the image itself: the build refuses a PHP older than the patched release. If an upstream tag were ever moved back, or a cache handed us yesterday's layer, the build would stop instead of publishing it.

```dockerfile Dockerfile
# Refuse a PHP without the fixes of the 19 November 2026 security release
RUN php -r '$min = ["8.3" => "8.3.37", "8.4" => "8.4.28"][PHP_MAJOR_VERSION.".".PHP_MINOR_VERSION] ?? "8.5.13"; if (version_compare(PHP_VERSION, $min, "<")) { fwrite(STDERR, "PHP ".PHP_VERSION." is older than ".$min.PHP_EOL); exit(1); }'
```

The second is how a build picks its base. Brewless takes its own images by digest, not by tag: a tag can be moved, a digest cannot. A new image is used once Brewless knows its digest, and not a moment before. That is also why Brewless itself had to go first. It deploys itself, so the release that knows the new digests has to be live before anything is built on them.

## Why did redeploying the same commit need a fix?

Because the first redeploy built nothing. An application's image was tagged with its commit, so a deploy of a commit that was already built found the image and used it again, on the old base. That is exactly right on an ordinary day and exactly wrong on this one.

The tag now also carries a short mark of the base image it was built on. The same commit on another base image is another image, so a deploy after new base images builds again. The fix went out the same evening, before the applications were redeployed. The [deployments documentation](https://docs.brewless.eu/deployments/deployments) describes it.

## What do you have to do yourself?

Deploy once, if you have not deployed since 19:00 Amsterdam time on 19 November 2026. A deploy builds on the patched images, even of the commit that is live now, and runs your release commands like any other. The applications we run ourselves were redeployed that way on the commit they were already running, and checked afterwards with `php artisan about`.

What stays yours is everything in your repository:

```bash
composer audit
npm audit
```

Brewless keeps PHP, FrankenPHP and the image underneath them up to date. Your Composer and npm packages, and your own code, are not in that image until you put them there. A pipeline that runs both audits catches the other half.

> [!TIP]
> Want to see which PHP your environment runs? `brewless command production "about --only=environment"` prints it, read from a container of the live release.

This round was done by hand, from the first look at Docker Hub to the last redeploy. The next one should not need a person watching Docker Hub at all, and that is what we are building now.

## Frequently asked questions

### Which PHP versions fix the 19 November 2026 security release?

PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36, all released on 19 November 2026. PHP 8.2 reaches the end of its security support on 31 December 2026, so on 8.2 this is one of the last fixes you get.

### Is my Laravel application on Brewless patched?

Brewless rebuilt its base images on PHP 8.5.13, 8.4.28 and 8.3.37 the same evening, and every deploy since 19:00 Amsterdam time on 19 November 2026 builds on them. If the live release of an environment is older than that, deploy it once; the same commit builds again on the patched images. php artisan about shows which PHP it runs.

### What does Brewless patch and what do I patch?

Brewless keeps PHP, FrankenPHP and the image underneath them up to date, in the public base image every application is built on. The Composer and npm packages in your repository, and your own code, are yours. Run composer audit and npm audit in your pipeline.

### Why did the patched PHP take hours to arrive, not minutes?

Because PHP itself is only the start. The official php images followed about an hour after the release, and FrankenPHP, which Brewless builds on, published its images about three hours after it. Building on PHP before those images exist would mean building PHP ourselves, outside the images thousands of others use and test.

### Does turning session upload progress off protect against CVE-2026-115560?

It closes the published attack path of that one flaw, and Brewless's images have had session.upload_progress.enabled off since October 2026. It does nothing for the other fixes in the release, so the patched PHP is still the real fix.

Source: https://brewless.eu/blog/php-security-release-patched-same-evening
