Welcome to Centmin Mod Community
Become a Member

Security PHP 8.5.13, 8.4.28, 8.3.37, 8.2.36 critical security updates & EOL Backports

Discussion in 'Centmin Mod News' started by eva2000, Nov 20, 2026 at 6:28 PM.

  1. eva2000

    eva2000 Administrator Staff Member

    60,551
    12,627
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +19,292
    Local Time:
    12:33 AM
    Nginx 1.31.x
    MariaDB 10.x/11.4+/12.3+
    PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 came out on 19 November 2026. They fix 17 security vulnerabilities, and 7 of them are rated critical with a CVSS v4.0 score of 9.2. php.net says the critical issues need a non-default configuration or an uncommon setup. Several of those setups are common enough on real servers that I'd treat this as an update to do today, not on your next maintenance window.

    This one was a lot of effort this time round as it also coincided with PHP 8.6.0 GA stable release. If you find Centmin Mod and my work useful, please support Centmin Mod ;)

    Centmin Mod can build these releases now. 141.00beta01 builds all four, 140.00beta01 builds all four with PHP 8.4 and 8.5 on EL8 and EL9, and 132.00stable builds 8.3.37 and 8.2.36. Run cmupdate to update your Centmin Mod code before you run centmin.sh menu option 5 to update PHP.

    What this means for Centmin Mod servers


    I checked each advisory's preconditions against Centmin Mod's own defaults and a fresh 141.00beta01 install running PHP 8.5.13.

    • WordPress sites using fastcgi_cache need the update first. CVE-2026-129289 needs persistent FastCGI connections to PHP-FPM. Centmin Mod's default php.conf leaves fastcgi_keep_conn off. WordPress sites created with centmin.sh menu option 22 using the fastcgi_cache option are different. That option only shows up if you set WP_FASTCGI_CACHE='y' in /etc/centminmod/custom_config.inc. Their /usr/local/nginx/conf/wpincludes/yourdomain.com/php-fastcgicache.conf sets fastcgi_keep_conn on; and passes PHP through an nginx upstream with keepalive. That meets the advisory's precondition. The exploit also needs an application path that opens php://input without reading it to the end, and I haven't confirmed whether WordPress or a plugin has one. Today's Centmin Mod update turns fastcgi_keep_conn off for new menu option 22 sites, and for existing ones at the next nginx upgrade through menu option 4 unless you've set NGINX_ALLOWOVERRIDE='n'.
    • Session upload progress is off on most servers. Centmin Mod has written session.upload_progress.enabled = 0 to /etc/centminmod/php.d/a_customphp.ini on PHP installs and menu option 5 upgrades since the October PHP security update. That removes the upload progress path for CVE-2026-115560 and one input path for CVE-2026-126714. Check the value PHP-FPM actually uses with the test page in the "If you can't update right away" section, because a .user.ini file or a pool setting can override it.
    • PHP 8.5's magic method backtrace bug is blocked by default. Centmin Mod installs PHP's production php.ini, which sets zend.exception_ignore_args = 1. The advisory for CVE-2026-129474 says that setting prevents the demonstrated attack.
    • PHP-FPM worker output capture is off. CVE-2026-129291 needs catch_workers_output enabled in a pool. Centmin Mod's pool configs leave it commented out.
    • PHP startup warnings don't reach a PHP error log file by default. CVE-2026-129496 needs a PHP startup warning, such as a bad date.timezone or a deprecated setting, written through PHP's own error_log file. Centmin Mod sets error_log in each PHP-FPM pool, which applies after PHP has started, and leaves it unset in php.ini. If you've set error_log in php.ini or in /etc/centminmod/php.d, or php -v prints any warnings, fix the warnings.
    • php-cgi isn't used. Centmin Mod runs PHP-FPM, so the php-cgi bug CVE-2026-129538 doesn't apply.

    EOL PHP 5.6 and 7.2-8.1 backports are live

    PHP 8.1 and older no longer get updates from the PHP project, and the advisories only list supported branches. Some of these bugs are old, though: the PHP-FPM request smuggling bug dates back to PHP 5.6.0. Backported fixes for PHP 7.2.34, 7.3.33, 7.4.33, 8.0.30 and 8.1.34 are now in Centmin Mod 132.00stable, 140.00beta01 and 141.00beta01, and for PHP 5.6.40 in 132.00stable and 140.00beta01. Run cmupdate and rebuild your PHP version with centmin.sh menu option 5. My EOL backport post in this thread has the details. Centmin Mod has no backport for PHP 7.0 and 7.1, so upgrade those.

    Security vulnerabilities fixed

    Severity ratings and scores are as published on each php-src GitHub security advisory.

    • CVE-2026-129289: Advisory GHSA-qc49-hpvq-g2w6; Severity Critical, 9.2; Description PHP-FPM request smuggling through an unread request body. With persistent FastCGI connections, leftover body bytes can be accepted as a new forged request that runs attacker PHP code; Fixed in 8.5.13, 8.4.28, 8.3.37, 8.2.36
    • CVE-2026-115560: Advisory GHSA-658j-r8rw-q6mx; Severity Critical, 9.2; Description Session upload progress can write data with one session serializer that is later read with another, which can lead to remote code execution; Fixed in 8.5.13, 8.4.28, 8.3.37, 8.2.36
    • CVE-2026-129496: Advisory GHSA-gr4f-wgx5-jpfv; Severity Critical, 9.2; Description Timezone cache use-after-free when a startup warning is written to a PHP error log file; Fixed in 8.5.13, 8.4.28, 8.3.37, 8.2.36
    • CVE-2026-126714: Advisory GHSA-fm2m-fjf5-v3cp; Severity Critical, 9.2; Description An interrupted write can leave a partly overwritten session file that PHP later unserializes; Fixed in 8.5.13, 8.4.28, 8.3.37, 8.2.36
    • CVE-2026-129481: Advisory GHSA-g3vh-838c-65v7; Severity Critical, 9.2; Description Use-after-free after an interrupted session shutdown. PHP 8.2 isn't affected; Fixed in 8.5.13, 8.4.28, 8.3.37
    • CVE-2026-129474: Advisory GHSA-8mjj-2r7p-4hg2; Severity Critical, 9.2; Description Use-after-free in backtraces of __call() and __callStatic() methods; Fixed in 8.5.13
    • CVE-2026-129182: Advisory GHSA-2fjv-p558-g82m; Severity Critical, 9.2; Description Use-after-free of the fatal error backtrace after request shutdown; Fixed in 8.5.13
    • CVE-2026-129291: Advisory GHSA-jm4m-qfqx-967m; Severity High, 8.8; Description PHP-FPM epoll use-after-free. Local privilege escalation to the FPM master when catch_workers_output is on; Fixed in 8.5.13, 8.4.28, 8.3.37, 8.2.36
    • CVE-2026-127960: Advisory GHSA-mmf9-xm3v-hg2x; Severity High, 8.7; Description A malicious HTTP server can tie up PHP workers with folded response headers; Fixed in 8.5.13, 8.4.28, 8.3.37, 8.2.36
    • CVE-2026-128064: Advisory GHSA-f6gg-rchx-xw8j; Severity High, 8.2; Description HTTPS:// and FTPS:// URLs with an uppercase scheme are sent without TLS; Fixed in 8.5.13, 8.4.28, 8.3.37, 8.2.36
    • CVE-2026-128090: Advisory GHSA-68fq-fh7h-f8gr; Severity High, 7.7; Description Phar OpenSSL signature check can be bypassed by switching the signature type; Fixed in 8.5.13, 8.4.28, 8.3.37, 8.2.36
    • CVE-2026-129538: Advisory GHSA-5j3f-64r7-f564; Severity Medium, 6.9; Description php-cgi out-of-bounds read and write during PATH_INFO correction. PHP-FPM isn't affected; Fixed in 8.5.13, 8.4.28, 8.3.37, 8.2.36
    • CVE-2026-129506: Advisory GHSA-4646-p932-gw34; Severity Medium, 6.3; Description SOAP use-after-free when parsing DTD entity references; Fixed in 8.5.13, 8.4.28, 8.3.37, 8.2.36
    • CVE-2026-129501: Advisory GHSA-x8r7-mg3g-74hg; Severity Medium, 6.3; Description Double free in the new DOM API's saveXml(); Fixed in 8.5.13, 8.4.28
    • CVE-2026-15353: Advisory GHSA-q23r-hr55-xmpg; Severity Medium, 6.3; Description SOAP can leak a few bytes of heap memory through a malformed array size; Fixed in 8.5.13, 8.4.28, 8.3.37, 8.2.36
    • CVE-2026-129438: Advisory GHSA-mg3p-mxj9-g2mm; Severity Medium, 6.3; Description Uri\Rfc3986\Uri returns a wrong string for URIs around 2 GiB; Fixed in 8.5.13
    • CVE-2026-129292: Advisory GHSA-3mg3-cr28-46gc; Severity Medium, 5.3; Description Cross-site scripting in the PHP-FPM status page's full HTML output; Fixed in 8.5.13, 8.4.28, 8.3.37, 8.2.36

    If you can't update right away

    These steps come from the advisories. They reduce exposure to specific attack paths but don't fix PHP. Only an update does that.

    • On WordPress sites using fastcgi_cache, comment out fastcgi_keep_conn on; in /usr/local/nginx/conf/wpincludes/yourdomain.com/php-fastcgicache.conf, then run nginx -t and ngxreload. Today's Centmin Mod update makes off the default, so leave it off.
    • Keep session.upload_progress.enabled = 0, and make sure no .user.ini file or PHP-FPM pool setting turns it back on.
    • On PHP 8.5, set fatal_error_backtraces = 0. It blocks CVE-2026-129182 and CVE-2026-129474. Centmin Mod's production php.ini also sets zend.exception_ignore_args = 1, which blocks CVE-2026-129474 on its own.
    • Fix anything that makes php -v print a startup warning.
    • Leave catch_workers_output off in your PHP-FPM pools.

    Put PHP settings in a new file in Centmin Mod's PHP override directory rather than editing php.ini. Don't rely on ini_set(), which applies too late, and check that no .user.ini file or PHP-FPM pool setting turns them back on. Use a new file name for each setting. If you followed my October post, zz-security.ini holds session.upload_progress.enabled = 0, and writing to it with > would remove that line. Then restart PHP-FPM and check both values as PHP-FPM sees them. php -i only shows the command line settings, so use a temporary test page on Centmin Mod's default site:

    Code (Text):
    echo "fatal_error_backtraces = 0" > /etc/centminmod/php.d/zz-fatal-error-backtraces.ini
    fpmrestart
    echo '<?php foreach (["session.upload_progress.enabled", "fatal_error_backtraces"] as $k) { echo $k, " = ", ini_get($k) ? "on" : "off", "\n"; }' > /usr/local/nginx/html/inicheck.php
    curl -s http://localhost/inicheck.php
    rm -f /usr/local/nginx/html/inicheck.php


    Both should show off. Then look for anything that turns upload progress back on, in pool configs, PHP override files or a site's .user.ini:

    Code (Text):
    grep -rn upload_progress /usr/local/etc/php-fpm.conf /usr/local/nginx/conf/phpfpmd/ /etc/centminmod/php.d/
    find /home/nginx/domains -name .user.ini -exec grep -l upload_progress {} +


    PHP releases

    • PHP 8.5.13 is the latest PHP 8.5 release. Supported in Centmin Mod 141.00beta01, and in 140.00beta01 on EL8 and EL9.
    • PHP 8.4.28 is the latest PHP 8.4 release. Supported in Centmin Mod 141.00beta01, and in 140.00beta01 on EL8 and EL9.
    • PHP 8.3.37 is the latest PHP 8.3 release. Supported in Centmin Mod 132.00stable, 140.00beta01 and 141.00beta01.
    • PHP 8.2.36 is the latest PHP 8.2 release. PHP 8.2 security support ends on 31 December 2026.

    Who is affected?

    • PHP 7.0 and 7.1: Vulnerable versions Not listed by the advisories, but they carry the vulnerable code for CVE-2026-126714, which affects every version before 8.2.36; Fix No Centmin Mod backport. Upgrade. Interim settings only reduce exposure
    • PHP 5.6: Vulnerable versions Not listed by the advisories; Fix 5.6.40 rebuilt with today's Centmin Mod update, on 132.00stable or 140.00beta01
    • PHP 7.2 to 8.1: Vulnerable versions Not listed by the advisories; Fix 7.2.34, 7.3.33, 7.4.33, 8.0.30 or 8.1.34 rebuilt with today's Centmin Mod update
    • PHP 8.2: Vulnerable versions Older than 8.2.36; Fix 8.2.36
    • PHP 8.3: Vulnerable versions Older than 8.3.37; Fix 8.3.37
    • PHP 8.4: Vulnerable versions Older than 8.4.28; Fix 8.4.28
    • PHP 8.5: Vulnerable versions Older than 8.5.13; Fix 8.5.13

    PHP changelogs


    Updating PHP on Centmin Mod LEMP stacks

    • If you're on Centmin Mod 130.00beta01 or older, update your server first. 132.00stable supports PHP up to 8.3, and 140.00beta01 adds PHP 8.4 and newer on EL8 and EL9.
    • On Centmin Mod 132.00stable, 140.00beta01 or 141.00beta01, first update to the latest code with the SSH command cmupdate, which does the same as centmin.sh menu option 23 submenu option 2. Then run centmin.sh menu option 5 and enter the PHP version you want.
    • On 141.00beta01, enter 8.5.13, 8.4.28, 8.3.37 or 8.2.36.
    • On 140.00beta01, enter 8.5.13 or 8.4.28 on EL8 and EL9, or 8.3.37 or 8.2.36.
    • On 132.00stable, enter 8.3.37 or 8.2.36.
    • To recompile an EOL version with the backported security fixes, enter 8.1.34, 8.0.30, 7.4.33, 7.3.33 or 7.2.34. PHP 5.6.40 rebuilds work on 132.00stable and 140.00beta01.
    • Today's Centmin Mod update also downloads libmemcached from the Centmin Mod mirror first. During testing, launchpad.net returned 502 errors for the libmemcached download, and the PHP upgrade stopped before restarting PHP-FPM. If you saw libmemcached-1.0.18.tar.gz download failed, run cmupdate and then menu option 5 again.

    Code (Text):
    cmupdate
    centmin


    141.00beta01: if cmupdate couldn't re-apply your local changes

    If you ran cmupdate on 141.00beta01 between 15:20 and 15:43 UTC on 19 November, it may have printed local changes could not be re-applied cleanly. A Centmin Mod default PHP version change in that window clashed with the PHP version your installer wrote into centmin.sh, and left git conflict markers in it. centmin.sh won't start until that's cleared, and later cmupdate runs can't update the code. To fix it:

    Code (Text):
    cd /usr/local/src/centminmod
    git status --short
    git checkout HEAD -- centmin.sh
    cmupdate


    If git status --short lists any other file starting with UU, run git checkout HEAD -- thatfile for it too. Your old local changes stay saved in git stash list. If you use tools/autoupdate.sh, run git stash drop once you've checked them with git stash show -p, so automatic builds can resume.

    Centmin Mod branch PHP version support

    • 132.00stable: PHP 8.3.x max
    • 140.00beta01: PHP 8.4.x, 8.5.x, 8.6.x on EL8 and EL9
    • 141.00beta01: PHP 8.4.x, 8.5.x, 8.6.x on EL8 and EL9 and EL10

    Centmin Mod 141.00beta01, and 140.00beta01 on EL8 and EL9, also support the new PHP 8.6.0 release. Before you move to a newer PHP branch, check that your web applications, such as WordPress, Xenforo or Laravel, support it.

    Security advisory references


    PHP-FPM upgrade issues

    If you have issues with PHP-FPM upgrades via centmin.sh menu option 5, check your PHP upgrade logs for details https://community.centminmod.com/threads/how-to-troubleshoot-php-installs-upgrades.17857/
     
  2. eva2000

    eva2000 Administrator Staff Member

    60,551
    12,627
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +19,292
    Local Time:
    12:33 AM
    Nginx 1.31.x
    MariaDB 10.x/11.4+/12.3+
    EOL PHP 5.6, 7.2-8.1 security backports for the 19 November PHP releases

    Centmin Mod 132.00stable, 140.00beta01 and 141.00beta01 now carry backported fixes for the PHP security advisories of 19 November 2026 for end-of-life PHP 7.2.34, 7.3.33, 7.4.33, 8.0.30 and 8.1.34. 132.00stable and 140.00beta01 also carry them for PHP 5.6.40. Run cmupdate, then use centmin.sh menu option 5 to recompile the PHP version you run, or better, move to a supported PHP 8.2 or newer.

    What's backported

    PHP 7.2, 7.3, 7.4, 8.0 and 8.1 get the fixes for these 12 advisories:

    • CVE-2026-129289: Advisory GHSA-qc49-hpvq-g2w6; Severity Critical, 9.2; Fix PHP-FPM request smuggling through an unread request body
    • CVE-2026-115560: Advisory GHSA-658j-r8rw-q6mx; Severity Critical, 9.2; Fix Session upload progress is now off by default
    • CVE-2026-129496: Advisory GHSA-gr4f-wgx5-jpfv; Severity Critical, 9.2; Fix Timezone cache use-after-free
    • CVE-2026-126714: Advisory GHSA-fm2m-fjf5-v3cp; Severity Critical, 9.2; Fix Partly overwritten session files
    • CVE-2026-129291: Advisory GHSA-jm4m-qfqx-967m; Severity High, 8.8; Fix PHP-FPM epoll use-after-free
    • CVE-2026-127960: Advisory GHSA-mmf9-xm3v-hg2x; Severity High, 8.7; Fix Folded HTTP response header denial of service
    • CVE-2026-128064: Advisory GHSA-f6gg-rchx-xw8j; Severity High, 8.2; Fix Mixed-case HTTPS and FTPS URLs sent without TLS
    • CVE-2026-128090: Advisory GHSA-68fq-fh7h-f8gr; Severity High, 7.7; Fix Phar OpenSSL signature bypass
    • CVE-2026-129538: Advisory GHSA-5j3f-64r7-f564; Severity Medium, 6.9; Fix php-cgi PATH_INFO out-of-bounds read and write
    • CVE-2026-129506: Advisory GHSA-4646-p932-gw34; Severity Medium, 6.3; Fix SOAP use-after-free with DTD entity references
    • CVE-2026-15353: Advisory GHSA-q23r-hr55-xmpg; Severity Medium, 6.3; Fix SOAP heap read through malformed array sizes
    • CVE-2026-129292: Advisory GHSA-3mg3-cr28-46gc; Severity Medium, 5.3; Fix PHP-FPM status page cross-site scripting

    Two of them need a note. The use-after-free path behind CVE-2026-129291 came with PHP 8.1.20, so on 7.2 to 8.0 that fix is hardening. CVE-2026-127960 affects 7.2 and 7.3 only because this update adds folded header support to their HTTP wrapper, and the fix comes with it.

    The same update also brings older fixes carried in these backport bundles. For PHP 7.4, 8.0 and 8.1 that includes CVE-2024-11235, a use-after-free with the ??= operator. PHP 7.2 and 7.3 get a larger set of older fixes they were missing, mostly in the HTTP wrapper's header handling, plus SOAP, Phar and PostgreSQL.

    The other five advisories don't apply to these versions. CVE-2026-129474, CVE-2026-129182 and CVE-2026-129438 are PHP 8.5 only, CVE-2026-129501 starts at PHP 8.4, and CVE-2026-129481 starts at PHP 8.3.

    PHP 5.6.40 gets 11 of the 12. The folded header fix for CVE-2026-127960 doesn't apply, because PHP 5.6's HTTP wrapper never joins folded header lines.

    Behaviour changes

    • Session upload progress is now off by default in the patched EOL builds. Centmin Mod has set session.upload_progress.enabled = 0 since the October update, so servers rebuilt since then see no change. If you turned it back on, read CVE-2026-115560 first.
    • PHP 7.2 and 7.3 now join folded HTTP response header lines, as PHP 7.4 and newer already do.
    • For PHP 7.2 and 7.3, two fixes I ported myself earlier are now replaced by the versions in these backport bundles: CVE-2025-1735 (PostgreSQL escaping) and CVE-2025-14181 (SOAP HTTP, PHP 7.2).

    A fix of my own for PHP 5.6

    The available PHP 5.6 port of the PHP-FPM status page fix (CVE-2026-129292) frees PHP's shared empty string when a status field holds a value that isn't valid UTF-8. A single request for the full HTML or XML status page with such a Basic auth username corrupts the PHP-FPM worker's memory. Centmin Mod only allows its status page from 127.0.0.1. I reproduced it on CentOS 6 and CentOS 7 and fixed it by changing five efree() calls to str_efree(), which releases those strings the safe way, plus a test. Patched builds pass the status page tests with it.

    Testing

    • PHP 8.1.34 and 8.0.30 built through menu option 5 on AlmaLinux 10, and 8.1.34, 8.0.30 and 7.4.33 on AlmaLinux 9, each with all the backported fixes applied and PHP-FPM and nginx running afterwards.
    • PHP 7.2 and 7.3 don't compile on EL9 and EL10, so for them I checked that every code change applies to the 7.2.34 and 7.3.33 source.
    • PHP 5.6.40 built in CentOS 6 and CentOS 7 test containers with the new patches and a reduced set of configure options, and the tests for these fixes passed. That isn't a full menu option 5 build.
    • On 141.00beta01, PHP 5.6 builds still stop partway through patching. That's an existing 141 issue, not new with this update. Use 132.00stable or 140.00beta01 for PHP 5.6.

    Which versions are fixed?

    • PHP 5.6: 5.6.40 rebuilt with today's Centmin Mod update, on 132.00stable or 140.00beta01
    • PHP 7.0 and 7.1: No Centmin Mod backport. Upgrade. Interim settings only reduce exposure
    • PHP 7.2: 7.2.34 rebuilt with today's Centmin Mod update
    • PHP 7.3: 7.3.33 rebuilt with today's Centmin Mod update
    • PHP 7.4: 7.4.33 rebuilt with today's Centmin Mod update
    • PHP 8.0: 8.0.30 rebuilt with today's Centmin Mod update
    • PHP 8.1: 8.1.34 rebuilt with today's Centmin Mod update
    • PHP 8.2 to 8.5: Update to 8.2.36, 8.3.37, 8.4.28 or 8.5.13, see my first post in this thread

    Other changes in today's update

    • WordPress sites created with centmin.sh menu option 22 using the fastcgi_cache option no longer get fastcgi_keep_conn on;. That setting is the precondition for CVE-2026-129289, and in testing it slowed PHP-FPM over TCP by about 45 ms per request. New sites get it commented out. For existing sites, the next nginx upgrade through menu option 4 comments it out in /usr/local/nginx/conf/wpincludes/yourdomain.com/php-fastcgicache.conf and keeps a backup in /usr/local/nginxbackup/fastcgi-keepconn/. A php-fastcgicache.conf that is a symlink is left alone with a message to edit it by hand. To keep the setting, set NGINX_ALLOWOVERRIDE='n' in /etc/centminmod/custom_config.inc, which also stops other nginx default updates.
    • The SSH login and check-for-updates.sh notice for a newer PHP release is now on by default, with short network timeouts so a slow connection doesn't hold up your login. Set DMOTD_PHPCHECK='n' in /etc/centminmod/custom_config.inc to turn it off.
    • The PHP version lookup used by menu option 5 no longer gets stuck with an empty or partial list when GitHub rate-limits it.
    • Menu option 5 now downloads libmemcached from the Centmin Mod mirror first, so a launchpad.net outage no longer stops it with libmemcached-1.0.18.tar.gz download failed.
    • cmupdate now stops with a message when the Centmin Mod code has unresolved git conflicts, instead of reporting it updated. My first post in this thread explains how 141.00beta01 users clear one from 19 November.
    • On 132.00stable, menu option 5 now refuses PHP 8.4 and newer, including 8.6, and points you to 140.00beta01.
    • On 132.00stable, a menu option 5 rebuild of the PHP version you already run could skip every backported fix. Menu option 5 unpacked PHP over the source folder an earlier build of that version left in /svr-setup, so Centmin Mod reported each patch as already applied while the sources were back to unpatched. Menu option 5 and the initial install now remove that folder first, so a rebuild after today's cmupdate applies every backport, including any an earlier rebuild skipped. After rebuilding, grep -c 'patch file already applied$' "$(ls -t /root/centminlogs/*_php_upgrade.log | head -1)" should print 0.

    Updating

    Code (Text):
    cmupdate
    centmin


    Then pick menu option 5 and enter the PHP version you run, for example 8.1.34 or 7.4.33, to rebuild it with the backported fixes.

    References

    • php.net PHP 8.5.13 release announcement PHP: News Archive - 2026
    • Advisories are linked in my first post in this thread.

    PHP-FPM upgrade issues

    If you have issues with PHP-FPM upgrades via centmin.sh menu option 5, check your PHP upgrade logs for details https://community.centminmod.com/threads/how-to-troubleshoot-php-installs-upgrades.17857/