Critical PHP updates
- Thread starter ju5t
- Start date
What are results of these 2 commands on that DA server ?
Code:
dpkg -l | grep -i icu
da build list_removalshere:
Code:
dpkg -l | grep -i icu
ii icu-devtools 67.1-7+deb11u1 amd64 Development utilities for International Components for Unicode
ii libicu-dev:amd64 67.1-7+deb11u1 amd64 Development files for International Components for Unicode
ii libicu67:amd64 67.1-7+deb11u1 amd64 International Components for Unicode
da build list_removals
Legacy Sysbk: is present
da build remove_sysbk
If you want to remove all the suggested programs above, run: da build remove_itemscentos7maniac
New member
- Joined
- Oct 22, 2026
- Messages
- 1
Hosted Power
Verified User
- Joined
- Apr 13, 2018
- Messages
- 11
Heads-up for CustomBuild, @fln: 8.4.27 and 8.5.12 introduced a SimpleXML regression. The GC double-frees the SimpleXMLElement properties table, so code like
json_decode(json_encode($xml), true) on an object in a reference cycle crashes the worker with "zend_mm_heap corrupted" (php-src#24488). PHP's fix is a one-line change in ext/simplexml/simplexml.c, approved but not released yet (php-src#24494). Since CustomBuild already ships patches, it may be worth adding for 8.4/8.5 until the next release. 8.3.36 and older aren't affected.People, I understand it's a long thread, but this has been mentioned many times now. You don't need custom things to get 8.3.36 on CenOS 7 with DirectAdmin. Even though it is legacy, DirectAdmin has been so kind to release patches for those servers too.https://yum.rocketsky.ch/ saved my life (for php 8.3.36)
If anyone has trouble getting PHP to build because some patches failed, be sure to check the custom_versions.txt in the custombuild directory.
In my case there was a PHP 7.4.29 version specification when the patches were for 7.4.33 (the latest available version.)
In my case there was a PHP 7.4.29 version specification when the patches were for 7.4.33 (the latest available version.)
WebMaister
Verified User
- Joined
- Aug 23, 2026
- Messages
- 5
I thought DirectAdmin provided PHP versions as-is (I mean, without the patches that CloudLinux applies).
Will PHP release patches for PHP 5.x? Otherwise, how would the DA team apply patches to PHP 5.x?
zEitEr
Super Moderator
Will PHP release patches for PHP 5.x? Otherwise, how would the DA team apply patches to PHP 5.x?
There is already a patch for PHP 5.6
zEitEr
Super Moderator
Update to DirectAdmin 1.712 183b67368b137bca2765445f19ece9b2dfc53132
Already solved, thank you. CSF countryblock was the reason.
alinajafi
Verified User
- Joined
- Nov 7, 2023
- Messages
- 35
Title: Safely updating PHP 8.2 with CustomBuild: empty configure.php82 and preserving extensions / Supervisor workers
Hello,
I would like to update PHP 8.2 to a patched release following the recent PHP security advisory:
https://www.php.net/archive/2026.php
My server configuration:
Current CLI settings:
Apache proxies /app to ws://127.0.0.1:8080/app using a per-domain custom configuration entered through DirectAdmin.
My main concern:
<span>da build used_configs</span> reports this PHP build configuration:
/usr/local/directadmin/custombuild/configure/php/configure.php82
However, that file is currently empty (0 bytes). I do not know why it became empty. The following custom configuration file does not exist:
/usr/local/directadmin/custombuild/custom/php/configure.php82
I previously added --enable-pcntl manually to the default configure.php82 file and rebuilt PHP. The installed PHP still has pcntl enabled, but the current build configuration no longer contains that flag.
I have backed up the PHP configuration and have not started rebuilding PHP.
Could you please advise on:
Thank you.
Hello,
I would like to update PHP 8.2 to a patched release following the recent PHP security advisory:
https://www.php.net/archive/2026.php
My server configuration:
- OS: AlmaLinux 8.10
- Control panel: DirectAdmin with CustomBuild; exact DirectAdmin version not yet collected
- Web server: Apache is installed, with a custom WebSocket reverse proxy configuration
- Current PHP CLI: 8.2.26, NTS
- PHP binary: /usr/local/php82/bin/php
- /usr/bin/php resolves to /usr/local/php82/bin/php
- Loaded php.ini: /usr/local/php82/lib/php.ini
- Additional INI directory: /usr/local/php82/lib/php.conf.d
- ionCube Loader: 14.0.0
- Zend OPcache: 8.2.26
- CustomBuild also lists PHP 7.4, but I have not yet checked which domains use it.
Current CLI settings:
- disable_functions: empty
- memory_limit: 512M
- max_execution_time: 0
- open_basedir: empty
- opcache.enable_cli: 1
Apache proxies /app to ws://127.0.0.1:8080/app using a per-domain custom configuration entered through DirectAdmin.
My main concern:
<span>da build used_configs</span> reports this PHP build configuration:
/usr/local/directadmin/custombuild/configure/php/configure.php82
However, that file is currently empty (0 bytes). I do not know why it became empty. The following custom configuration file does not exist:
/usr/local/directadmin/custombuild/custom/php/configure.php82
I previously added --enable-pcntl manually to the default configure.php82 file and rebuilt PHP. The installed PHP still has pcntl enabled, but the current build configuration no longer contains that flag.
I have backed up the PHP configuration and have not started rebuilding PHP.
Could you please advise on:
- The supported way to restore the empty default configure.php82 file. Is <span>da build update</span> sufficient?
- The correct way to preserve --enable-pcntl and other custom build options across future updates.
- The recommended command to update only the configured PHP 8.2 branch to at least 8.2.35, without changing the PHP 7.4 installation or domain PHP selections.
- Which existing extensions, particularly ionCube, Redis, and Imagick, may require updating or rebuilding.
- Whether this operation preserves php.ini, additional INI files, Supervisor configuration, and DirectAdmin per-domain Apache customizations, and which relevant services/workers should be restarted afterward.
Thank you.
I've just updated PHP 7.2 
but I noticed that I'm missing the following option:
I've now added this option to:
If i run
will I get a new PHP 7.2 build including the patches I previously used for :CVE-2026-109618 · CVE-2026-109619
???
but I noticed that I'm missing the following option:
Code:
--with-pdo-odbc=unixODBC,/usr \
Code:
/usr/local/directadmin/custombuild/custom/php/configure.php72
Code:
./build php 7.2???
zEitEr
Super Moderator
the patches will be applied every time you rebuild PHP.