On November 11 Apache released 2.4.71 to fix CVE-2026-119618, a remote code execution flaw in its HTTP/2 module, mod_http2, before any distribution had a patch (see our report). On November 12 Ubuntu and Debian released fixed packages, and Red Hat had already shipped its fix on the 11th. One correction: going by the affected range Apache published (2.4.55 through 2.4.70), our previous article concluded that the 2.4.52 shipped with Ubuntu 22.04 was outside it. Ubuntu's own assessment is that it has backported newer versions of mod_h2 into its stable releases, so 20.04 and 22.04 were affected as well and are fixed in this update. If you skipped a 22.04 server because of our earlier article, upgrade it now.

Fixed versions by distribution

  • Ubuntu (USN-9090-1, published at 21:25 UTC on November 12): 2.4.52-1ubuntu4.27 on 22.04, 2.4.58-1ubuntu8.19 on 24.04, 2.4.66-2ubuntu2.8 on 26.04 and 2.4.68-1ubuntu6.2 on 26.10; 2.4.41-4ubuntu3.23+esm11 for 20.04 is available only through paid ESM. The notice fixes 5 vulnerabilities in total; the other 4 are a NULL pointer dereference in mod_md (CVE-2026-106023), a stack overflow in mod_vhost_alias (CVE-2026-109163), a memory size miscalculation when mod_dav handles WebDAV locks (CVE-2026-42528), and a CGI internal redirect issue that affects only 26.04 and 26.10 (CVE-2026-42356).
  • Debian: Debian 13 gets DSA-6620-1 with fixed version 2.4.71-1~deb13u1. Debian 12 is now maintained by the Long Term Support (LTS) team and gets DLA-4902-1 with 2.4.71-1~deb12u1, which moves it straight to 2.4.71 and fixes 23 CVEs at once. Both were published on November 12.
  • RHEL: RHSA-2026:98981 (RHEL 9, mod_http2 2.0.26-7.el9_9.1) and RHSA-2026:98978 (RHEL 10, mod_http2 2.0.29-5.el10_3.1) were released on November 11. RHEL 8 and earlier ship mod_http2 older than 2.0.8, which does not contain the affected code, so they are not affected.

How to upgrade and confirm

  • Debian and Ubuntu: run sudo apt update && sudo apt upgrade, then sudo systemctl restart apache2 so the running processes switch to the new version.
  • To confirm, check the package version rather than apache2 -v: Ubuntu patches the existing version, so after the upgrade apache2 -v on 22.04 still reports 2.4.52. Run dpkg -s apache2 | grep Version instead; a result no lower than the versions listed above means you are fixed.
  • RHEL family: run sudo dnf update mod_http2, then sudo systemctl restart httpd, and confirm with rpm -q mod_http2.
  • If you followed our earlier advice and turned HTTP/2 off with sudo a2dismod http2, turn it back on after upgrading with sudo a2enmod http2 and restart Apache.

How dangerous is it right now

The assessments differ. Red Hat rates it Critical (CVSS 9.8) and states that public research has demonstrated a reliable exploit against a default-configured server with mod_http2 enabled; only servers that enable h2 or h2c in the Protocols directive are affected, and servers that serve only HTTP/1.1 are not. The mod_http2 in RHEL 9 and 10 allocates memory for each HTTP/2 stream separately, which makes exploitation much harder, so Red Hat rates those two Important. The US National Vulnerability Database lists CISA's score of 8.1 (high attack complexity); CISA's assessment on November 13 recorded no exploitation, and as of November 17 the flaw is not in the KEV catalog. Whichever assessment you go by, the answer is to upgrade soon. If a control panel such as aaPanel compiled Apache for you, upgrade to 2.4.71 inside the panel; panel security settings are in our aaPanel installation and security guide. If you are still on 20.04 without ESM, you will not get this patch; migration advice is in choosing a VPS operating system. If the server showed unfamiliar processes or files while it was unpatched, go through our intrusion check and hardening guide.