There is not a lot of clear information about CVE-2026-109618 and CVE-2026-109619, they appear to affect most (all?) PHP versions from v5 to v8.

AlmaLinux is probably affected? Based on the exploit video, it shows running on mod_php and not php-fpm, I am not sure if that makes a difference.

Hello community. So, I just started studying for RHCSA and it results RHEL10 is not compatible with my PC due to x86_64-v2 deprecation (got to this conclusion after expending 2 days trying to install it in Vmware and Virtualbox and crashing every time after grub), and a little search tells me AlmaLinux extended v2 compatibility for another 10 years. Can I use it instead of RHEL?

I had a script running every hour to look for updates to PHP and they just appeared

php-cli.x86_64 8.0.30-8.el9_8.alma.1 appstream
php-common.x86_64 8.0.30-8.el9_8.alma.1 appstream
php-fpm.x86_64 8.0.30-8.el9_8.alma.1 appstream
php-intl.x86_64 8.0.30-8.el9_8.alma.1 appstream
php-mbstring.x86_64 8.0.30-8.el9_8.alma.1 appstream
php-pdo.x86_64 8.0.30-8.el9_8.alma.1 appstream
php-pgsql.x86_64 8.0.30-8.el9_8.alma.1 appstream
php-process.x86_64 8.0.30-8.el9_8.alma.1 appstream
php-xml.x86_64 8.0.30-8.el9_8.alma.1 appstream

I have been applying a fix for the recently reported 8 compromised certificates and figured I'd share the script I'm using.

Designed for RH and clones, I'll share it as a text file you can review before you rename and apply. It's a simple script based directly on the disclosure page linked to that I found after the original article here on reddit.

I hope it helps, here is distrust.sh - downloaded as a .txt file you can read/review before renaming to distrust.sh and running it as /bin/bash distrust.sh. If your system isn't vulnerable it does nothing.