I'm running a web server with Debian 13 (Trixie), Apache 2.4.71 and PHP 8.3 using mod_php. The PHP packages come from the Sury repository and are automatically updated through unattended-upgrades.
I first noticed during the PHP2Shell security updates that Apache was not automatically restarted after the PHP updates had been installed. Last night, unattended-upgrades once again installed several updates for libapache2-mod-php8.3 and other PHP extensions, but Apache was not restarted afterward.
For example, at around 06:14 this morning, several PHP 8.3 packages were updated, including libapache2-mod-php8.3 and php8.3-opcache. However, the Apache main process was still running since the previous evening, when I had manually installed the first round of updates and restarted Apache myself:
ExecMainStartTimestamp=Thu 2026-11-19 22:18:18 CET
ActiveEnterTimestamp=Thu 2026-11-19 22:18:18 CET
After doing some research, I found that this is a known issue and was supposedly fixed in Apache 2.4.65-3 back in August 2025:
Debian bug report #1060450:
https://bugs.debian.org/1060450
However, the problem apparently still exists in Debian 13. A new bug report was filed in October 2026:
https://bugs.debian.org/1151638
The cause seems to be in the apache2_needs_action() function in /usr/share/apache2/apache2-maintscript-helper, which handles the configure method but not triggered.
I checked the installed script on my server, which is running Apache package version 2.4.71-1~deb13u1. The relevant section still looks like this:
postinst)
if [ "$APACHE2_MAINTSCRIPT_METHOD" = "configure" ] ; then
# act on fresh installs
[ -z "$APACHE2_MAINTSCRIPT_ARGUMENT" ] && return 0
# act if someone told us
[ -n "$APACHE2_NEED_ACTION" ] && return 0
fi
;;
Unless I'm missing something, it seems that the fix already made in Debian's Apache packaging has still not been included in the Debian 13 stable packages.
From my point of view, this is a potential security issue. Although the updated PHP packages are installed, running Apache processes may continue using the old PHP libraries until Apache is restarted.
Has anyone found a workaround for this issue, or have I missed an update on my server that would fix the bug?