Apache HTTP Server 2.4.71 fixes critical mod_http2 flaw CVE-2026-119618
Apache HTTP Server 2.4.71 fixes CVE-2026-119618, a critical mod_http2 bug that needs no authentication and has a demonstrated exploit; Debian and standalone mod_h2 have no fix.
Apache HTTP Server 2.4.71 was released on 2026-11-11. According to The Hacker News, the release fixes CVE-2026-119618, a critical flaw in mod_http2, the module that handles HTTP/2 connections. The Apache HTTP Server project describes the bug as a concurrent-execution problem in assign_headers() that can lead to remote code execution (RCE).
What is affected
Apache HTTP Server 2.4.55 through 2.4.70 is affected, as are standalone mod_h2 releases 2.0.8 through 2.0.42 published on GitHub. Debian bookworm, trixie and forky are listed as vulnerable with no fix, and the standalone mod_h2 project has published no fixed release.
According to the report, only servers with HTTP/2 enabled are affected, and an attacker who can reach the server needs no authentication. Red Hat says public research has demonstrated a reliable exploit against a default-configuration server with mod_http2 enabled, the report adds.
Why it matters
Anyone who can reach an affected server can attempt the flaw without credentials. Public research has demonstrated a reliable exploit against a default-configuration server with mod_http2 enabled. Servers that do not enable HTTP/2 are outside the affected configuration.
What to do
Upgrade to Apache HTTP Server 2.4.71. The advisory offers no workaround. Admins who cannot update yet can remove h2 and h2c from the Protocols directive and leave Protocols http/1.1, as Wiz advises, according to the report.
On Red Hat Enterprise Linux 9, the fix ships as mod_http2-2.0.26-7.el9_9.1 under RHSA-2026:98981. On Red Hat Enterprise Linux 10 it is mod_http2-2.0.29-5.el10_3.1 under RHSA-2026:98978. Red Hat Enterprise Linux 6, 7 and 8 are not affected.
Sources
Related reading
3 postsDiscussion
Spotted an error? Send corrections to [email protected] .