← All articles

Apache HTTP/2 flaw puts servers at risk of code execution

Apache HTTP/2 flaw puts servers at risk of code execution

The Apache HTTP/2 vulnerability CVE-2026-119618 can allow an unauthenticated remote attacker to run code through the Apache HTTP Server process. The flaw affects the mod_http2 module, which provides HTTP/2 support, in Apache versions 2.4.55 through 2.4.70. Apache fixed it in version 2.4.71, released yesterday.

HTTP/2 is a newer version of the web protocol used to exchange pages and other content between browsers and servers. Only servers with HTTP/2 enabled are affected, according to Red Hat, which distributes Apache as part of Red Hat Enterprise Linux. An attacker only needs network access to the server and does not need an account or password. Red Hat rates the issue 9.8 out of 10 on the Common Vulnerability Scoring System, or CVSS, a scale used to describe the severity of security flaws.

Red Hat’s assessment says public research has demonstrated a reliable exploit against a server in its default configuration when mod_http2 is enabled. The assessment does not identify or link that research. Security company Wiz said later the same day that no exploit was available and that it had seen no exploitation in the wild. Those statements describe different assessments of the available evidence, so administrators should treat the vulnerability as serious without assuming that attacks are already confirmed.

Administrators should check whether HTTP/2 is enabled through Apache’s Protocols directive. This setting can apply to the whole server or to an individual virtual host, meaning one separately configured website on the same server. The value h2 enables HTTP/2 over an encrypted connection, while h2c enables it over plain TCP. Both the server-wide setting and every virtual host should be checked.

Administrators using the Apache HTTP Server project’s own releases should upgrade to 2.4.71. That release also addresses a crash in mod_md, rated important, and a one-byte overwrite of stack memory in mod_vhost_alias, rated low. A stack overwrite is an error that writes beyond the intended area of a program’s temporary memory and can affect its operation or security.

The standalone version of the module, distributed on GitHub as mod_h2, is also affected from version 2.0.8 through 2.0.42. The project has not published a fixed release. Its GitHub release list ends at 2.0.42, the last affected version, and the repository has been read-only since it was archived on June 9. The same mitigation applies to these builds: remove h2 and h2c from the Protocols directive and leave Protocols http/1.1, according to Wiz’s vulnerability analysis. Apache’s own advisory does not list a workaround.

Distribution packages use their own version numbers and release schedules. Red Hat shipped fixes for Red Hat Enterprise Linux 9 and 10 yesterday, rating the issue Important on those systems rather than Critical. Red Hat says its mod_http2 packages assign each HTTP/2 stream its own memory allocator, which makes exploitation much harder. The fixed packages are mod_http2-2.0.26-7.el9_9.1 for Red Hat Enterprise Linux 9 and mod_http2-2.0.29-5.el10_3.1 for Red Hat Enterprise Linux 10. Red Hat Enterprise Linux 8 and earlier do not contain the vulnerable code.

Red Hat also lists fixes for Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions, and for versions 9.6, 9.8, 10.0 and 10.2 Extended Update Support, through separate advisories RHSA-2026:98968, RHSA-2026:98954, RHSA-2026:98982, RHSA-2026:98953 and RHSA-2026:98979. Red Hat Enterprise Linux 6, 7 and 8 are marked not affected. Red Hat JBoss Core Services and Red Hat Hardened Images are marked affected, with no fix listed.

Debian marks the issue fixed in unstable, also called sid, with apache2 2.4.71-1. Debian bookworm, trixie and forky are listed as vulnerable with no fixed package listed. Amazon Linux 2 Core, Amazon Linux 2023 and Amazon Linux 2027 Preview have a fix pending. Ubuntu had no status page for the CVE when the issue was checked. These statuses come from the Debian security tracker and Amazon Linux tracker, while the Ubuntu status was checked in its CVE tracker.

Anthropic’s OSS Scanner, a free service that scans open-source projects using the company’s AI models, reported the flaw on October 26. Google Cloud Vulnerability Research reported it last week. An earlier HTTP/2 issue, CVE-2026-23918, was fixed in Apache 2.4.67, released on May 4, but systems updated to 2.4.67 or any later version through 2.4.70 remain affected by CVE-2026-119618.

Website owners who rely on a provider should ask which Apache release and HTTP/2 configuration serve their sites, rather than assuming that a previous Apache update included this fix. AEU Hosting provides managed WordPress hosting, secured end to end, which is relevant for site owners who want hosting security handled as part of a managed service.

Until the appropriate vendor package or Apache release is installed, administrators should disable HTTP/2 where practical, confirm that no virtual host separately enables it, and continue checking the relevant distribution advisory for an updated package.

Also available in: DeutschItalianoShqip