Connect a repo or start from a template — we build, deploy, and route it with SSL.
Docs, an API, and a CLI — wired to the same platform your services run on.
PHP October and November 2026 Security Releases: What to Upgrade
PHP shipped two rounds of security releases in four weeks. On October 21, 2026, it fixed two critical bugs that let an unauthenticated request run code on a PHP server. On November 19 it fixed 17 more, seven of them rated critical. Upgrade to 8.5.13, 8.4.28, 8.3.37 or 8.2.36. These include both rounds.
The October 21 releases (8.5.12, 8.4.27, 8.3.36 and 8.2.35) fix CVE-2026-109618 and CVE-2026-109619. Both are rated critical, CVSS 4.0 score 9.2. php.net says they affect "all PHP installations serving web requests, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed."
php.net considers the risk highest for mod_php, "with a demonstrated exploit where an unauthenticated request can trigger the attack before any application code runs." It lists configuration changes that reduce the risk but says they "do not make an installation safe". The only complete fix is to update.
The November 19 releases fix 17 issues with published advisories: seven critical, four high and six moderate. php.net says the critical ones "require either non-default configuration or uncommon setups." For example:
php://input without reading all of it.error_log.The four high-rated issues cover PHP-FPM worker privilege escalation, a Phar signature check bypass, uppercase HTTPS:// and FTPS:// URLs that can send data in plain text, and folded HTTP response headers. The advisories list each issue's conditions. Even if none of them match your setup, the upgrade is the same.
These include the October fixes. PHP 8.6.0, released the same day, includes them too. In October's words, "PHP 8.1 and older no longer receive updates from the PHP project." If you're on 8.1 or older, move to a supported branch.
Run php -v in the container image you actually deploy, or check the tag or digest in your Dockerfile's FROM line. Anything below the versions above is missing some of these fixes.
PHP services run from your own Dockerfile or prebuilt image, so the PHP version is whatever your base image contains. Rebuild on a current official base image (php:8.5, php:8.4, php:8.3 or php:8.2, in the variant you use) so you get 8.5.13, 8.4.28, 8.3.37 or 8.2.36 or later. If you pin a patch version or digest, move it up first. With auto-deploy on, the push builds a new image and redeploys your service. If auto-deploy is paused, as it is after a rollback, choose Resume auto-deploy on the service first, or start a build by hand (deploy actions).
After the deploy, run php -v again to confirm the version.
Last checked November 19, 2026.
Fixed price per spherelet, flat plan per team — ship without DevOps or surprise bills.
Start free trial14-day free trial
Predictable per-spherelet pricing, a flat plan per team, and managed primitives built in — no DevOps, no surprise bills.
Browse Some Related Blogs
Connect a repo or start from a template — live URL, SSL, and zero DevOps, on predictable monthly pricing. 14-day free trial.