The Apache HTTP Server project has released version 2.4.71, a security update that fixes a critical flaw in its HTTP/2 module that could let a remote attacker run code on affected web servers. The flaw, tracked as CVE-2026-119618, affects every Apache release from 2.4.55 through 2.4.70, and administrators are being urged to upgrade immediately.
The bug sits in a function called assign_headers() inside mod_http2, the module that handles HTTP/2 traffic. Apache describes it as a concurrency problem: two threads can touch shared memory without proper locking, corrupting the heap of the process serving the request. In the worst case, that corruption can be turned into remote code execution, giving an attacker control of the server process.
Red Hat, which ships Apache as part of Red Hat Enterprise Linux, rates the flaw 9.8 out of 10 on the CVSS scale. An attacker needs no login and no action from a user — only the ability to reach the server. Only servers with HTTP/2 actually enabled are exposed, since the vulnerable code runs only when the module is loaded.
Found by two teams — and no known attacks yet
The flaw was found independently by two teams. Anthropic's OSS Scanner, a free scanning service for open-source projects, reported it on October 26, and researchers Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research reported it on November 3. The fix shipped with version 2.4.71 on November 11, the same day the flaw was made public.
There is no evidence so far that the flaw has been exploited in the wild. Security company Wiz said no exploit was available on the day of the release, and the flaw is not listed in CISA's Known Exploited Vulnerabilities catalog. A repository published on GitHub on November 12 appears to reproduce a crash, but researchers who examined it say it is not a demonstrated code-execution exploit. Apache itself publishes no CVSS score for the flaw, relying on its own severity scale, under which it is rated critical.
Two more flaws fixed in the same release
Version 2.4.71 fixes three vulnerabilities in total. Alongside the HTTP/2 flaw, it patches CVE-2026-109163, a one-byte stack buffer overwrite in mod_vhost_alias rated important, and CVE-2026-106023, a null pointer dereference in mod_md rated low. The standalone mod_h2 module distributed separately on GitHub is also affected, in versions 2.0.8 through 2.0.42, and it has no fixed release yet.
What to do now
Administrators running Apache's own releases should move to version 2.4.71. Distribution packages are lagging behind the upstream release: as of November 12, Debian's stable and testing branches still ship vulnerable builds, with the fixed version available only in unstable. Turning HTTP/2 off removes the exposure entirely, since requests never reach the vulnerable module when it is not loaded — an option for servers that cannot be patched right away.
Apache remains one of the most widely deployed web servers in the world, so a flaw of this severity in a default-adjacent module draws immediate attention. It is the second serious HTTP/2 issue for the project this year: an earlier flaw, CVE-2026-23918, was fixed in version 2.4.67 in May. The better-known HTTP/2 Rapid Reset attack, CVE-2023-44487, is a separate issue and is not involved here.



