What Apache has confirmed

Apache lists CVE-2026-119618 as a critical mod_http2 heap-corruption issue that can lead to remote code execution. The cause is concurrent use of a shared resource without correct synchronization in assign_headers(). Apache HTTP Server versions 2.4.55 through 2.4.70 are affected; the separately distributed mod_h2 releases 2.0.8 through 2.0.42 are also listed.

The issue was fixed in Apache HTTP Server 2.4.71, released on 11 November 2026. A server is exposed to this specific path when the affected HTTP/2 module and version are in use. Check protocol configuration and package source rather than relying on a generic web-server scan.

Find all HTTP/2 endpoints

Inventory Apache servers on public websites, internal portals, APIs and partner gateways. Check whether mod_http2 is loaded and whether the server advertises or accepts HTTP/2. Some services terminate HTTP/2 at a proxy; others pass traffic to Apache. Map each layer to its owner.

Include container images, control panels and vendor products that package Apache. The operating system may backport a fix without changing the upstream version string. Confirm the package advisory when the installed version does not match 2.4.71.

Patch and confirm the running build

Install Apache 2.4.71 or the supported vendor package containing the fix. Test the change in a representative environment, then verify the service version and HTTP/2 behaviour after restart. Confirm normal TLS, virtual host routing and upstream responses.

If you cannot update immediately, ask the service owner and supplier about a supported temporary reduction of exposure. Preserve HTTP/2 service requirements and validate any protocol change. A workaround does not replace the fixed release.