The Apache HTTP Server Project released httpd 2.4.71 on November 11, 2026. The update fixes three security issues, and one of them, CVE-2026-119618 in the HTTP/2 module, is rated critical because it can let an attacker run code on the server.
Apache httpd still fronts a large share of web applications, REST endpoints and admin consoles, including many that sit in front of database-backed apps. Any server that has HTTP/2 turned on and runs a release from the last few years should be patched quickly.
What was fixed in httpd 2.4.71
The project's security page lists three CVEs for this release, one critical, one important and one low:
- CVE-2026-119618 (critical): a synchronization bug in the assign_headers function of mod_http2. Concurrent access to a shared resource can corrupt heap memory, and the project says this can lead to remote code execution.
- CVE-2026-106023 (important): a NULL pointer dereference in mod_md, the module that manages certificates through ACME. A crafted request can crash a child process.
- CVE-2026-109163 (low): a one-byte stack buffer overwrite in mod_vhost_alias. It is a follow-up to an earlier fix, CVE-2026-63292.
Which versions are affected
The critical HTTP/2 bug affects httpd 2.4.55 through 2.4.70. It also affects the standalone mod_h2 module published on GitHub, in versions 2.0.8 through 2.0.42. Sites that build mod_h2 separately, often to get newer HTTP/2 features, need to update that module as well.
The mod_md crash reaches much further back, covering 2.4.30 through 2.4.70. The mod_vhost_alias overwrite only touches 2.4.69 and 2.4.70, because it was introduced by the previous round of fixes.
Who found the bugs
The critical flaw was reported twice. Anthropic's open source scanner flagged it on October 26, and researchers Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research reported it on November 3. The fix landed in the 2.4.x branch and shipped in the release on November 11.
The mod_md issue was reported in late September by several independent finders, including a team from the 360 Vulnerability Research Institute. Five separate researchers reported the mod_vhost_alias overwrite in October.
What it means for developers and DBAs
Heap corruption bugs in a protocol handler are the kind of flaw attackers work hard to turn into exploits, because they can be reached by anyone who can open a connection. No exploit details have been published on the security page, but the critical rating and two independent reports suggest the bug is reachable in practice.
Start by finding where httpd runs. Common places include reverse proxies in front of Oracle REST Data Services or Tomcat, PHP application servers, internal tools, and container images built on official httpd tags. Check the version with httpd -v or apachectl -v, and confirm whether the Protocols directive enables h2 or h2c.
Most Linux users will receive the fix through their distribution packages rather than the upstream tarball. Watch your vendor's advisory for CVE-2026-119618 and confirm that the updated package carries a backported patch, since distributions often keep an older version number.
If you cannot patch right away, removing h2 and h2c from the Protocols directive and falling back to HTTP/1.1 takes the vulnerable module out of the request path. This costs some performance for browsers but closes the most serious hole. The mod_md and mod_vhost_alias issues are only relevant if those modules are loaded.
How to upgrade
Source builds can download 2.4.71 from the Apache HTTP Server download page and verify the signature before installing. Container users should rebuild on the newest official image once it carries 2.4.71, and redeploy rather than patching running containers in place.
After the upgrade, restart the service fully, not just a graceful reload, so that no worker processes keep running the old code. Then confirm the reported version and test HTTP/2 traffic again with a browser or a client such as curl with HTTP/2 enabled.
Conclusion
httpd 2.4.71 is a short release with one urgent fix. Any server on 2.4.55 or newer with HTTP/2 enabled is exposed to a critical memory corruption bug, so patching or disabling HTTP/2 should not wait for the next maintenance window.
Sources
- Apache HTTP Server Project: Apache HTTP Server 2.4 vulnerabilities
- Apache HTTP Server Project: Apache httpd 2.4.71 Released
See my articles more often when you search Google.
