Apache HTTP/2 CVE-2026-119618: Check Exposure and Verify the Fix
Apache rates CVE-2026-119618 critical: a synchronization flaw in mod_http2’s assign_headers() can cause heap corruption and remote code execution. The advisory lists Apache HTTP Server 2.4.55 through 2.4.70, and independently released GitHub mod_h2 2.0.8 through 2.0.42, as affected. Apache HTTP Server 2.4.71, released November 11, 2026, includes the fix.
Prioritize servers that accept HTTP/2 requests. For an upstream installation, move to 2.4.71 or a later supported release containing the fix. For a distribution package, establish the vendor’s fix status before judging an older version string.
Find the service that handles HTTP/2
Apache’s HTTP/2 guide requires mod_http2 and protocol configuration. Check the executable, configuration and modules used by each running service or container. With the service’s own environment and configuration arguments, the Apache control wrapper’s -v reports the version, -M lists loaded modules, and -S shows virtual hosts. The command reference documents those options; wrapper names commonly include apachectl and apache2ctl. Configuration errors or permission failures leave the check unresolved.
Look for http2_module, then inspect Protocols in the base configuration and every applicable virtual host, including included files. h2 enables HTTP/2 over TLS; h2c covers cleartext HTTP/2. A loaded module alone does not establish that a particular endpoint accepts HTTP/2. A wrapper inspecting a different installation says nothing about the active service.
Trace both sides of a reverse proxy. The protocol a browser negotiates with a CDN does not identify the origin protocol. Apache’s HTTP/2 proxy module can forward HTTP/1.1 frontend requests to an HTTP/2 backend. Check direct origin access and internal listeners too. A firewall allowing ordinary web traffic does not by itself remove exposure in the HTTP/2 request handler.
Collect package evidence locally
On a Debian-family installation, this read-only Bash command reports package revisions and installation status. It needs no root access, creates no files, and requires no cleanup:
LC_ALL=C dpkg-query -W -f='${binary:Package}\t${Version}\t${Status}\n' apache2 apache2-binObserved output on the Debian 13 Linux environment used for this article:
dpkg-query: no packages found matching apache2
dpkg-query: no packages found matching apache2-binThe command exited with status 1 because these packages were absent. This does not rule out a source installation, another package name, or Apache inside a container. Run the inventory in the environment that supplies the service. The module may also come from a separate package or build; record its supplier and revision. No Apache service or vulnerability reproduction was tested here.
Vendors can backport security fixes while retaining an older upstream version. Match the exact installed package revision and operating-system release to the supplier’s advisory for this CVE. Record the advisory URL and fixed package revision; a banner or scanner’s version comparison is insufficient. This article does not establish that any particular distribution package has received a backport.
Patch and verify the running replacement
The released upstream fix is Apache HTTP Server 2.4.71, published November 11, 2026. It is available from Apache’s download page, which includes source archives and signature/checksum verification links. Upgrade an upstream installation to 2.4.71 or a later supported release containing the fix. Apache links the correction as commit 824beab; prefer the supported release over applying an isolated patch without integration testing.
For a distribution-managed installation, use its established update channel and the supplier’s advisory for this CVE. Install the specified fixed package revision for your operating-system release, which may retain an older upstream version through a backport. Record the installed revision and advisory together. For a separately supplied module, verify its fix independently of the server version. The inventory command above cannot establish that a backport exists or that the running service has loaded it.
Test the replacement in staging, run the configuration syntax check through the service’s wrapper, and follow the supplier’s procedure for restarting into the updated binary. A graceful configuration restart leaves the parent process running and lets old workers finish requests; it alone does not prove that a patched executable has replaced the old one. Confirm that the parent and all serving workers use the replacement binary and module; updated files on disk do not prove existing processes have stopped using old code. Recheck virtual hosts and normal application requests, including expected protocol negotiation. Ordinary health checks establish service behavior, not absence of this race condition. These rollout steps were not executed against an Apache service for this article.
If patching must wait, assess temporarily disabling HTTP/2 on the affected listeners. The Protocols directive allows HTTP/1.1-only configuration, but a virtual host’s own setting replaces the base setting. Account for every override and both h2 and h2c, test application compatibility, then verify the effective behavior after applying the change. Treat this as temporary exposure reduction pending a verified fix.
NVD: CVE-2026-119618.
Acknowledgements
This post was created with assistance from AI.