Apache 2.4.71 fixes critical mod_http2 flaw that can lead to RCE
Key takeaways
- CVE-2026-119618 is a critical mod_http2 concurrency flaw that can lead to RCE in Apache 2.4.55 through 2.4.70
- Apache 2.4.71 was released on 11 November 2026, after the first report of this flaw on 26 October 2026
- Servers on 2.4.69 or 2.4.70 are also affected by the mod_vhost_alias flaw fixed in 2.4.71, and mod_md is affected from 2.4.30
The Apache HTTP Server project released version 2.4.71 on 11 November 2026 to fix CVE-2026-119618, a critical flaw in mod_http2 that can lead to remote code execution.
What changed
The flaw sits in the assign_headers() function of mod_http2, the module that handles HTTP/2 traffic. The advisory's own title for the issue is "heap corruption and RCE in assign_headers", and it says the flaw can lead to remote code execution. Affected releases of the standalone mod_h2 module from GitHub, from 2.0.8 through 2.0.42, are also vulnerable.
The timeline is short. Anthropic's OSS Scanner reported the bug to the security team on 26 October 2026, tracked as ANT-2026-MAPKT6MZ. Anthony Weems and Simon Scannell of the Google Cloud Vulnerability Research team reported it to the security team on 3 November. The fix landed in the 2.4.x branch on 11 November, the same day 2.4.71 was released.
The release also fixes two other issues. CVE-2026-106023, rated important, is a NULL pointer dereference in mod_md that leads to a child process crash during HTTP request processing, affecting 2.4.30 through 2.4.70. CVE-2026-109163, rated low, is a one-byte stack buffer overwrite in mod_vhost_alias that affects only 2.4.69 and 2.4.70. It is listed as arising after CVE-2026-63292, an earlier mod_vhost_alias stack overflow fixed in 2.4.69.
In all, 2.4.71 carries 3 CVEs: one critical, one important and one low.
Impact on businesses
The critical flaw covers a long span of releases, from 2.4.55 through 2.4.70. Enterprise IT teams should start with an inventory: which hosts run a version in that range, and which of them load mod_http2.
Servers on 2.4.69 or 2.4.70 have an additional reason to move. They are affected by the mod_vhost_alias overwrite, CVE-2026-109163, which 2.4.71 fixes. The mod_md crash, CVE-2026-106023, reaches much further back, to 2.4.30, so any estate using mod_md should treat it as in scope as well.
Impact on consumers and users
Ordinary users will not see anything directly. The practical consequence is indirect: a remote code execution flaw in a web server is a risk to the sites running it and to the people who use them. Site owners who run Apache themselves are responsible for applying the update, and the safest course is to move to 2.4.71 and confirm the version afterwards.
Impact on the wider industry
The credit lines are worth reading. The critical bug was found by Anthropic's OSS Scanner, and Anthony Weems and Simon Scannell of the Google Cloud Vulnerability Research team are credited as finders too. The 2.4.69 advisory also credits "Calif.io in collaboration with Anthropic" and "AISLE in partnership with Red Hat" for the finding behind CVE-2026-93546, a mod_dav_fs namespace overflow.
The recent release history shows varying CVE counts: 2.4.66 in December 2025 fixed 5 CVEs, 2.4.67 in May 2026 fixed 11, 2.4.68 in June fixed 13, and 2.4.69 in October fixed 20. 2.4.71 followed in November with 3. For maintainers, a rising volume of reports means more fixes to ship. For defenders, it means more updates to track and deploy. As recent coverage of the Oracle cycle shows, patch volume is a pressure across the industry, not just for Apache.
What comes next
Check your vendor's advisory rather than the version string alone, and re-read the Apache advisory for updates. The advisory lists the affected range as 2.4.55 through 2.4.70, so any server in that range should be moved to 2.4.71 as soon as testing allows.
Verdict
This is a net positive for defenders who act on it: the fix is out and the advisory is specific about the affected versions. It is a net negative for anyone who runs Apache and does not track point releases, because a critical remote code execution flaw now has a published fix and advisory. Patch the servers running mod_http2 first, then work through the mod_md and mod_vhost_alias fixes.
Frequently asked questions
Which Apache versions are affected by CVE-2026-119618?
Apache HTTP Server from 2.4.55 through 2.4.70, plus mod_h2 releases from GitHub from 2.0.8 through 2.0.42. The fix is in 2.4.71, released on 11 November 2026.
What is the critical Apache flaw?
A concurrency bug in mod_http2's assign_headers() function. The Apache team describes it as improper synchronisation of a shared resource and says it can lead to remote code execution.