Repository navigation
Critical PHP security release 2026-11-18 #749
jaydrogers
announced in
Announcements
Replies: 7 comments 12 replies
0 replies
Update: New release is issued and we're building 👷♂️PHP has released the fixes. We're starting the build (can take 45-55 minutes -- assuming the first build completes without retrying 😅) Job to monitor: Right now we're just focusing on the build to get started. We will update this thread with what we know about the vulnerability soon. We'll update the release notes too, but expect this is the version you'll need to upgrade to: |
3 replies
|
But what was the security issue? |
3 replies
Update: They're all published 🚀Start patching! 🏎️ |
3 replies
|
Thank you for all your work! It's much appreciated. |
0 replies
|
Howdy, I'm the researcher who found CVE-2026-115560 - you can find more details here |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment





Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Tip
Patched images are live. Update now.
Last updated: (see upper right of this post)
What's being fixed
php.net fixed 17 vulnerabilities today. Seven are rated critical (CVSS 9.2). Most of those can lead to remote code execution.
php.net says every critical issue needs a non-default configuration or an uncommon setup. Our image defaults already block a few of them.
Update anyway. Whether you're exposed depends a lot on your app, and pulling a new image is easier than checking.
The full list is in php.net's changelog.
Am I affected?
Here's what we found when we checked each critical issue against our images:
fpm-nginxorfpm-apachefpmbehind your own proxyfastcgi_keep_conn onin NGINX, orenablereuse=onin Apache. If you have it, update first.frankenphpcliwww-data, so this only reaches root if you run the container as root.Using Laravel? Laravel handles sessions itself and doesn't use PHP's native
session_start(), so the three session bugs mostly don't reach a standard Laravel app. Symfony and plain PHP apps do use native sessions.Our defaults also block two of the critical bugs outright:
PHP_SESSION_UPLOAD_PROGRESS_ENABLED=0) since the October advisory, which blocks CVE-2026-115560zend.exception_ignore_argsis on, which blocks the PHP 8.5 backtrace bug (CVE-2026-129474)If you've changed either of those, update first.
How to update
Find the tag you use below:
8.5-fpm-nginx8.5-fpm-nginx-v5.1.48.5-fpm-nginx-v5.1.58.5.12-fpm-nginx8.5.13-fpm-nginxIf you build your own image
FROM serversideup/php, add--pullso Docker grabs the new base image:Then confirm you're on the patched version (swap
phpfor your service name):docker compose exec php php -vWhich images get the fix
PHP 8.6.0 is scheduled for today too. It's coming in a separate release (v5.2.0).
Thank you
This one went a lot smoother than October. php.net published at 14:08 UTC, our build started at 14:10, and patched images were live about 45 minutes later. That's the payoff from building PHP ourselves since v5.1.0.
Thanks to everyone who followed along and kept this thread helpful. And thank the PHP security team too. Most of them are volunteers, and they put in a lot of extra hours to keep your servers safe.
If you're using these images professionally
Days like today take a lot of work behind the scenes. If you're using these images to make money, sponsoring us on GitHub really helps us keep this going (and gives your business some visibility too).
All reactions