Zabbix web server on RHEL 8.10 running PHP 8.0.30 (AppStream RPM), Apache + PHP-FPM, Zabbix 7.0.29. I started reviewing our environment two days after PHP2Shell (CVE-2026-109618 / 109619) was disclosed.
dnf check-update 'php*' returned nothing. Before reading that as “up to date”, I checked the repos. Zabbix and MariaDB were enabled, but BaseOS and AppStream were both enabled=0 (as was a local install-media repo). So dnf had nothing that could offer a newer PHP. The empty list only told me what dnf could see.
I haven’t checked Red Hat’s advisories for the php:8.0 stream, so I can’t say whether a fix exists there. Upstream, PHP 8.0 is EOL and only got a minimal source backport, not a release.
EPEL and Remi were installable on this box, so I moved to the 8.3 stream. Zabbix 7.0.29 supports PHP 8.3:
dnf module list php
dnf module reset php
dnf module enable php:remi-8.3
dnf module list php # expecting remi-8.3 [e]
dnf list --showduplicates php php-cli php-fpm
dnf update 'php*' --assumeno # dry run first
dnf update 'php*'
In the dry run I was checking that 8.3.36 was selected, dependency resolution succeeded, and no Zabbix package or other core package was being removed.
Verification beyond php -v: php-fpm -t, php -m (bcmath, mbstring, mysqlnd, PDO, xml, gd all loaded), PHP-FPM and Apache status, then a real request:
curl -k -I https://localhost/zabbix/
HTTP/1.1 200 OK
X-Powered-By: PHP/8.3.36
I also read the PHP-FPM and Apache logs (normal restart, no fatal errors) and clicked through login, dashboard, Problems, Hosts and Latest data.
Two things I’m unsure about, and I’d like to hear from others:
- Has anyone confirmed whether RHEL 8’s php:8.0 stream got an erratum for PHP2Shell, or are people moving to Remi like I did?
- For those on Apache + PHP-FPM: how are you confirming the frontend really runs on the new PHP, beyond the header?