A flaw in the HTTP/2 module can reach the server process

Apache lists CVE-2026-119618 as a critical concurrency flaw in mod_http2 that can lead to remote code execution. It affects Apache HTTP Server 2.4.55 through 2.4.70. Apache released 2.4.71 on 11 November with the fix.

This is a module-specific exposure. A version string alone does not establish that a host is reachable through the vulnerable path: check whether mod_http2 is loaded and HTTP/2 is offered on the affected service. Distribution packages may also carry a backported fix without adopting the upstream version number.

Do not assume exploitation

The published Apache notice describes the vulnerability and fix. It does not, by itself, establish that attackers have used it against real systems. Treat a vulnerable, reachable server as urgent without presenting attacks as confirmed.

Check exposure and the running fix

  1. 1

    Find the actual HTTP/2 endpoints. Inventory Apache instances, including containers and reverse proxies. Confirm whether mod_http2 is loaded and which listeners negotiate HTTP/2.

  2. 2

    Apply the right package. Upgrade to Apache 2.4.71 or the distribution's advisory-backed patched build. Record the package advisory if it is a backport.

  3. 3

    Restart and verify. Restart affected services, confirm the running binary or container image has changed, and check that expected HTTP/2 traffic still works.

Keep the inventory tied to service behavior

A package scan gives the starting list. The useful closure evidence is narrower: the affected service, its loaded module, the applicable vendor fix, and the version now running. That avoids both overlooking a hidden container and chasing an Apache install that never enabled HTTP/2.