All posts

Apache 2.4.71, nginx 1.30.7 and the November PHP releases: how to check and patch a cPanel server

Between November 11 and November 19, 2026, Apache, nginx and PHP each shipped security releases. If you run cPanel & WHM servers, all three are likely on your machines. This guide covers what was fixed, how to check what you're running, and how to update without leaving the old code in memory.

Run everything here as root. The checks in the first two sections change nothing.

What was released

Software Fixed versions Released Severity (vendor's rating)
Apache HTTP Server 2.4.71 Nov 11 Critical: CVE-2026-119618, mod_http2. Affects 2.4.55 to 2.4.70
nginx 1.30.7 (stable), 1.31.9 (mainline) Nov 18 Ten CVEs. Highest: "major", including CVE-2026-123007 (HTTP/2 flow control)
PHP 8.5.13, 8.4.28, 8.3.37, 8.2.36 Nov 19 Highest severity critical, per php.net

Apache. The flaw is in mod_http2, the module that handles HTTP/2. Apache describes it as a race condition in how headers are assigned, which can lead to remote code execution. A server is only exposed if mod_http2 is loaded and HTTP/2 is enabled.

nginx. cPanel servers don't run nginx by default, but many use ea-nginx, cPanel's nginx reverse proxy in front of Apache. The release fixes ten issues across HTTP/2, HTTP/3, TLS 1.3 request handling, the resolver, the mail proxy and the stream modules, so the HTTP/2 bugs aren't the only reason to update.

PHP. Every supported branch got a security release on the same day. The fixes include PHP-FPM, session handling and the date extension. PHP 8.1 and older are no longer supported by the PHP project and get no fixes.

1. Check what you're running

Apache version and whether HTTP/2 is loaded:

httpd -v
httpd -M 2>/dev/null | grep -i http2

The EasyApache 4 packages behind them:

rpm -q ea-apache24 ea-apache24-mod_http2 ea-nginx

On Ubuntu servers use dpkg -l 'ea-apache24*' 'ea-nginx*' instead. "Not installed" for ea-nginx simply means you don't use it.

Every PHP version installed through EasyApache 4:

for p in /opt/cpanel/ea-php*/root/usr/bin/php; do
  echo "$p $($p -r 'echo PHP_VERSION;')"
done

On CloudLinux servers, the alt-php versions live under /opt/alt/php*/usr/bin/php; the same loop works with that path.

To see which sites use which PHP version:

whmapi1 php_get_vhost_versions | grep -E '^\s+(version|vhost):' | paste - -

2. Check from the outside

Whether a site actually negotiates HTTP/2 (this works from any machine with a recent curl):

curl -sI --http2 -o /dev/null -w '%{http_version}\n' https://example.com

2 means HTTP/2. 1.1 means it isn't in use for that site.

3. Update, then restart

EasyApache 4 packages come through the system package manager.

AlmaLinux, Rocky and CloudLinux 8/9:

dnf update 'ea-*'

CentOS 7 or CloudLinux 7: yum update 'ea-*'. Ubuntu:

apt-get update
apt-get install --only-upgrade $(dpkg-query -W -f='${binary:Package}\n' 'ea-*')

Updating everything under ea-* also brings any other pending EasyApache updates. On a busy server, try it on one machine first and have a recent backup.

Then restart. This is the step that gets missed. A running web server or PHP-FPM pool keeps the old code in memory until it restarts, and nginx needs a full restart, not a reload, to load a new binary.

/scripts/restartsrv_httpd
/scripts/restartsrv_apache_php_fpm
/scripts/restartsrv_nginx      # only if ea-nginx is installed

Confirm nothing is still running old code (RHEL family; the command comes with dnf-utils):

needs-restarting -s

Anything it lists still needs a restart.

Finally, run the checks from section 1 again and compare the versions.

If the fixed version isn't offered yet

cPanel builds its own EasyApache 4 packages, so there can be a gap between an upstream release and the package for your OS. PHP only shipped on November 19, so expect that one to lag. If dnf reports nothing to update and the versions are still old, check again later and watch cPanel's EasyApache 4 change log.

A stopgap for the HTTP/2 bugs

If you can't update straight away, turning HTTP/2 off removes exposure to the HTTP/2 flaws. Visitors fall back to HTTP/1.1. It does nothing for the other nginx fixes or for PHP, so treat it as a holding measure, not a fix.

  • Apache on cPanel: in WHM, open EasyApache 4, customize the current profile, switch off mod_http2 under Apache Modules, then review and provision. Turn it back on once 2.4.71 is installed.
  • nginx: remove http2 from the listen directives (or set http2 off; on newer versions), test with nginx -t, then restart. On ea-nginx, check cPanel's documentation first, because its configuration is generated and manual edits may be overwritten.

Old PHP versions

PHP 8.1 and older receive no security fixes from the PHP project, and PHP 8.2 reaches end of life on December 31, 2026. Some vendors, including CloudLinux, offer backported fixes for older versions; check with yours. Otherwise, use the php_get_vhost_versions output above to list the sites still on old versions, contact their owners, and move them to 8.3 or newer.

Keeping a record

After a week like this, it's useful to be able to answer "when did the update actually land on each server?" Watchdog (beta) for cPanel & WHM records installed package versions with every configuration snapshot, so you can see exactly when ea-apache24 or an ea-php package changed.

Sources