PHP security releases (19 Nov): redeploy PHP sites on Quant Cloud to pick up the patched PHP. What you need to do →
 
 

Security Advisory

PHP November 2026 security releases (memory-safety and session flaws)

PHP 8.4.28, 8.3.37 and 8.2.36, released on 19 November 2026, fix memory-safety and session-handling flaws, some of which can lead to remote code execution. PHP sites built from our PHP starter images before 20 November 2026 need a redeploy to pick up the fixed runtime.

Action needed high CVE-2026-128090 Published 20 November 2026

Affects: PHP 8.4.x before 8.4.28; PHP 8.3.x before 8.3.37; PHP 8.2.x before 8.2.36; PHP 7.4 (no upstream fix)

The vulnerability

On 19 November 2026 the PHP project released security releases 8.5.13, 8.4.28, 8.3.37 and 8.2.36. The fixes include several use-after-free flaws (in core, the timezone cache, DOM serialization and session shutdown) and session-serializer flaws that can lead to remote code execution, a PHAR signature bypass (CVE-2026-128090), a case where HTTPS or FTPS traffic could be sent in plain text, and a denial-of-service issue with folded HTTP headers. There is no evidence of any of them being exploited in the wild at the time of writing.

Some fixes in the release concern PHP-FPM and PHP-CGI. Our PHP starter images run PHP as an Apache module, so those do not apply to them.

Who is affected

How your site runsExposed?
A static site served by QuantNot exposed. There is no PHP runtime in the request path.
A PHP app on Quant Cloud built from our PHP starter images (Apache + PHP, Drupal, Drupal CMS, WordPress, Laravel, Craft CMS, Statamic, Symfony)The PHP runtime is whatever was in the starter image when your environment was last built. Builds from before 20 November 2026 carry an older PHP and are exposed until you redeploy.
A custom Dockerfile starting FROM php: or FROM ghcr.io/quantcdn-templates/app-apache-phpSame: check the PHP version your last build baked in.
PHP 7.4Exposed, and there is no upstream fix for the 7.4 line. Move to a supported PHP version.

What you need to do

  1. Redeploy your application. A redeploy rebuilds your image on the current starter image, which now carries the patched PHP, so no code change is needed for the runtime itself. Updating your CMS from its own dashboard does not update PHP.
  2. To check your own image: docker run --rm <your image> php -v. You want 8.4.28, 8.3.37 or 8.2.36 or later.
  3. If your site still runs PHP 7.4, plan the move to PHP 8.3 or 8.4. PHP 8.2 reaches the end of upstream security support on 31 December 2026.

What Quant has done

We rebuilt our PHP starter images on 20 November 2026 (Melbourne time) on the patched official PHP images, and checked the PHP version on both amd64 and arm64: ghcr.io/quantcdn-templates/app-apache-php:8.4 carries PHP 8.4.28 (digest sha256:03dd77f0d650), :8.3 carries 8.3.37 (digest sha256:ec2be1fb7b23) and :8.2 carries 8.2.36 (digest sha256:4cf3b6311a5e). The Drupal, Drupal CMS, Laravel, Craft CMS, Statamic and Symfony starter images were rebuilt on top of them and run PHP 8.4.28. The WordPress starter image runs PHP 8.3.37 on :latest and :php8.3, 8.2.36 on :php8.2 and 8.4.28 on :php8.4. A redeploy from now on runs the fixed PHP.

If you are not sure which image or PHP version your site runs, contact support and we will check it with you.

← All security advisories