PHP scheduled critical security release CVE-2026-115560
-
Hello Cloudron Community
We are aware of the upcoming PHP security release today and will act accordingly.
First we will triage the security update to evaluate the risk factor in a Cloudron environment.
CVEs may only apply partially to Cloudron or do not apply at all, due to the design of Cloudron with isolated containers and the read-only nature of every Cloudron app.If you have question, helpful insights or anything else related to this topic, please reply in this topic.
As soon as we have more details, we will post updates here.~Cheers
The Cloudron Team -
TL;DR
The Cloudron box (system) is not affected.
Most critical issues need settings that Cloudron does not use.
Some issues depend on the app code, not on Cloudron.
All PHP app packages will get a rebuild on the fixed versions, whatever their score below.
Details
PHP published the fixed releases 8.5.13 - ChangeLog).
17 advisories: 7 critical, 4 high, 6 medium (php-src advisories).What we found so far
- Cloudron itself (box) is not affected. The platform code is Node.js and does not run PHP.
- PHP apps are running affected PHP versions.
cloudron/php-basecurrently ships PHP 8.5.12 and 8.4.27. All PHP app packages will get a rebuild on the fixed versions, whatever their score below. - Most critical issues need settings that Cloudron does not use. For example:
- FPM request smuggling (GHSA-qc49-hpvq-g2w6) needs FastCGI keep-alive connections. Our packages do not enable them.
- The
__callbacktrace RCE (GHSA-8mjj-2r7p-4hg2) needszend.exception_ignore_args=0. Our images shipOn. - The FPM root escalation (GHSA-jm4m-qfqx-967m) needs
catch_workers_output=yes. No package sets it.
- Some issues depend on the app code, not on Cloudron. These are the session issues (CVE-2026-115560, CVE-2026-126714, CVE-2026-129481) and the outbound HTTP issues (CVE-2026-128064, CVE-2026-127960). We are checking these per app.
What we are checking per app
We are starting with the most used PHP apps (WordPress, Nextcloud and others) and checking:
- FPM or Apache mod_php, and whether FastCGI connections are reused
- Session handler (files or Redis), serializer, and whether the app changes either at runtime
php.ini/.user.ini/.htaccessoverrides (exception_ignore_args,error_log,zlib.output_compression,PHP_VALUE)- Whether outbound requests use PHP stream wrappers or curl
- Use of Phar, SOAP and DOM XML serialization
How we score the risk for Cloudron (0.0 to 10.0)
Cloudron score = upstream severity × reachabilityUpstream severity: the CVSS score where upstream publishes one. Otherwise we map the rating: critical 9.0, high 7.5, medium 5.0.
Reachability on Cloudron:
Factor Meaning 1.0 Reachable with the default Cloudron package and default app settings 0.6 Reachable only if the app code does a specific thing (to be confirmed per app) 0.3 Needs a setting that the package does not set but an admin could add 0.1 A required precondition is absent from the Cloudron image We do not lower the score for container isolation. A compromised app container still exposes that app's data, which is what matters to you.
Preliminary platform scores (before per-app review)
Advisory Upstream Reachability Score Outbound HTTP plaintext / header DoS (CVE-2026-128064, CVE-2026-127960) high 0.6 4.5 Session issues (CVE-2026-115560, CVE-2026-126714, CVE-2026-129481) critical 0.3 2.7 FPM smuggling, __callRCE, timezone UAF, backtrace UAFcritical 0.1 0.9 FPM root escalation, Phar signature bypass high 0.1 0.75 These scores are preliminary.
-
TL;DR
The only higher risk factor is the LAMP app when you are running custom applications.
Everything else is minimal.Details
We reviewed the package config and the app source of the most used PHP apps.
Scores use the method from the previous post (upstream severity × reachability).App Score Main reason LAMP 5.4 Your own code and /app/data/php.inidecide. PHP 8.1 is end of life and gets no fix.WordPress 2.7 Core does not use PHP sessions and fetches URLs with curl. Plugins that call session_start()orfile_get_contents()on URLs can be affected.Nextcloud 2.7 Uses PHP file sessions (torn session files, CVE-2026-126714). The session payload is encrypted, which limits what an attacker controls. FreshRSS 2.7 Uses PHP file sessions. Feeds are fetched with curl. Moodle 1.5 Sessions are in Redis. SOAP issue applies only if you enabled the SOAP webservice. Matomo, MediaWiki, Roundcube, SnappyMail, Firefly III 0.9 Required preconditions are absent BookStack, Invoice Ninja, Mautic 0.9 Config reviewed, source review pending LimeSurvey, Shaarli, 2FAuth, Lychee, Pixelfed, OpnForm 0.9 These use PHP-FPM. FastCGI connections are not reused (no request smuggling) and worker output capture is off (no root escalation). Source review pending. All other PHP apps use Apache mod_php, where the PHP-FPM issues do not apply.
Package updates with the fixed PHP versions follow.
Updating the app is the fix, whatever the score. -
-
-
New PHP base images are built now. Updates to the packages will arrive in the coming days.
cloudron/php-base:8.5-20261119@sha256:bd7b80d95a0aae4719f3f0fc731d891d1d645792904d3744ee88a3fdea5cefab
cloudron/php-base:8.4-20261119@sha256:56ead2c7c2936f79b8b33e6bb0e9ef2451b1a4ac8d594741dfd0cee5808a20f8
-
-
-
P Package Updates referenced this topic
-
P Package Updates referenced this topic
-
P Package Updates referenced this topic
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login