VMTech
Discuss a project →

Apache HTTP Server 2.4.71 fixes critical HTTP/2 code execution flaw

Apache HTTP Server 2.4.71 fixes critical HTTP/2 code execution flaw

Apache HTTP Server 2.4.71 fixes CVE-2026-119618, a critical remote-code-execution vulnerability in the mod_http2 module. The flaw affects Apache HTTP Server versions 2.4.55 through 2.4.70 when HTTP/2 is enabled, and Red Hat assigned it a CVSS score of 9.8 out of 10.

An attacker who can reach an affected server does not need authentication and could take full control of the server process, Red Hat said. The Linux vendor also stated that public research had demonstrated a reliable exploit against a default configuration with mod_http2 enabled. Wiz said later the same day that no exploit was publicly available and that it had seen no evidence of exploitation in the wild.

Exposure depends on the HTTP/2 configuration

The vulnerable component is active only when the Apache Protocols directive enables HTTP/2. Administrators can enable TLS-based HTTP/2 with h2 or cleartext HTTP/2 over TCP with h2c. Because the directive can be configured globally or per virtual host, a complete exposure review must cover both the server-wide configuration and every virtual-host definition.

The Apache HTTP Server Project recommends moving to version 2.4.71. That release also addresses an important crash issue in mod_md and a low-severity one-byte stack-memory overwrite in mod_vhost_alias. Organisations should not treat an update to 2.4.67, which fixed the earlier CVE-2026-23918 HTTP/2 issue, as sufficient: every release from 2.4.67 through 2.4.70 remains affected by the newly disclosed flaw.

Distribution packages need separate checks

Linux distributions may ship their own builds and package versions rather than the upstream Apache release number. Red Hat issued fixes for Red Hat Enterprise Linux 9 and 10, including mod_http2-2.0.26-7.el9_9.1 for RHEL 9 and mod_http2-2.0.29-5.el10_3.1 for RHEL 10. It rates the issue Important, rather than Critical, on those versions because its packages provide each HTTP/2 stream with a separate memory allocator, which it says makes exploitation much harder.

Red Hat Enterprise Linux 6, 7 and 8 do not contain the vulnerable code. Its JBoss Core Services and Hardened Images were listed as affected without a fix. Debian unstable received apache2 2.4.71-1, while Debian bookworm, trixie and forky were listed as vulnerable. Amazon Linux 2, Amazon Linux 2023 and Amazon Linux 2027 Preview had pending fixes, and Ubuntu had no status page when the report was checked.

Mitigation when upgrading cannot happen immediately

Apache's advisory provides no workaround. Wiz recommends removing h2 and h2c from the Protocols directive and leaving Protocols http/1.1 until a supported update can be deployed. The same mitigation applies to standalone mod_h2 builds, which are affected from version 2.0.8 through 2.0.42 and have no fixed release; the GitHub repository was archived on June 9.

The issue was reported on October 26 by Anthropic's OSS Scanner and was also reported by Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research. For operations teams, the immediate business implication is to identify externally reachable Apache services with HTTP/2 enabled, validate distribution-specific fixes, and disable HTTP/2 temporarily where a tested patch cannot yet be installed.

#apache#httpsecurity#vulnerability#patchmanagement
Open analytics
On the site 4 views
min read 4 12.11.2026
Instagram

Apache HTTP Server 2.4.71 fixes critical HTTP/2 code execution flaw

Open the post on Instagram ↗